Difference between revisions of "MiniAudicle/miniAudiclebuildInstructionsforwindows/buildinstructionswindowsvc6"

From CSWiki
Jump to: navigation, search
Line 42: Line 42:
Change the dropdown list to Library files and add the path below.
''Change the dropdown list to Library files and add the path below.''

Revision as of 19:07, 19 October 2007

mini Audicle Build directory setup guide:

I noticed that there were no setup intructions for building miniAudicle so I decided to add these instructions to encourage others who might wish to become involved. I am limiting these instructions to Visual C++ 6.0 and may add instructions later for how to import the projects in to Visual Studio 2003. you will need to first download the source for miniAudicle and wxWidgets. I chose wxWidgets all 2.8.6 at a later time there may be a newer version. first I decided to extract the main directory structure to a partition, in my case it was G: but you might prefer C:. I changed all the paths in this document to C: since that is the likely structure. It might be good to create a new directory called C:/miniAudicleProject and extract the files within that sub-directory. I chose not to do that but with these instruction you should be able to locate all the dependencies needed to build mini Audicle.

Paths includes and libraries:


mini Audicle source directory and main Visual C++ 6.0 workspace/project file location

c:\miniAudicle- c:\miniAudicle-\miniAudicle.dsw


wxWidgets source directory and main Visual C++ 6.0 workspace/project file location c:\wxWidgets-2.8.6\build\msw


STC Library:

You will need to build the STC library separately from the rest of the wxWidgets. The workspace file is located at.


Please ensure that you have compiled this before beginning to compile the miniAudicle executable. The library output directory is located in the same place as the rest of the wxWidgets library files.

Extra paths for Visual C++:

These paths need to be added to the development environment To change these go to the VC menu "Tools" and select "Options". The options tabbed dialog appears select "Directories". Notice there is a dropdown list on the right by default it should be displaying Include files. Add the additional paths below.






Change the dropdown list to Library files and add the path below.


miniAudicle Project settings:

The project will need to be altered if you chose to use the updated wxWidget files I decided to use 2.8.6 and needed to change the project setting. Go to the VC 6.0 menu "Project" and then get to the tab Link. In that you will see library names like the following

wxmsw26d_adv.lib wxmsw26d_stc.lib wxmsw26d_core.lib

change them all to

wxmsw28d_adv.lib wxmsw28d_stc.lib wxmsw28d_core.lib.

The "d" in the names indicates a debug build for a release build you will only need to alter 26 to 28.

Select okay and build your copy of miniAudicle alpha for windows and you now can begin developing other additional changes or features for miniAudicle.



I added the root of the wxWidgets source directory into the includes so that the build could locate "c:\wxWidgets-2.8.6\lib\vc_lib\mswd\wx\setup.h" which is needed to build the libraries.


I found that you need to go through the wxWidget Library build process per each sub-project contained in the workspace file. This is just a limitation that perhaps I will locate a solution for it is just the way the wxWidget developers did it and has nothing to do with the miniAudicle developers, so don't complain to them. I assume if I properly configure the imported Visual C++ 6.0 files into Visual C++ 7.1 (Visual Studio 2003) it will be resolved. With all the include and library paths setup and the wxWidgets libraies built you should now be able to build a debug version of miniAudicle.


I wished to try and add the MAUI elements to miniAudicle but haven't yet figured that out. That may be my next wiki entry hopefully this will assist people getting started developing miniAudicle.

Errors vs Warnings:

Anytime you compile a cross platform application using cross platform libraries you may see a lot of warnings. I don't wish to claim that compiler warnings are unimportant but they may be less then critical when compiling a cross platform application. The systems that they might run under have different requirements and using the same code may be seen by the platform compiler as a warning. So I again point out that they may be less of an issue then one imagines but they do mean something that may not effect the actual running of the compile application. However if you get errors you will have to deal with those in order to move forward in whatever it is you are trying to accomplish.