Difference between revisions of "Viewer 2 Microsoft Windows Builds"

From Second Life Wiki
Jump to navigation Jump to search
Line 45: Line 45:
  md olibs\linden\indra
  md olibs\linden\indra
  md olibs\linden\indra\newview
  md olibs\linden\indra\newview
SVN folder tree - for simplicity of coping files to your build folder
  trunk\indra\newview
  trunk\libraries\i686-win32\include\GL
  trunk\libraries\i686-win32\include\quicktime
  trunk\libraries\i686-win32\lib\debug
  trunk\libraries\i686-win32\lib\release
           


=== Quicktime ===
=== Quicktime ===
Line 70: Line 78:
=== cares ===
=== cares ===
TBD
TBD


== Set up your source code tree ==
== Set up your source code tree ==

Revision as of 17:26, 18 April 2010

Open Source Portal

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.

Philosophy: to keep it brief, this page should only include steps we KNOW ARE NEEDED, not random hints. Extra details or open issues can go on the talk page.

Following this recipe 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.

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.

  • Install other development tools

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

SVN folder tree - for simplicity of coping files to your build folder
  trunk\indra\newview
  trunk\libraries\i686-win32\include\GL
  trunk\libraries\i686-win32\include\quicktime
  trunk\libraries\i686-win32\lib\debug
  trunk\libraries\i686-win32\lib\release

Quicktime

  • 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".

Fmod

  • 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"

Boost

  • Grab the files that Robin Cornelius has precompiled at

http://www.byteme.org.uk/downloads/boost_1_39_VC90_no_scl_shared_crt_static_link.zip

((TBD: verify, simplify, fix))

cares

TBD

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 ))
  • Copy your "olibs" from above into the source tree.

Downloads for SVN snapshoting software: 

TortoiseSVN:
   Home Page  : http://tortoisesvn.net/
   SourceForge:
       32-bit : TortoiseSVN-1.6.8.19260-win32-svn-1.6.11.msi
       64-bit : TortoiseSVN-1.6.8.19260-x64-svn-1.6.11.msi

If you use SVN snapshoting software I suggest actualy useing the same file tree as LL dose that way it will be easier to talk about some thing in a particular folder or file with your fellow builders.

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
    • Run "develop.py -G VC90" or "python develop.py -G VC90"
    • The develop.py script will create and populate a build directory for you. It should be in 'build-vc90'

((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)

Iteratively 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?))

References

These instructions are condensed from about a dozen previous pages of info:

((add other references here))

Retrieved from "https://wiki.secondlife.com/w/index.php?title=Viewer_2_Microsoft_Windows_Builds&oldid=869502"