Second Life Wiki - User contributions [en]

LlGetFreeMemory

2010-12-01T23:32:00Z

Apotheus Silverman: Fixed incorrect word in sample script

{{LSL_Function
|func_id=225|func_sleep=0.0|func_energy=10.0
|func=llGetFreeMemory
|return_type=integer
|func_desc
|Return_text=of the number of free bytes of memory the script can use.
|func_footer
|spec=
This function's behavior is dependent upon the VM the script is using. [[#Mono|Mono]] is the new VM, [[#LSO|LSO]] is the old VM. The big difference between between Mono and LSO is that Mono scripts run faster and can utilize four times more memory.

===Mono===

In Mono the value returned is the amount of free memory available to the script prior to garbage collection being run. This means that memory that is awaiting garbage collection counts against the scripts 64KiB allotment. In addition to this, Mono does not enforce the memory restrictions as strictly as the LSO VM did{{Footnote|http://www.langnetsymposium.com/2009/talks/17-JimPurbrick-SecondLife.html}} (with LSO it was impossible to exceed the 16KiB memory cap), consequently it is possible to utilize more of the free memory{{Footnote|In LSO, all types are immutable, every operation results in Heap values being duplicated, meaning <code>a = a + a;</code> resulting in 3 values of |In LSO, all types are immutable, every operation results in Heap values being duplicated, meaning a = a + a; resulting in 3 values of }}.

===LSO===

In LSO, the value returned by this function is the amount of memory that the Stack can use of the Heap has yet to allocate for itself.

The LSL memory space is divided into four sections: Byte-code, Stack, Free Memory, Heap. Free Memory isn't an allocated block of memory, it's just the space between Stack and Heap. The size of all four sections combined is 16384 bytes (16KiB).

[[String]]s, [[list]]s and [[key]]s are stored in the Heap. Heap pointers (for [[string]]s, [[list]]s & [[key]]s), [[integer]]s, [[float]]s, [[vector]]s and [[rotation]]s are all temporarily stored in the stack as the script executes.

As the script executes the Stack grows and shrinks in size depending upon the complexity of the expressions being executed. Likewise the Heap grows as the script executes but unlike the Stack, it never shrinks in size. When there is no free memory left for Stack or Heap to use they collide and a Stack-Heap Collision error is thrown causing the script to crash.

The Heap can become fragmented and blocks of memory in it can become unusable (due to their size). There is no defragment function{{Footnote|Due to the design of the LSO VM, a defragment function is impossible.}} but there are scripting techniques that can be used to reduce fragmentation.
|caveats=
*The number of free bytes the Heap can use may be greater but not less.
|constants
|examples=
Calling llGetFreeMemory can look like this:
<lsl>
integer free_memory = llGetFreeMemory();
llOwnerSay((string)free_memory + " bytes of free memory available for allocation.");
</lsl>
|helpers
|also_functions
|also_events
|also_tests
|also_articles
|notes=See also: the "Script run-time error" "Stack-Heap Collision" among the [[LSL Errors]]
|lso=This function does not count free memory, and the name of this function makes this function difficult for people to learn. People say this function may be redefined or superseded by another more useful function when the LSL VM moves to [[Mono]].

We can concisely specify llGetFreeMemory in the context of the classic Unix model for a parallel task/ thread/ process. Think of the task of the script always holding 16384 bytes (16 KiB). Let the byte code and then stack grow up from the bottom, let the heap grow down from the top. llGetFreeMemory then returns the "historic lowest heap pointer minus the stack end pointer".

llGetFreeMemory does not count the bytes freed, llGetFreeMemory instead counts all the bytes never yet used.
|cat1=Script
|cat2
|cat3
|cat4
}}

Viewer 2 Microsoft Windows Builds

2010-07-23T22:58:01Z

Apotheus Silverman: /* Boost */

{{multi-lang}}
{{CompileNav}}

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.

* Obtain Visual Studio (2005, 2008, 2010) (Express is OK)
** [http://www.microsoft.com/express/download/ Click here to download Visual C++ Express - current version is VS2010]
** Note: LL still uses VS2005 internally, which uses the VC80 libraries. VS2008 uses the VC90 libraries. VS2010 TBD (test with the VC90 libraries new ones for VC100 may need to be made).
* Install Microsoft Platform & DirectX SDKs
** Download and install [http://www.microsoft.com/downloads/details.aspx?FamilyID=F26B1AA4-741A-433A-9BE5-FA919850BDBF&displaylang=en Windows SDK for Windows Server 2008 and .NET Framework 3.5]
** Download and install [http://www.microsoft.com/downloads/details.aspx?FamilyID=ea4894b5-e98d-44f6-842d-e32147237638&DisplayLang=en DirectX SDK (August 2008)]

* Install other development tools
** '''UniCode NSIS'''([http://www.scratchpaper.com/home/downloads download Unicode NSIS])
*** This is the package installer used to build Setup.exe. Note: As of this writing the file is downloaded with an *.exec extension that needs renamed *.exe.--[[User:Nicky Perian|Nicky Perian]] 16:22, 30 March 2010 (UTC)
** '''CMake''' ([http://www.cmake.org/HTML/Download.html download CMake])
*** must be version 2.6.2 or higher (and ensure any older versions aren't in your PATH environment variables)
** '''Cygwin''' ([http://www.cygwin.com/ 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 [http://www.python.org/download/ Python.org Standard Python] or [http://www.activestate.com/Products/ActivePython/?mp=1 ActivePython]

*'''SVN software:'''(added by [[User:WolfPup Lowenhar|WolfPup Lowenhar]] 02:16, 19 April 2010 (UTC) )
**'''TortoiseSVN:''' http://tortoisesvn.net/
***'''Download Page:'''
****[http://tortoisesvn.net/downloads TortoiseSVN Downloads](contains link to 32-bit and 64-bit intsallers)

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

== 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
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 copying 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 [http://developer.apple.com/quicktime/download/ Quicktime SDK for Windows] (login may be necessary).
* copy "QuicktimeSDK\Libraries\QTMLClient.lib" to "olibs\linden\libraries\i686-win32\lib\release" and to "olibs\linden\libraries\i686-win32\lib\debug"
* Copy the contents of "QuicktimeSDK\CIncludes" into "olibs\linden\libraries\i686-win32\include\quicktime".

=== Fmod ===
* Download & extract [http://www.fmod.org/files/fmod3/fmodapi375win.zip FMOD3.75 API for Windows]. (later versions, like FMOD Ex, are incompatible).
* Copy "fmodapi375win\api\inc\fmod.h" to "olibs\linden\libraries\include"
* Copy "fmodapi375win\api\inc\fmod_errors.h" to "olibs\linden\libraries\include"
* Copy "fmodapi375win\api\inc\fmoddyn.h" to "olibs\linden\libraries\include"
* Copy "fmodapi375win\api\lib\fmodvc.lib" to "olibs\linden\libraries\i686-win32\lib\release" and to "olibs\linden\libraries\i686-win32\lib\debug"
* Copy "fmodapi375win\api\fmod.dll" to "olibs\linden\indra\newview"

=== Boost ===

Only needed if not using VS2005.

* 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
* If you get the zip file from Robin Cornelius copy the libraries folder into the the tree you made above for fmod and QuickTime files that way you have a ready back up of those files for if you update your build directory from the SVN server.
* or alternatively follow the instructions from the 25/Feb/10 and 15/Apr/10 entries of http://jira.secondlife.com/browse/VWR-9541

((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. A sugestion would be to use the same dev tree as LL as all folder names are short and do not have any spaces.

* Example: ((specific snapshot example TBD; SVN example also ))

* Copy your "olibs" from above into the source tree.

== Fix known problems with the source code tree ==

TBD - edits to scripts that must be made for windows VC90 builds to succeed?

Known Problems:
* /indra/cmake/Boost.cmake file has to be edited as shown in [http://jira.secondlife.com/browse/VWR-9541?focusedCommentId=168967&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_168967 VWR-9541] in order to use the boost files in VS2008.

== 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

*Get public tarballs(artwork and other needed files)[ added by [[User:WolfPup Lowenhar|WolfPup Lowenhar]] 03:16, 1 May 2010 (UTC) ]
** From the command line, '''cd into the trunk\scripts subdirectory'''
** Run <code>"python public_fetch_tarballs.py"</code>
** "trunk" should now have three LICENSE files in it.

* Run develop.py --
** From the command line, '''cd into the indra subdirectory'''
** Run <code>"develop.py -G VC90"</code> or <code>"python develop.py -G VC90"</code> NOTE: use <code> -G VC80 </code> if you are using VS2005
** The <code>develop.py</code> script will create and populate a build directory for you. It should be in <code>'build-vc90'</code> or <code>'build-vc80'</code> if using VS2005

((TBD: how to tell if you succeeded))

When it completes you will get your command prompt back and it should say something like:

Trying to set active config to "RelWithDebInfo"
Success!
Trying to set "secondlife-bin" to the startup project
Success!
got ret 0 from tools\vstool\VSTool.exe --solution build-VC80\SecondLife.sln --config RelWithDebInfo --startup secondlife-bin

== Compile using the IDE ==

* Run Visual Studio.
* Configure Visual Studio.
**Use Tools>Options to get the Options window open.
**Goto Projects and Solutions>VC++ Directories and set the following:
Executable Files:
$(SystemRoot)
$(SystemRoot)\System32
$(SystemRoot)\System32\wbem
$(VCInstallDir)bin
$(VCInstallDir)PlatformSDK\bin
$(VCInstallDir)PlatformSDK\common\bin
$(VSInstallDir)Common7\Tools\bin
$(VSInstallDir)Common7\tools
$(VSInstallDir)Common7\ide
$(ProgramFiles)\HTML Help Workshop
$(FrameworkSDKDir)bin
$(FrameworkDir)$(FrameworkVersion)
$(VSInstallDir)
C:\Program Files\Microsoft SDKs\Windows\v7.0\Bin
C:\Program Files\Microsoft SDKs\Windows\v6.1\Bin
C:\Python26
C:\Program Files\NSIS
$(SystemRoot)\SysWow64 (needed in Vista and 7 64-bit version)
$(FxCopDir)
$(PATH)
C:\cygwin\bin

Included Files:
$(VCInstallDir)include
$(VCInstallDir)atlmfc\include
$(VCInstallDir)PlatformSDK\include
$(VCInstallDir)PlatformSDK\common\include
$(FrameworkSDKDir)include
C:\Program Files\Microsoft SDKs\Windows\v7.0\Include
C:\Program Files\Microsoft SDKs\Windows\v7.0\Include\gl
C:\Program Files\Microsoft SDKs\Windows\v7.0\Samples\winui\TSF\tsfapp
C:\Program Files\Microsoft SDKs\Windows\v6.1\Include
C:\Program Files\Microsoft SDKs\Windows\v6.1\Include\gl
C:\Program Files\Microsoft SDKs\Windows\v6.1\Samples\winui\TSF\tsfapp
C:\Program Files\Microsoft DirectX SDK (February 2010)\Include

Library Files:
$(VCInstallDir)lib
$(VCInstallDir)atlmfc\lib
$(VCInstallDir)atlmfc\lib\i386
$(VCInstallDir)PlatformSDK\lib
$(VCInstallDir)PlatformSDK\common\lib
$(FrameworkSDKDir)lib
$(VSInstallDir)
$(VSInstallDir)lib
C:\Program Files\Microsoft SDKs\Windows\v7.0\Lib
C:\Program Files\Microsoft SDKs\Windows\v6.1\Lib
C:\Program Files\Microsoft DirectX SDK (February 2010)\Lib\x86

* 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.
* In the MSVS toolbar, just to the right of the triangular "Start Debugging" arrow, is a text box whose tooltip is "Solution Configurations". Select RelWithDebugInfo.
* If ALL_BUILD is not set as your StartUp Project (the StartUp Project is displayed in bold font), right-click on ALL_BUILD and choose "Set as StartUp Project".
* Right-click on ALL_BUILD and choose "Properties". In "Configuration Properties -> Debugging", find "Working Directory" and navigate to "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?))

* report your experiences, if useful, on the talk page, https://wiki.secondlife.com/wiki/Talk:Viewer_2_Microsoft_Windows_Builds
* ask for help on the SL "Snowglobe" group or the opensource-dev mailing list.

== Common Issues/Bugs/Glitches And Solutions ==
Applies to Visual C++ 2005 Express:
 
If you run into an issue when running develop.py similar to this:
 
1>Linking... 
1>link: extra operand `/ERRORREPORT:QUEUE' 
1>Try `link --help' for more information. 
1>Project : error PRJ0002 : Error result 1 returned from 'C:\cygwin\bin\link.exe'. 
 
You may have not configured Visual Studio properly. The articles in this wiki in regards to the setup of executable paths do not specify an order or priority, but you must make sure that the CYGWIN executable path is set lower in the list than the VC++ paths, otherwise develop.py winds up executing the CygWin Link.exe which won't work. 
This issue has also been seen when using the Windows Command Prompt instead of the command prompt within VC++ (Visual Studio 2010?).

== References ==

These instructions are condensed from about a dozen previous pages of info:
*https://wiki.secondlife.com/wiki/Microsoft_Windows_Builds
*https://wiki.secondlife.com/wiki/Compiling_the_Viewer_%28MSVS2008%29
*https://wiki.secondlife.com/wiki/User:Jodiah_Jensen#UPDATING_BOOST_LIBRARIES_TO_WORK_WITH_VS2008
** now partially incorrect
*http://jira.secondlife.com/browse/VWR-9541

((add other references here))

[[Category:Compiling viewer]]

Viewer 2 Microsoft Windows Builds

2010-07-22T20:34:35Z

Apotheus Silverman: /* Compile using the IDE */

{{multi-lang}}
{{CompileNav}}

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.

* Obtain Visual Studio (2005, 2008, 2010) (Express is OK)
** [http://www.microsoft.com/express/download/ Click here to download Visual C++ Express - current version is VS2010]
** Note: LL still uses VS2005 internally, which uses the VC80 libraries. VS2008 uses the VC90 libraries. VS2010 TBD (test with the VC90 libraries new ones for VC100 may need to be made).
* Install Microsoft Platform & DirectX SDKs
** Download and install [http://www.microsoft.com/downloads/details.aspx?FamilyID=F26B1AA4-741A-433A-9BE5-FA919850BDBF&displaylang=en Windows SDK for Windows Server 2008 and .NET Framework 3.5]
** Download and install [http://www.microsoft.com/downloads/details.aspx?FamilyID=ea4894b5-e98d-44f6-842d-e32147237638&DisplayLang=en DirectX SDK (August 2008)]

* Install other development tools
** '''UniCode NSIS'''([http://www.scratchpaper.com/home/downloads download Unicode NSIS])
*** This is the package installer used to build Setup.exe. Note: As of this writing the file is downloaded with an *.exec extension that needs renamed *.exe.--[[User:Nicky Perian|Nicky Perian]] 16:22, 30 March 2010 (UTC)
** '''CMake''' ([http://www.cmake.org/HTML/Download.html download CMake])
*** must be version 2.6.2 or higher (and ensure any older versions aren't in your PATH environment variables)
** '''Cygwin''' ([http://www.cygwin.com/ 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 [http://www.python.org/download/ Python.org Standard Python] or [http://www.activestate.com/Products/ActivePython/?mp=1 ActivePython]

*'''SVN software:'''(added by [[User:WolfPup Lowenhar|WolfPup Lowenhar]] 02:16, 19 April 2010 (UTC) )
**'''TortoiseSVN:''' http://tortoisesvn.net/
***'''Download Page:'''
****[http://tortoisesvn.net/downloads TortoiseSVN Downloads](contains link to 32-bit and 64-bit intsallers)

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

== 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
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 copying 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 [http://developer.apple.com/quicktime/download/ Quicktime SDK for Windows] (login may be necessary).
* copy "QuicktimeSDK\Libraries\QTMLClient.lib" to "olibs\linden\libraries\i686-win32\lib\release" and to "olibs\linden\libraries\i686-win32\lib\debug"
* Copy the contents of "QuicktimeSDK\CIncludes" into "olibs\linden\libraries\i686-win32\include\quicktime".

=== Fmod ===
* Download & extract [http://www.fmod.org/files/fmod3/fmodapi375win.zip FMOD3.75 API for Windows]. (later versions, like FMOD Ex, are incompatible).
* Copy "fmodapi375win\api\inc\fmod.h" to "olibs\linden\libraries\include"
* Copy "fmodapi375win\api\inc\fmod_errors.h" to "olibs\linden\libraries\include"
* Copy "fmodapi375win\api\inc\fmoddyn.h" to "olibs\linden\libraries\include"
* Copy "fmodapi375win\api\lib\fmodvc.lib" to "olibs\linden\libraries\i686-win32\lib\release" and to "olibs\linden\libraries\i686-win32\lib\debug"
* Copy "fmodapi375win\api\fmod.dll" to "olibs\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
* If you get the zip file from Robin Cornelius copy the libraries folder into the the tree you made above for fmod and QuickTime files that way you have a ready back up of those files for if you update your build directory from the SVN server.
* or alternatively follow the instructions from the 25/Feb/10 and 15/Apr/10 entries of http://jira.secondlife.com/browse/VWR-9541

((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. A sugestion would be to use the same dev tree as LL as all folder names are short and do not have any spaces.

* Example: ((specific snapshot example TBD; SVN example also ))

* Copy your "olibs" from above into the source tree.

== Fix known problems with the source code tree ==

TBD - edits to scripts that must be made for windows VC90 builds to succeed?

Known Problems:
* /indra/cmake/Boost.cmake file has to be edited as shown in [http://jira.secondlife.com/browse/VWR-9541?focusedCommentId=168967&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_168967 VWR-9541] in order to use the boost files in VS2008.

== 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

*Get public tarballs(artwork and other needed files)[ added by [[User:WolfPup Lowenhar|WolfPup Lowenhar]] 03:16, 1 May 2010 (UTC) ]
** From the command line, '''cd into the trunk\scripts subdirectory'''
** Run <code>"python public_fetch_tarballs.py"</code>
** "trunk" should now have three LICENSE files in it.

* Run develop.py --
** From the command line, '''cd into the indra subdirectory'''
** Run <code>"develop.py -G VC90"</code> or <code>"python develop.py -G VC90"</code> NOTE: use <code> -G VC80 </code> if you are using VS2005
** The <code>develop.py</code> script will create and populate a build directory for you. It should be in <code>'build-vc90'</code> or <code>'build-vc80'</code> if using VS2005

((TBD: how to tell if you succeeded))

When it completes you will get your command prompt back and it should say something like:

Trying to set active config to "RelWithDebInfo"
Success!
Trying to set "secondlife-bin" to the startup project
Success!
got ret 0 from tools\vstool\VSTool.exe --solution build-VC80\SecondLife.sln --config RelWithDebInfo --startup secondlife-bin

== Compile using the IDE ==

* Run Visual Studio.
* Configure Visual Studio.
**Use Tools>Options to get the Options window open.
**Goto Projects and Solutions>VC++ Directories and set the following:
Executable Files:
$(SystemRoot)
$(SystemRoot)\System32
$(SystemRoot)\System32\wbem
$(VCInstallDir)bin
$(VCInstallDir)PlatformSDK\bin
$(VCInstallDir)PlatformSDK\common\bin
$(VSInstallDir)Common7\Tools\bin
$(VSInstallDir)Common7\tools
$(VSInstallDir)Common7\ide
$(ProgramFiles)\HTML Help Workshop
$(FrameworkSDKDir)bin
$(FrameworkDir)$(FrameworkVersion)
$(VSInstallDir)
C:\Program Files\Microsoft SDKs\Windows\v7.0\Bin
C:\Program Files\Microsoft SDKs\Windows\v6.1\Bin
C:\Python26
C:\Program Files\NSIS
$(SystemRoot)\SysWow64 (needed in Vista and 7 64-bit version)
$(FxCopDir)
$(PATH)
C:\cygwin\bin

Included Files:
$(VCInstallDir)include
$(VCInstallDir)atlmfc\include
$(VCInstallDir)PlatformSDK\include
$(VCInstallDir)PlatformSDK\common\include
$(FrameworkSDKDir)include
C:\Program Files\Microsoft SDKs\Windows\v7.0\Include
C:\Program Files\Microsoft SDKs\Windows\v7.0\Include\gl
C:\Program Files\Microsoft SDKs\Windows\v7.0\Samples\winui\TSF\tsfapp
C:\Program Files\Microsoft SDKs\Windows\v6.1\Include
C:\Program Files\Microsoft SDKs\Windows\v6.1\Include\gl
C:\Program Files\Microsoft SDKs\Windows\v6.1\Samples\winui\TSF\tsfapp
C:\Program Files\Microsoft DirectX SDK (February 2010)\Include

Library Files:
$(VCInstallDir)lib
$(VCInstallDir)atlmfc\lib
$(VCInstallDir)atlmfc\lib\i386
$(VCInstallDir)PlatformSDK\lib
$(VCInstallDir)PlatformSDK\common\lib
$(FrameworkSDKDir)lib
$(VSInstallDir)
$(VSInstallDir)lib
C:\Program Files\Microsoft SDKs\Windows\v7.0\Lib
C:\Program Files\Microsoft SDKs\Windows\v6.1\Lib
C:\Program Files\Microsoft DirectX SDK (February 2010)\Lib\x86

* 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.
* In the MSVS toolbar, just to the right of the triangular "Start Debugging" arrow, is a text box whose tooltip is "Solution Configurations". Select RelWithDebugInfo.
* If ALL_BUILD is not set as your StartUp Project (the StartUp Project is displayed in bold font), right-click on ALL_BUILD and choose "Set as StartUp Project".
* Right-click on ALL_BUILD and choose "Properties". In "Configuration Properties -> Debugging", find "Working Directory" and navigate to "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?))

* report your experiences, if useful, on the talk page, https://wiki.secondlife.com/wiki/Talk:Viewer_2_Microsoft_Windows_Builds
* ask for help on the SL "Snowglobe" group or the opensource-dev mailing list.

== Common Issues/Bugs/Glitches And Solutions ==
Applies to Visual C++ 2005 Express:
 
If you run into an issue when running develop.py similar to this:
 
1>Linking... 
1>link: extra operand `/ERRORREPORT:QUEUE' 
1>Try `link --help' for more information. 
1>Project : error PRJ0002 : Error result 1 returned from 'C:\cygwin\bin\link.exe'. 
 
You may have not configured Visual Studio properly. The articles in this wiki in regards to the setup of executable paths do not specify an order or priority, but you must make sure that the CYGWIN executable path is set lower in the list than the VC++ paths, otherwise develop.py winds up executing the CygWin Link.exe which won't work. 
This issue has also been seen when using the Windows Command Prompt instead of the command prompt within VC++ (Visual Studio 2010?).

== References ==

These instructions are condensed from about a dozen previous pages of info:
*https://wiki.secondlife.com/wiki/Microsoft_Windows_Builds
*https://wiki.secondlife.com/wiki/Compiling_the_Viewer_%28MSVS2008%29
*https://wiki.secondlife.com/wiki/User:Jodiah_Jensen#UPDATING_BOOST_LIBRARIES_TO_WORK_WITH_VS2008
** now partially incorrect
*http://jira.secondlife.com/browse/VWR-9541

((add other references here))

[[Category:Compiling viewer]]

Viewer 2 Microsoft Windows Builds

2010-07-22T18:33:29Z

Apotheus Silverman: /* Fix known problems with the source code tree */

{{multi-lang}}
{{CompileNav}}

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.

* Obtain Visual Studio (2005, 2008, 2010) (Express is OK)
** [http://www.microsoft.com/express/download/ Click here to download Visual C++ Express - current version is VS2010]
** Note: LL still uses VS2005 internally, which uses the VC80 libraries. VS2008 uses the VC90 libraries. VS2010 TBD (test with the VC90 libraries new ones for VC100 may need to be made).
* Install Microsoft Platform & DirectX SDKs
** Download and install [http://www.microsoft.com/downloads/details.aspx?FamilyID=F26B1AA4-741A-433A-9BE5-FA919850BDBF&displaylang=en Windows SDK for Windows Server 2008 and .NET Framework 3.5]
** Download and install [http://www.microsoft.com/downloads/details.aspx?FamilyID=ea4894b5-e98d-44f6-842d-e32147237638&DisplayLang=en DirectX SDK (August 2008)]

* Install other development tools
** '''UniCode NSIS'''([http://www.scratchpaper.com/home/downloads download Unicode NSIS])
*** This is the package installer used to build Setup.exe. Note: As of this writing the file is downloaded with an *.exec extension that needs renamed *.exe.--[[User:Nicky Perian|Nicky Perian]] 16:22, 30 March 2010 (UTC)
** '''CMake''' ([http://www.cmake.org/HTML/Download.html download CMake])
*** must be version 2.6.2 or higher (and ensure any older versions aren't in your PATH environment variables)
** '''Cygwin''' ([http://www.cygwin.com/ 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 [http://www.python.org/download/ Python.org Standard Python] or [http://www.activestate.com/Products/ActivePython/?mp=1 ActivePython]

*'''SVN software:'''(added by [[User:WolfPup Lowenhar|WolfPup Lowenhar]] 02:16, 19 April 2010 (UTC) )
**'''TortoiseSVN:''' http://tortoisesvn.net/
***'''Download Page:'''
****[http://tortoisesvn.net/downloads TortoiseSVN Downloads](contains link to 32-bit and 64-bit intsallers)

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

== 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
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 copying 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 [http://developer.apple.com/quicktime/download/ Quicktime SDK for Windows] (login may be necessary).
* copy "QuicktimeSDK\Libraries\QTMLClient.lib" to "olibs\linden\libraries\i686-win32\lib\release" and to "olibs\linden\libraries\i686-win32\lib\debug"
* Copy the contents of "QuicktimeSDK\CIncludes" into "olibs\linden\libraries\i686-win32\include\quicktime".

=== Fmod ===
* Download & extract [http://www.fmod.org/files/fmod3/fmodapi375win.zip FMOD3.75 API for Windows]. (later versions, like FMOD Ex, are incompatible).
* Copy "fmodapi375win\api\inc\fmod.h" to "olibs\linden\libraries\include"
* Copy "fmodapi375win\api\inc\fmod_errors.h" to "olibs\linden\libraries\include"
* Copy "fmodapi375win\api\inc\fmoddyn.h" to "olibs\linden\libraries\include"
* Copy "fmodapi375win\api\lib\fmodvc.lib" to "olibs\linden\libraries\i686-win32\lib\release" and to "olibs\linden\libraries\i686-win32\lib\debug"
* Copy "fmodapi375win\api\fmod.dll" to "olibs\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
* If you get the zip file from Robin Cornelius copy the libraries folder into the the tree you made above for fmod and QuickTime files that way you have a ready back up of those files for if you update your build directory from the SVN server.
* or alternatively follow the instructions from the 25/Feb/10 and 15/Apr/10 entries of http://jira.secondlife.com/browse/VWR-9541

((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. A sugestion would be to use the same dev tree as LL as all folder names are short and do not have any spaces.

* Example: ((specific snapshot example TBD; SVN example also ))

* Copy your "olibs" from above into the source tree.

== Fix known problems with the source code tree ==

TBD - edits to scripts that must be made for windows VC90 builds to succeed?

Known Problems:
* /indra/cmake/Boost.cmake file has to be edited as shown in [http://jira.secondlife.com/browse/VWR-9541?focusedCommentId=168967&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_168967 VWR-9541] in order to use the boost files in VS2008.

== 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

*Get public tarballs(artwork and other needed files)[ added by [[User:WolfPup Lowenhar|WolfPup Lowenhar]] 03:16, 1 May 2010 (UTC) ]
** From the command line, '''cd into the trunk\scripts subdirectory'''
** Run <code>"python public_fetch_tarballs.py"</code>
** "trunk" should now have three LICENSE files in it.

* Run develop.py --
** From the command line, '''cd into the indra subdirectory'''
** Run <code>"develop.py -G VC90"</code> or <code>"python develop.py -G VC90"</code> NOTE: use <code> -G VC80 </code> if you are using VS2005
** The <code>develop.py</code> script will create and populate a build directory for you. It should be in <code>'build-vc90'</code> or <code>'build-vc80'</code> if using VS2005

((TBD: how to tell if you succeeded))

When it completes you will get your command prompt back and it should say something like:

Trying to set active config to "RelWithDebInfo"
Success!
Trying to set "secondlife-bin" to the startup project
Success!
got ret 0 from tools\vstool\VSTool.exe --solution build-VC80\SecondLife.sln --config RelWithDebInfo --startup secondlife-bin

== Compile using the IDE ==

* Run Visual Studio.
* Configure Visual Stidio.
**Use Tools>Options to get the Options window open.
**Goto Projects and Solutions>VC++ Directories and set the following:
Executable Files:
$(SystemRoot)
$(SystemRoot)\System32
$(SystemRoot)\System32\wbem
$(VCInstallDir)bin
$(VCInstallDir)PlatformSDK\bin
$(VCInstallDir)PlatformSDK\common\bin
$(VSInstallDir)Common7\Tools\bin
$(VSInstallDir)Common7\tools
$(VSInstallDir)Common7\ide
$(ProgramFiles)\HTML Help Workshop
$(FrameworkSDKDir)bin
$(FrameworkDir)$(FrameworkVersion)
$(VSInstallDir)
C:\Program Files\Microsoft SDKs\Windows\v7.0\Bin
C:\Program Files\Microsoft SDKs\Windows\v6.1\Bin
C:\Python26
C:\Program Files\NSIS
$(SystemRoot)\SysWow64 (needed in Vista and 7 64-bit version)
$(FxCopDir)
$(PATH)
C:\cygwin\bin

Included Files:
$(VCInstallDir)include
$(VCInstallDir)atlmfc\include
$(VCInstallDir)PlatformSDK\include
$(VCInstallDir)PlatformSDK\common\include
$(FrameworkSDKDir)include
C:\Program Files\Microsoft SDKs\Windows\v7.0\Include
C:\Program Files\Microsoft SDKs\Windows\v7.0\Include\gl
C:\Program Files\Microsoft SDKs\Windows\v7.0\Samples\winui\TSF\tsfapp
C:\Program Files\Microsoft SDKs\Windows\v6.1\Include
C:\Program Files\Microsoft SDKs\Windows\v6.1\Include\gl
C:\Program Files\Microsoft SDKs\Windows\v6.1\Samples\winui\TSF\tsfapp
C:\Program Files\Microsoft DirectX SDK (February 2010)\Include

Library Files:
$(VCInstallDir)lib
$(VCInstallDir)atlmfc\lib
$(VCInstallDir)atlmfc\lib\i386
$(VCInstallDir)PlatformSDK\lib
$(VCInstallDir)PlatformSDK\common\lib
$(FrameworkSDKDir)lib
$(VSInstallDir)
$(VSInstallDir)lib
C:\Program Files\Microsoft SDKs\Windows\v7.0\Lib
C:\Program Files\Microsoft SDKs\Windows\v6.1\Lib
C:\Program Files\Microsoft DirectX SDK (February 2010)\Lib\x86

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

* report your experiences, if useful, on the talk page, https://wiki.secondlife.com/wiki/Talk:Viewer_2_Microsoft_Windows_Builds
* ask for help on the SL "Snowglobe" group or the opensource-dev mailing list.

== Common Issues/Bugs/Glitches And Solutions ==
Applies to Visual C++ 2005 Express:
 
If you run into an issue when running develop.py similar to this:
 
1>Linking... 
1>link: extra operand `/ERRORREPORT:QUEUE' 
1>Try `link --help' for more information. 
1>Project : error PRJ0002 : Error result 1 returned from 'C:\cygwin\bin\link.exe'. 
 
You may have not configured Visual Studio properly. The articles in this wiki in regards to the setup of executable paths do not specify an order or priority, but you must make sure that the CYGWIN executable path is set lower in the list than the VC++ paths, otherwise develop.py winds up executing the CygWin Link.exe which won't work. 
This issue has also been seen when using the Windows Command Prompt instead of the command prompt within VC++ (Visual Studio 2010?).

== References ==

These instructions are condensed from about a dozen previous pages of info:
*https://wiki.secondlife.com/wiki/Microsoft_Windows_Builds
*https://wiki.secondlife.com/wiki/Compiling_the_Viewer_%28MSVS2008%29
*https://wiki.secondlife.com/wiki/User:Jodiah_Jensen#UPDATING_BOOST_LIBRARIES_TO_WORK_WITH_VS2008
** now partially incorrect
*http://jira.secondlife.com/browse/VWR-9541

((add other references here))

[[Category:Compiling viewer]]

Viewer 2 Microsoft Windows Builds

2010-07-22T18:16:32Z

Apotheus Silverman: /* Fmod */

{{multi-lang}}
{{CompileNav}}

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.

* Obtain Visual Studio (2005, 2008, 2010) (Express is OK)
** [http://www.microsoft.com/express/download/ Click here to download Visual C++ Express - current version is VS2010]
** Note: LL still uses VS2005 internally, which uses the VC80 libraries. VS2008 uses the VC90 libraries. VS2010 TBD (test with the VC90 libraries new ones for VC100 may need to be made).
* Install Microsoft Platform & DirectX SDKs
** Download and install [http://www.microsoft.com/downloads/details.aspx?FamilyID=F26B1AA4-741A-433A-9BE5-FA919850BDBF&displaylang=en Windows SDK for Windows Server 2008 and .NET Framework 3.5]
** Download and install [http://www.microsoft.com/downloads/details.aspx?FamilyID=ea4894b5-e98d-44f6-842d-e32147237638&DisplayLang=en DirectX SDK (August 2008)]

* Install other development tools
** '''UniCode NSIS'''([http://www.scratchpaper.com/home/downloads download Unicode NSIS])
*** This is the package installer used to build Setup.exe. Note: As of this writing the file is downloaded with an *.exec extension that needs renamed *.exe.--[[User:Nicky Perian|Nicky Perian]] 16:22, 30 March 2010 (UTC)
** '''CMake''' ([http://www.cmake.org/HTML/Download.html download CMake])
*** must be version 2.6.2 or higher (and ensure any older versions aren't in your PATH environment variables)
** '''Cygwin''' ([http://www.cygwin.com/ 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 [http://www.python.org/download/ Python.org Standard Python] or [http://www.activestate.com/Products/ActivePython/?mp=1 ActivePython]

*'''SVN software:'''(added by [[User:WolfPup Lowenhar|WolfPup Lowenhar]] 02:16, 19 April 2010 (UTC) )
**'''TortoiseSVN:''' http://tortoisesvn.net/
***'''Download Page:'''
****[http://tortoisesvn.net/downloads TortoiseSVN Downloads](contains link to 32-bit and 64-bit intsallers)

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

== 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
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 copying 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 [http://developer.apple.com/quicktime/download/ Quicktime SDK for Windows] (login may be necessary).
* copy "QuicktimeSDK\Libraries\QTMLClient.lib" to "olibs\linden\libraries\i686-win32\lib\release" and to "olibs\linden\libraries\i686-win32\lib\debug"
* Copy the contents of "QuicktimeSDK\CIncludes" into "olibs\linden\libraries\i686-win32\include\quicktime".

=== Fmod ===
* Download & extract [http://www.fmod.org/files/fmod3/fmodapi375win.zip FMOD3.75 API for Windows]. (later versions, like FMOD Ex, are incompatible).
* Copy "fmodapi375win\api\inc\fmod.h" to "olibs\linden\libraries\include"
* Copy "fmodapi375win\api\inc\fmod_errors.h" to "olibs\linden\libraries\include"
* Copy "fmodapi375win\api\inc\fmoddyn.h" to "olibs\linden\libraries\include"
* Copy "fmodapi375win\api\lib\fmodvc.lib" to "olibs\linden\libraries\i686-win32\lib\release" and to "olibs\linden\libraries\i686-win32\lib\debug"
* Copy "fmodapi375win\api\fmod.dll" to "olibs\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
* If you get the zip file from Robin Cornelius copy the libraries folder into the the tree you made above for fmod and QuickTime files that way you have a ready back up of those files for if you update your build directory from the SVN server.
* or alternatively follow the instructions from the 25/Feb/10 and 15/Apr/10 entries of http://jira.secondlife.com/browse/VWR-9541

((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. A sugestion would be to use the same dev tree as LL as all folder names are short and do not have any spaces.

* Example: ((specific snapshot example TBD; SVN example also ))

* Copy your "olibs" from above into the source tree.

== Fix known problems with the source code tree ==

TBD - edits to scripts that must be made for windows VC90 builds to succeed?

Known Problems:
* boost.make file has to be edited as shown in the JIRA mentioned in the above section in order to use the boost files in VS2008.

== 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

*Get public tarballs(artwork and other needed files)[ added by [[User:WolfPup Lowenhar|WolfPup Lowenhar]] 03:16, 1 May 2010 (UTC) ]
** From the command line, '''cd into the trunk\scripts subdirectory'''
** Run <code>"python public_fetch_tarballs.py"</code>
** "trunk" should now have three LICENSE files in it.

* Run develop.py --
** From the command line, '''cd into the indra subdirectory'''
** Run <code>"develop.py -G VC90"</code> or <code>"python develop.py -G VC90"</code> NOTE: use <code> -G VC80 </code> if you are using VS2005
** The <code>develop.py</code> script will create and populate a build directory for you. It should be in <code>'build-vc90'</code> or <code>'build-vc80'</code> if using VS2005

((TBD: how to tell if you succeeded))

When it completes you will get your command prompt back and it should say something like:

Trying to set active config to "RelWithDebInfo"
Success!
Trying to set "secondlife-bin" to the startup project
Success!
got ret 0 from tools\vstool\VSTool.exe --solution build-VC80\SecondLife.sln --config RelWithDebInfo --startup secondlife-bin

== Compile using the IDE ==

* Run Visual Studio.
* Configure Visual Stidio.
**Use Tools>Options to get the Options window open.
**Goto Projects and Solutions>VC++ Directories and set the following:
Executable Files:
$(SystemRoot)
$(SystemRoot)\System32
$(SystemRoot)\System32\wbem
$(VCInstallDir)bin
$(VCInstallDir)PlatformSDK\bin
$(VCInstallDir)PlatformSDK\common\bin
$(VSInstallDir)Common7\Tools\bin
$(VSInstallDir)Common7\tools
$(VSInstallDir)Common7\ide
$(ProgramFiles)\HTML Help Workshop
$(FrameworkSDKDir)bin
$(FrameworkDir)$(FrameworkVersion)
$(VSInstallDir)
C:\Program Files\Microsoft SDKs\Windows\v7.0\Bin
C:\Program Files\Microsoft SDKs\Windows\v6.1\Bin
C:\Python26
C:\Program Files\NSIS
$(SystemRoot)\SysWow64 (needed in Vista and 7 64-bit version)
$(FxCopDir)
$(PATH)
C:\cygwin\bin

Included Files:
$(VCInstallDir)include
$(VCInstallDir)atlmfc\include
$(VCInstallDir)PlatformSDK\include
$(VCInstallDir)PlatformSDK\common\include
$(FrameworkSDKDir)include
C:\Program Files\Microsoft SDKs\Windows\v7.0\Include
C:\Program Files\Microsoft SDKs\Windows\v7.0\Include\gl
C:\Program Files\Microsoft SDKs\Windows\v7.0\Samples\winui\TSF\tsfapp
C:\Program Files\Microsoft SDKs\Windows\v6.1\Include
C:\Program Files\Microsoft SDKs\Windows\v6.1\Include\gl
C:\Program Files\Microsoft SDKs\Windows\v6.1\Samples\winui\TSF\tsfapp
C:\Program Files\Microsoft DirectX SDK (February 2010)\Include

Library Files:
$(VCInstallDir)lib
$(VCInstallDir)atlmfc\lib
$(VCInstallDir)atlmfc\lib\i386
$(VCInstallDir)PlatformSDK\lib
$(VCInstallDir)PlatformSDK\common\lib
$(FrameworkSDKDir)lib
$(VSInstallDir)
$(VSInstallDir)lib
C:\Program Files\Microsoft SDKs\Windows\v7.0\Lib
C:\Program Files\Microsoft SDKs\Windows\v6.1\Lib
C:\Program Files\Microsoft DirectX SDK (February 2010)\Lib\x86

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

* report your experiences, if useful, on the talk page, https://wiki.secondlife.com/wiki/Talk:Viewer_2_Microsoft_Windows_Builds
* ask for help on the SL "Snowglobe" group or the opensource-dev mailing list.

== Common Issues/Bugs/Glitches And Solutions ==
Applies to Visual C++ 2005 Express:
 
If you run into an issue when running develop.py similar to this:
 
1>Linking... 
1>link: extra operand `/ERRORREPORT:QUEUE' 
1>Try `link --help' for more information. 
1>Project : error PRJ0002 : Error result 1 returned from 'C:\cygwin\bin\link.exe'. 
 
You may have not configured Visual Studio properly. The articles in this wiki in regards to the setup of executable paths do not specify an order or priority, but you must make sure that the CYGWIN executable path is set lower in the list than the VC++ paths, otherwise develop.py winds up executing the CygWin Link.exe which won't work. 
This issue has also been seen when using the Windows Command Prompt instead of the command prompt within VC++ (Visual Studio 2010?).

== References ==

These instructions are condensed from about a dozen previous pages of info:
*https://wiki.secondlife.com/wiki/Microsoft_Windows_Builds
*https://wiki.secondlife.com/wiki/Compiling_the_Viewer_%28MSVS2008%29
*https://wiki.secondlife.com/wiki/User:Jodiah_Jensen#UPDATING_BOOST_LIBRARIES_TO_WORK_WITH_VS2008
** now partially incorrect
*http://jira.secondlife.com/browse/VWR-9541

((add other references here))

[[Category:Compiling viewer]]

Viewer 2 Microsoft Windows Builds

2010-07-22T18:14:36Z

Apotheus Silverman: /* Quicktime */

{{multi-lang}}
{{CompileNav}}

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.

* Obtain Visual Studio (2005, 2008, 2010) (Express is OK)
** [http://www.microsoft.com/express/download/ Click here to download Visual C++ Express - current version is VS2010]
** Note: LL still uses VS2005 internally, which uses the VC80 libraries. VS2008 uses the VC90 libraries. VS2010 TBD (test with the VC90 libraries new ones for VC100 may need to be made).
* Install Microsoft Platform & DirectX SDKs
** Download and install [http://www.microsoft.com/downloads/details.aspx?FamilyID=F26B1AA4-741A-433A-9BE5-FA919850BDBF&displaylang=en Windows SDK for Windows Server 2008 and .NET Framework 3.5]
** Download and install [http://www.microsoft.com/downloads/details.aspx?FamilyID=ea4894b5-e98d-44f6-842d-e32147237638&DisplayLang=en DirectX SDK (August 2008)]

* Install other development tools
** '''UniCode NSIS'''([http://www.scratchpaper.com/home/downloads download Unicode NSIS])
*** This is the package installer used to build Setup.exe. Note: As of this writing the file is downloaded with an *.exec extension that needs renamed *.exe.--[[User:Nicky Perian|Nicky Perian]] 16:22, 30 March 2010 (UTC)
** '''CMake''' ([http://www.cmake.org/HTML/Download.html download CMake])
*** must be version 2.6.2 or higher (and ensure any older versions aren't in your PATH environment variables)
** '''Cygwin''' ([http://www.cygwin.com/ 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 [http://www.python.org/download/ Python.org Standard Python] or [http://www.activestate.com/Products/ActivePython/?mp=1 ActivePython]

*'''SVN software:'''(added by [[User:WolfPup Lowenhar|WolfPup Lowenhar]] 02:16, 19 April 2010 (UTC) )
**'''TortoiseSVN:''' http://tortoisesvn.net/
***'''Download Page:'''
****[http://tortoisesvn.net/downloads TortoiseSVN Downloads](contains link to 32-bit and 64-bit intsallers)

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

== 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
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 copying 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 [http://developer.apple.com/quicktime/download/ Quicktime SDK for Windows] (login may be necessary).
* copy "QuicktimeSDK\Libraries\QTMLClient.lib" to "olibs\linden\libraries\i686-win32\lib\release" and to "olibs\linden\libraries\i686-win32\lib\debug"
* Copy the contents of "QuicktimeSDK\CIncludes" into "olibs\linden\libraries\i686-win32\include\quicktime".

=== Fmod ===
* Download & extract [http://www.fmod.org/files/fmod3/fmodapi375win.zip 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
* If you get the zip file from Robin Cornelius copy the libraries folder into the the tree you made above for fmod and QuickTime files that way you have a ready back up of those files for if you update your build directory from the SVN server.
* or alternatively follow the instructions from the 25/Feb/10 and 15/Apr/10 entries of http://jira.secondlife.com/browse/VWR-9541

((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. A sugestion would be to use the same dev tree as LL as all folder names are short and do not have any spaces.

* Example: ((specific snapshot example TBD; SVN example also ))

* Copy your "olibs" from above into the source tree.

== Fix known problems with the source code tree ==

TBD - edits to scripts that must be made for windows VC90 builds to succeed?

Known Problems:
* boost.make file has to be edited as shown in the JIRA mentioned in the above section in order to use the boost files in VS2008.

== 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

*Get public tarballs(artwork and other needed files)[ added by [[User:WolfPup Lowenhar|WolfPup Lowenhar]] 03:16, 1 May 2010 (UTC) ]
** From the command line, '''cd into the trunk\scripts subdirectory'''
** Run <code>"python public_fetch_tarballs.py"</code>
** "trunk" should now have three LICENSE files in it.

* Run develop.py --
** From the command line, '''cd into the indra subdirectory'''
** Run <code>"develop.py -G VC90"</code> or <code>"python develop.py -G VC90"</code> NOTE: use <code> -G VC80 </code> if you are using VS2005
** The <code>develop.py</code> script will create and populate a build directory for you. It should be in <code>'build-vc90'</code> or <code>'build-vc80'</code> if using VS2005

((TBD: how to tell if you succeeded))

When it completes you will get your command prompt back and it should say something like:

Trying to set active config to "RelWithDebInfo"
Success!
Trying to set "secondlife-bin" to the startup project
Success!
got ret 0 from tools\vstool\VSTool.exe --solution build-VC80\SecondLife.sln --config RelWithDebInfo --startup secondlife-bin

== Compile using the IDE ==

* Run Visual Studio.
* Configure Visual Stidio.
**Use Tools>Options to get the Options window open.
**Goto Projects and Solutions>VC++ Directories and set the following:
Executable Files:
$(SystemRoot)
$(SystemRoot)\System32
$(SystemRoot)\System32\wbem
$(VCInstallDir)bin
$(VCInstallDir)PlatformSDK\bin
$(VCInstallDir)PlatformSDK\common\bin
$(VSInstallDir)Common7\Tools\bin
$(VSInstallDir)Common7\tools
$(VSInstallDir)Common7\ide
$(ProgramFiles)\HTML Help Workshop
$(FrameworkSDKDir)bin
$(FrameworkDir)$(FrameworkVersion)
$(VSInstallDir)
C:\Program Files\Microsoft SDKs\Windows\v7.0\Bin
C:\Program Files\Microsoft SDKs\Windows\v6.1\Bin
C:\Python26
C:\Program Files\NSIS
$(SystemRoot)\SysWow64 (needed in Vista and 7 64-bit version)
$(FxCopDir)
$(PATH)
C:\cygwin\bin

Included Files:
$(VCInstallDir)include
$(VCInstallDir)atlmfc\include
$(VCInstallDir)PlatformSDK\include
$(VCInstallDir)PlatformSDK\common\include
$(FrameworkSDKDir)include
C:\Program Files\Microsoft SDKs\Windows\v7.0\Include
C:\Program Files\Microsoft SDKs\Windows\v7.0\Include\gl
C:\Program Files\Microsoft SDKs\Windows\v7.0\Samples\winui\TSF\tsfapp
C:\Program Files\Microsoft SDKs\Windows\v6.1\Include
C:\Program Files\Microsoft SDKs\Windows\v6.1\Include\gl
C:\Program Files\Microsoft SDKs\Windows\v6.1\Samples\winui\TSF\tsfapp
C:\Program Files\Microsoft DirectX SDK (February 2010)\Include

Library Files:
$(VCInstallDir)lib
$(VCInstallDir)atlmfc\lib
$(VCInstallDir)atlmfc\lib\i386
$(VCInstallDir)PlatformSDK\lib
$(VCInstallDir)PlatformSDK\common\lib
$(FrameworkSDKDir)lib
$(VSInstallDir)
$(VSInstallDir)lib
C:\Program Files\Microsoft SDKs\Windows\v7.0\Lib
C:\Program Files\Microsoft SDKs\Windows\v6.1\Lib
C:\Program Files\Microsoft DirectX SDK (February 2010)\Lib\x86

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

* report your experiences, if useful, on the talk page, https://wiki.secondlife.com/wiki/Talk:Viewer_2_Microsoft_Windows_Builds
* ask for help on the SL "Snowglobe" group or the opensource-dev mailing list.

== Common Issues/Bugs/Glitches And Solutions ==
Applies to Visual C++ 2005 Express:
 
If you run into an issue when running develop.py similar to this:
 
1>Linking... 
1>link: extra operand `/ERRORREPORT:QUEUE' 
1>Try `link --help' for more information. 
1>Project : error PRJ0002 : Error result 1 returned from 'C:\cygwin\bin\link.exe'. 
 
You may have not configured Visual Studio properly. The articles in this wiki in regards to the setup of executable paths do not specify an order or priority, but you must make sure that the CYGWIN executable path is set lower in the list than the VC++ paths, otherwise develop.py winds up executing the CygWin Link.exe which won't work. 
This issue has also been seen when using the Windows Command Prompt instead of the command prompt within VC++ (Visual Studio 2010?).

== References ==

These instructions are condensed from about a dozen previous pages of info:
*https://wiki.secondlife.com/wiki/Microsoft_Windows_Builds
*https://wiki.secondlife.com/wiki/Compiling_the_Viewer_%28MSVS2008%29
*https://wiki.secondlife.com/wiki/User:Jodiah_Jensen#UPDATING_BOOST_LIBRARIES_TO_WORK_WITH_VS2008
** now partially incorrect
*http://jira.secondlife.com/browse/VWR-9541

((add other references here))

[[Category:Compiling viewer]]

Talk:LlHTTPRequest

2008-10-15T19:13:15Z

Apotheus Silverman: New section: HTTP_VERIFY_CERT behavior clarification

I have a Question ..
Does POST work ?
I couldnt get it working
Anylyn Hax 13:34, 28 July 2007 (PDT)

The following headers will be present, usable by scripts running on the HTTP server if the scripting language allows you to access the headers.

An PHP example on how to check to see if the call came from the main grid:
<?php
if ($_SERVER["HTTP_X_SECONDLIFE_SHARD"] == "Production") {
echo 'You are using the main grid';
} else {
echo 'You are not using the main grid';
}
?>

== Odd format for header names ==

Why are the headers listed as HTTP_SOME_HEADER_NAME, when the sent headers are in the format Some-Header-Name? Is there some benefit to putting false values that match conventions used by CGI, but aren't actually correct?
* This is because you are looking at a global property with a lot more information than just headers. Some functions like listed below handle the stripping of the HTTP_ information, but you could also just use substr to remove the HTTP_ [[User:Wouter Hobble|Wouter Hobble]] - 4 July 2008

I am aware that the example given above works, but (assuming that you're using mod_php) this would too, and reflects the real header names:
<?php
$headers = apache_request_headers();
if($headers['X-SecondLife-Shard'] == 'Production')
{
print "You are on the main grid.";
}
else
{
print "You are on a preview grid.";
}
?>
Additionally, the current information does not show the capitalisation, thus further confusing the matter.
[[User:Katharine Berry|Katharine Berry]] 09:55, 21 June 2007 (PDT)

== Root Certificates ==
Can someone add a list of root certificates to this article?

I know that Verisign, Thawt, and RapidSSL are accepted, I know that CACert.org is not.

== HTTP_VERIFY_CERT behavior clarification ==

Even when HTTP_VERIFY_CERT is set to FALSE, if the certificate domain name does not match the URL domain you will get a HTTP 499 response.