Difference between revisions of "Developing On Windows"
(Links to related pages.)
|Line 1:||Line 1:|
* [[On Linux]]
* [[On Mac]]
=Windows Set Up=
=Windows Set Up=
Revision as of 11:09, 30 August 2007
Windows Set Up
Edit-hint: Please help us improve this text.
It can help to work in stages. It's probably not advisable to try to do all four steps in one session:
- First get comfortable with Microsoft's visual studio, MSVC 2005, downloadable from Microsoft . To develop in C/C++ for Windows you also need a second download from the Microsoft site, which is the "Platform SDK", or if you are on Vista you'll need the new "Windows SDK". Download links:
|Windows Server 2003 R2 Platform SDK for Windows 2000/XP/Server 2003:|
|Windows SDK for Windows XP/Server 2003/Vista:|
|There are instructions for using Visual C++ 2005 Express Edition with the Microsoft Platform SDK. With MSVC set up you can write 'hello world' and similar small programs just to check things out, or use some of the examples that Microsoft provide.|
- Next get a recent version of . If you want to work with cutting edge code in Audacity, use wxWidgets 2.8.4. Follow the instructions in the wxWidgets documentation to get some of the wxWidgets samples to compile. wxWidgets has excellent documentation on its API. Time spent reading that documentation and trying things out is time well spent. There is one detail in setting up wxWidgets which is very important. It's setting up the $(WXWIN) environment variable. It's not set by the installer. It must be set correctly to your wxWidgets directory if you're to compile Audacity. wxWidgets has be compiled in many different modes, e.g. Unicode and ansi, debug and release, library or dll. If you want to work with the latest Audacity code, make sure that amongst the versions you compile is the unicode - debug - dll version.
- Set up for CVS. For Windows get from Sourceforge. This adds extra menu items to your file explorer windows. When you right click on a folder you get additional items in the menu. These are used for synchronising your local copy of the files with the files at Sourceforge. Any user can read the files at Sourceforge via CVS, and that's all you need at this stage. If you have problems with accessing Audacity CVS from Windows send a message about it to the Audacity developer list. If we can't help you sort it out then we can at least send you an up to date snapshot of the code which will get you started.
Don't try moving onto this next step until you have at least one sample wxWidgets program compiled and running!
- If you have done all the steps above, this step should go smoothly. Open the project file for Audacity in MSVC, select the wx284Debug build of Audacity and click compile. Problems? Try cutting and pasting the error message into a google search box. Many of the compiler and linker error messages are fairly cryptic unless you've seen them before. Fortunately there's a lot of people out there who have, and there are messages in web searchable e-mail lists explaining what they mean and what to do.
Compiling on Windows
Edit hint: This is older advice relevant to the 1.2 series of Audacity, for building and linking with wxWidgets 2.6.x.
See the file win/compile.txt in the Audacity source code. Feel free to add any tips or tricks here. As of December 2004, now in CVS are *.vcproj files which will build in the newer versions of MS VC++ (.NET). 7-zip is a good free decompressor for extracting the source code archives.