Viewer 2 Microsoft Windows Builds
THESE INSTRUCTIONS ARE NOT YET COMPLETE OR DEBUGGED as of 18 April 2010.
When finished, we hope this page will constitute a complete recipe for compiling viewer 2 from source on a Windows machine, all in one place, as simply as possible.
Philosophy: to keep it brief, this page should only include steps we KNOW ARE NEEDED, not random hints.
This process will probably take 6 to 12 hours of wall-clock time, and 2 to 6 hours of your time, if you're starting from a fresh Windows XP/Vista/7 system.
- 1 Establish your programming environment
- 2 Download and compile libraries that must be manually added to each LL source release
- 3 Set up your source code tree
- 4 Fix known problems with the source code tree
- 5 Initial build steps using develop.py and CMake
- 6 Compile using the IDE
- 7 Fix things until the compile succeeds
- 8 Annotate your successes and failures here
- 9 References
Establish your programming environment
This is needed for compiling any viewer based on the LL open source code, but only needs to be done once.
- Obtain Visual Studio (2005, 2008, 2010) (Express is OK)
- Click here to download Visual C++ Express - current version is VS2010
- Note: LL still uses VS2005 internally, which uses the VC80 libraries. VS2008 and VS2010 ((confirm?)) use the VC90 libraries. We'll assume VC90 here.
- Install Microsoft Platform & DirectX SDKs
- Download and install Windows SDK for Windows Server 2008 and .NET Framework 3.5
- Download and install DirectX SDK (August 2008)
- Install other development tools
- CMake (download CMake)
- must be version 2.6.2 or higher
- Cygwin (download Cygwin)
- When you run the cygwin setup utility make sure you have selected to install patchutils, flex, and bison (all located under "devel") which are not part of the default install.
- Python (download either Python.org Standard Python or ActivePython
- CMake (download CMake)
Download and compile libraries that must be manually added to each LL source release
It is probably a good idea to build an empty directory tree for the files below and first copy the files there and once completed, copy the whole tree to the actual source folder. Then, if you obtain a new batch of source code, you can save some steps.
rem OLIBS.CMD to build a folder tree for 3rd party libraries and includes md olibs md olibs\linden\ md olibs\linden\libraries md olibs\linden\libraries\include md olibs\linden\libraries\i686-win32 md olibs\linden\libraries\i686-win32\lib\release md olibs\linden\libraries\i686-win32\lib\debug md olibs\linden\libraries\i686-win32\include md olibs\linden\libraries\i686-win32\include\GL md olibs\linden\libraries\i686-win32\include\quicktime md olibs\linden\indra md olibs\linden\indra\newview
- Download & install the Quicktime SDK for Windows
- copy "QuicktimeSDK\Libraries\QTMLClient.lib" to "linden\libraries\i686-win32\lib\release" and to "linden\libraries\i686-win32\lib\debug"
- Copy the contents of "QuicktimeSDK\CIncludes" into "linden\libraries\i686-win32\include\quicktime".
- Download & extract FMOD3.75 API for Windows. (later versions, like FMOD Ex, are incompatible).
- Copy "fmodapi375win\api\inc\fmod.h" to "linden\libraries\include"
- Copy "fmodapi375win\api\inc\fmod_errors.h" to "linden\libraries\include"
- Copy "fmodapi375win\api\inc\fmoddyn.h" to "linden\libraries\include"
- Copy "fmodapi375win\api\lib\fmodvc.lib" to "linden\libraries\i686-win32\lib\release" and to "linden\libraries\i686-win32\lib\debug"
- Copy "fmodapi375win\api\fmod.dll" to "linden\indra\newview"
Set up your source code tree
LL distributes the source code in three parts: the source package, the artwork package, and the library package. You should choose whether to use a snapshot or SVN checkout. You'll need art and libraries from a snapshot if you use the SVN method.
- Unzip or checkout your source tree into a directory that has as short full pathname as possible, with NO SPACES in it, to avoid trouble in the build scripts.
- Example: ((specific snapshot example TBD; SVN example also ))
Fix known problems with the source code tree
TBD - edits to scripts that must be made for windows VC90 builds to succeed?
Initial build steps using develop.py and CMake
You may notice that there's no Visual Studio project file as part of the distributed source tree. That's because it is GENERATED in this step using command-line tools. Only after this step can you begin using the IDE.
- open a Command Prompt window
- Run develop.py --
- From the command line, cd into the indra subdirectory
"develop.py -G VC90"or
"python develop.py -G VC90"
develop.pyscript will create and populate a build directory for you. It should be in
((TBD: how to tell if you succeeded))
Compile using the IDE
- Run Visual Studio.
- Use "File -> Open -> Project/Solution", navigate to linden/indra/build-VC90/Viewer.vcproj, and open it.
- if you can't find this file, perhaps your previous run of develop.py failed.
- Project ALL_BUILD and configuration RelWithDebugInfo should be selected, and the working directory for ALL_BUILD should be "linden\indra\newview".
- Build -> Build Solution (F7)
Fix things until the compile succeeds
((TBD - add any fixup steps here. e.g. does fmod375.dll need to be moved into RelWithDbgInfo at this step?))
Annotate your successes and failures here
These instructions are condensed from about a dozen previous pages of info:
- now partially incorrect
((add other references here))