Talk:Microsoft Windows Builds
Running viewer outside of MS VS
To leave the executable where it is, but run it without running MSVS:
- Make a shortcut for linden/indra/build-VC80/relwithdebinfo/secondlife-bin.exe
- Right-click the shortcut, Properties, and for "Start in:", navigate to "linden/indra/newview".
Lear Cale 17:52, 6 February 2009 (UTC)
Alternatively, if you really want to pull SL executable out of the build environment: (Thanks to Ambrosia of sldev list for this text. I have not tried it myself. Lear Cale 18:11, 5 February 2009 (UTC))
Make a new folder, somewhere.
Copy the contents of your build-vc90/release/* (or debug, or relwithdeb) folder into that one. The only exceptions are the secondlife-bin.* files aside of the .exe, you don't necessarily need those.
Also copy the following files from indra/newview/ there:
- app_settings
- character
- fonts
- skins
- all .txt files that include 'feature'
llkdu.dll needs to be grabbed from a plain LL viewer. If you use OpenAL, you might have to rename openal.dll to openal32.dll, and you might have to manually copy fmod.dll from your /libraries/ folder into the new one.
What is TLC?
Soft Linden introduced several sentences that include an acronym "TLC." What does that mean? I looked up several dictionaries, but I got "thin layer chromatography" and "tender loving care", that both don't make any sense in this context... Please use plain, no cryptic English when updating SL wiki. Thanks. --Alissa Sabre 06:48, 18 May 2008 (PDT)
- Actually, I'm fairly sure he did mean "tender loving care", by which Soft meant it needs some work. --Ky Aska 05:19, 3 June 2008 (PDT)
- Thanks. --Alissa Sabre 07:32, 28 July 2008 (PDT)
VS2008
On May 2008, Soft Linden entirely rewrote this page, and classified the build environments into three groups. She put VS2008 under community experimental thing. On June 2008, Sardonyx Linden edited this page and put VS2008 under community supported, without removing it from community experimental.
I'm not sure whether it is possible to build a stable binary using VS2008, but at least there seems no instructions available on the wiki...
--Alissa Sabre 07:38, 28 July 2008 (PDT)
Quicktime has developer SDKs (presumably outdated, but they still work) on a branch of their website [1] [2]
llkdu.dll
Why do the instructions say to copy llkdu.dll if you get an error message? Isn't it always missing? Shouldn't it be added to the instructions along with fmod and Quicktime to put it in libraries\i686-win32\lib\debug and release instead of into the build directory? And why do the fmod and Quicktime instructions say "if you're using CMake? Is there an alternative?
Mm Alder 04:04, 21 April 2009 (UTC)
Don't forget to run cmake
The Windows Build Instructions left out the detail that you must run:
python develop.py cmake
after you run
python develop.py -G VC80/90
Doing so will alleviate the missing llkdu.dll file error