Second Life Wiki - User contributions [en]

User talk:Liana Linden/Hippopelago

2008-08-04T13:46:33Z

Nicholaz Beresford: New page: === Nick's Random Thoughts === * Sandbox: I know that a lot of people are enjoying the sandboxing I'm currently offering on my parcel (the usual comment is "it's a nice and quiet place to...

=== Nick's Random Thoughts ===

* Sandbox: I know that a lot of people are enjoying the sandboxing I'm currently offering on my parcel (the usual comment is "it's a nice and quiet place to do stuff"). It's certainly not OS related, but I guess the sandbox puts more actual use to the SIM than the current winner parcels. I have currently set aside about 1000-2000 prims for that purpose.
* Dev Sandbox: I guess it's way too large. When a dev needs land options to test features (I remember that I needed one once to check for a bug with voice enabled parcels and think it was Alissa who had the idea of offering land features for developers with basic accounts for such cases), a small place (even 16sqm) would have been enough for me to test a given feature etc. I may be wrong, but I don't foresee many such cases (but I may be misinterpreting the use of the Dev Sandbox entirely though).
* Legacy winner parcels: A group owned parcel would be fine by me ... just a place to put a few prims (and maybe terraforming). However, given the large Dev sandbox, I'd personally prefer a bit more room on OpenSpace (I don't need many prims but prefer space). So maybe the previous winners could be given parcels on the openspace sim, leaving the rest there as Dev. Sandbox or even public building sandbox.
* The above are just my two cents worth of comment off my mind.

Alternate viewers

2008-05-20T11:13:27Z

Nicholaz Beresford: just some whitespace between the entries

== Introduction ==

The [[Extended_FAQ|Extended FAQ]] states that it is okay to create and distribute homebrew viewers as long they adhere to the respective licenses for code usage and server usage.

The code itself is licensed under {{OSWebsite|gplv2|alt=the GNU General Public License (GPL)}}, which governs modification and redistribuition of the source code. Use of Linden Lab's servers will still be governed by [http://secondlife.com/corporate/tos.php the Second Life Terms of Service]].

'''Homebrew viewers are obviously not associated with LindenLab, are governed by their own respective licenses. LindenLab is not responsible for any desired or undesired results in association with those viewers.'''

''Note to authors: If you make a viewer available make sure to include platform, version numbers and dates.''

 
 
 

== Able Edition ==

=== Description ===

This is a Windows viewer is an unofficial build which adds a [https://jira.secondlife.com/browse/VWR-1017 Mute Visibility] feature, which allows objects in-world to be rendered partially or entirely invisible.

=== Extra Features ===
* Mute Visibility
* Improvements to the Mute List
* Muting objects applies to entire linksets

=== Links ===
* Website: [http://ablewhitman.blogspot.com/ Able Whitman on Blogspot]
* Direct download link: http://ablewhitman.org/viewer/
* Source code: http://ablewhitman.org/viewer/

 
 
 

== Dale Glass Edition ==

=== Description ===

This is a Windows (soon Linux) viewer which adds new experimental features. The features are intended to give users more information about the world and to simplify moderation by making it easier to tell where people are and what they're doing.

=== Extra Features ===
* Avatar Scanner
** Shows nearby avatars, roughly in drawing distance range.
** Shows name, age, payment info, current activity.
** Land and estate commands for ejecting/banning multiple avatars at once
** Integration with Luskwood moderation tools
** Buttons to open profile, IM, teleport to or track selected avatars
* Event Log: Experimental feature, shows a list of active particle effects (soon sounds too), and their owners. Allows moving camera to emitter.
* Branding: Replaces LL branding with my own. Different login page, checks for updates against my server.
* Logging of the owner and location of speaking objects

=== Links ===
* Website: http://sl.daleglass.net
* Blog: http://daleglass.wordpress.com
* Direct download link: http://sl.daleglass.net/download
* Source code: http://svn.daleglass.net/sl/release/ ( [[User:Dale_Glass#Subversion_Repository|subversion]] )

 
 
 

== Nicholaz Edition (Discontinued) ==

=== Description ===

These are Windows viewer based on SL builds with a focus on stability, usability and performance (see [http://www.blueflash.cc/users/nicholaz/EyeCandy/!!Installation.txt Installation.txt] for homebrew disclaimer). Mac and Linux variants are available through other open sourcers (links on the website).

'''Note:''' Development of this viewer is discontinued as of 1.19.1. Older versions are still working, download links can be found [http://nicholaz-beresford.blogspot.com/ here] (look for "Release" posts).

=== Extra Features ===
* Improved stability
* Lower memory footprint
* GUI redesigns
* Workarounds for common annoyances (Group IM Filtering, "Release Key" button, etc.)
* see [http://www.blueflash.cc/users/nicholaz/EyeCandy/!Changes.txt Changes.txt] for all details

=== Links ===
* Website: [http://nicholaz-beresford.blogspot.com/ Nicholaz Beresford on Blogspot]
* Direct download link: [http://www.blueflash.cc/users/nicholaz Download versions of this viewer]
* Source code: Look at the [http://www.blueflash.cc/users/nicholaz download site] for the source-xxx-zip files in the respective folders and see the readme.txt inside the archives

 
 
 

== Marine Edition ==

=== Description ===

This viewer, codename "'''RestrainedLife'''" is an attempt at enhancing the experience of people who practice BDSM in Second Life. It is used jointly with simple scripts made to use its features in-world, such as making an attached object undetachable, preventing chat and such. An '''API''' (Application Programming Interface, a text file) is provided so that every content creator can create their own scripts to interface their own items to the viewer and use its features.

=== Extra Features ===
* Attachments can be made undetachable
* Chat and IM prevention on demand, with exceptions if needed
* Teleport and sit-tp prevention on demand, with exceptions if needed
* Editing and Rezzing prevention on demand
* Adding/Removing clothes on demand, + force remove clothes and force remove unlocked attachments
* Force sit and prevent stand up (even after a relog) on demand
* Manual (by IM) and automatic (by script) version checking
* API for content creators

=== Links ===
* Website: [http://realrestraint.blogspot.com/ Marine Kelley's blog on Blogspot]
* Direct download link to the Windows viewer: [http://www.erestraint.com/realrestraint Download for Windows] (Executable and readme)
* Direct download link to the MacOS X viewer: [http://www.erestraint.com/realrestraint Download for MacOS X] (Executable and readme, courtesy of Mo Noel)
* Direct download link to the Linux viewer: [http://www.loomiverse.net/RestrainedLife Download for Linux] (Executable and readme, courtesy of Loom Kish)
* Source code and text API : [http://www.erestraint.com/realrestraint Download] (Text files)
* API as a wiki page : [https://wiki.secondlife.com/wiki/RestrainedLifeAPI API] (Wiki format)
* Specification to interface cages & furnitures with the viewer through the use of a relay : [https://wiki.secondlife.com/wiki/LSL_Protocol/RestrainedLifeRelaySpecs Relay Spec] (Wiki format)

=== Version and timestamp ===

* Version : 1.10.5.2, compiled on SL official viewer 1.19.0.5
* Date : 04/09/2008

 
 
 

== Henri Beauchamp Edition ==

=== Description ===

This viewer, codename "'''Cool SL Viewer'''" combines elements of several of the other viewers, as well as some extra patches very carefully tested.

=== Extra Features ===
* Reverses many of the unpopular interface changes made in the transition to voice being standard (including reinstating the packet loss and bandwidth indicators, the old toolbar and buttons layouts, the old, more visible, status bar icons, and optionally reinstating the old, more visible, tracking dots in the mini-map).
* Implements the "Restrained Life" API discussed more fully in the Marine Edition client.
* Defines double-click default actions for many types of inventory.
* Allows to optionally prevent IMs to show in the main chat.
* Allows to hide the "Release Keys" and/or the "Master volume" in the panel overlay.
* MUD/MUSH/MUCK/MU* style "poses".
* Allows to build and TP over 768m of altitude (and up to 4096m).
* Allows to build large prims (up to 100m in any or all dimensions) on OpenSim (not on SL, because of server-side limitations).
* Various patches by Nicholaz Beresford, Gigs Taggart, Blakar Ogre, and others.

=== Links ===
* Website: [http://sldev.free.fr/ The Cool SL Viewer homepage]
* Direct download link to the Linux viewer: [http://sldev.free.fr/SecondLife_i686_1_19_0_5_CoolRelease_10-diff_files.tar.bz2 Download for Linux] (please, check the [http://sldev.free.fr/ The Cool SL Viewer homepage] for installation instructions).
* Windows viewer: [http://my.opera.com/boylane/blog/ See Boy Lane's site] for files and instructions.
* MacOS X viewer: [http://radio-boomslang.shacknet.nu/~bb/articles/cool-viewer-mac/index.html See Barney Boomslang's site] for files and instructions. Beware: Barney's first version was not an exact port of the Cool SL Viewer: it missed the RestrainedLife features: be sure to download the latest release (1.19.1.4(b) or later).
* Source code: The standard Linden codebase is used, with the addition of the patches listed and linked to on the homepage.

=== Version and timestamp ===

* Version : i686 1.19.0.5 CoolRelease 10
* Date : 2008/05/09

* Version : i686 1.19.1.4 CoolRelease 7
* Date : 2008/05/09

 
 
 

== Kirstens Viewers ==

=== Description ===

These Viewers are custom built for win32 platforms, and take code from the SLDev and patches from 3rd parties or jira, and should be considered experimental compared to the standard release client, they are however compiled more or less exclusively for high end intel based machines for best performance or to fix specific problems and have proved very stable with minor performance increases and added stability in some cases.

Kirsten also builds Viewers based off snapshots, very experimental and sometimes not yet available from the official website.

=== Extra Features ===
* Compiled For Maximum Performance (Some Viewers High End Intel Specific)
* Quicker Loading,More Responsive,better memory use.
* Record Logins 19 to 20h Hours (Thanks to Phantium and Paulo For the Tests)
* Viewers Released to Fix specific problems (Including Kirstens Own Patches)
* Snapshots Preview Builds of Newest Viewers (Sometimes Before Official Release )

* Redesigned Skins on Certain Viewers

=== Links ===
* http://code.google.com/p/kirstens-secondlife-viewers/
* http://www.armyof4.com/Kirstenlee/

=== Version and timestamp ===

* Version : Kirstens Dazzle(Stable,Low Memory Footprint,Grey UI )
* Version : Kirstens 1-20-2-85057(R5) Latest Snapshot - R4(most Stable) R5(latest) R5a(Dark Hi Contrast UI)
* Version : Kirstens Retro ,For Older Hardware based on 1-18-6-4 (To Support Older Hardware,Grid Thinks its a 1-20 ^^ )
* Date : 04/19/2008

 
 
 

== Onrez Viewer ==

=== Description ===

The Onrez viewer was made by the Onrez company in connection with a Second Life themed story on the high tech forensics based TV show "CSI: New York".

=== Extra Features ===
* A back and history button for teleports
* In-viewer web browsing.

=== Links ===
* http://viewer.onrez.com for the download

=== Comment ===
The source code for this viewer is closed source.

 
 
 

== RealXtend Edition ==

=== Description ===

The realXtend viewer is a heavily modified version of the Linden Labs' Second Life client by a partnership of two Finnish companies, ADMINO technologies and LudoCraft.

=== Extra Features ===
* Second life compatibility mode for use in SL and Opensim worlds
* Teleports between realXtend and Secondlife

=== Links ===
* Website: [http://www.realxtend.org/]
* Direct download link: http://www.realxtend.org/downloads.html
* Source code: http://sourceforge.net/projects/realxtendviewer/

 
 
 

== METAbolt ==
=== Text Based SL Viewer Edition ===

=== Description ===

METAbolt is a non-graphical (text based) viewer. It's light weight and cross grid, which means it will work in Second Life as well as other grids that are based on OpenSIM. The viewer is Open Source so it's free. Currently METAbolt is only available for Windows platforms.

METAbolt is ideal if:

* the graphical viewers are not allowed at your work place
* you have a low powered computer that has difficulty running the SL viewer
* you have a low speed internet connection e.g. dial up
* you need to run multiple alts at the same time
* you need to run alts to carry out land security, group management functions
* you can't or don't want to run the SL viewer all the time but need the ability to stay online for communications or other reasons

=== Extra Features ===
Too many to be listed here. Here are just a few:
* Built in Machine Translation with 16 language pairs
* Emoticons on chat & IM. Feature can be switched on/off
* Land monitor: monitor parcels that are for sale on a SIM
* Object Manager: Detailed object information & stats
* (optional) Group Manager plug-in for sending direct group invites
* Uses extremely low computing power and bandwidth

=== Version and timestamp ===

* Version : 0.9.0.34 BETA (at the time this page was prepared)
* Date : 01 May 2008
* Platform: Windows Only

=== Links ===
* Website: http://www.metabolt.net/
* Download: http://www.metabolt.net/download.asp

Preparing Code

2008-05-07T10:12:28Z

Nicholaz Beresford:

{{OSWikiContribBox}}

If you have a piece of source code (be it a fix, new feature, or optimization of existing code) submit the patches in a way that makes it easy for the Lindens to incorporate them into the source code.

== Good Patch Practise ==

=== General ===

The people who review and apply patches are the bottleneck in the system. If you can make it easier for Lindens to understand, test and apply your patch without lots of cleanup, Lindens can incorporate more patches in a fixed amount of time.

===Before You Start===

Check [https://jira.secondlife.com/secure/Dashboard.jspa JIRA Bug Tracker] to see if a similar issue has been submitted, and check its status. You will eventually attach to the existing issue if you find one. If your issue is new, it can help to create the issue before starting work so that others can begin voting for the patch. More votes lead to faster incorporation.

If you haven't, don't forget to sign and send in the [http://secondlifegrid.net/programs/open_source/submission contribution agreement]. The sooner you do that, the sooner Lindens can accept your patch. Getting this out of the way early avoids any mailing or processing delays. You only need to do this one time.

=== Coding Standard ===

Please read and follow the coding standard: [[Coding_standard|Second Life coding standard]]

=== Comments ===

Please do not add issue numbers and your name to the code section. These have to be removed by hand. While comments explaining code in a general working context are helpful, bracketing a patch with comments like "// PATCH START" and "// PATCH END" does not add any information, and adds to the manual cleanup Lindens have to do.

In short, add to the patch what is expected to appear in the final source.

=== Give Yourself Credit! ===

While names and JIRAs shouldn't appear in source, they do belong in doc/contributions.txt. Please don't be shy about adding the issue label and adding your name. We use this file for a number of purposes, including the generation of the [[Source contributions]] page. This also helps Lindens track the purpose of a given patch file.

=== One Patch for one Issue ===

Each patch should do exactly one thing. If you have three different bugs to fix, please submit three different patches. When you fold unrelated hunks into a single patch, Lindens have to try to figure out which part of the patch applies to which bug, and split it out by hand, usually into several patches. Combo patches are particularly time consuming, and the manual splitting up makes it very easy to lose pieces of patches altogether.

=== Less is more ===

Smaller patches are easier to review and therefore more likely to be integrated quickly. The longer it takes for a patch to be incorporated, the higher the likelihood that the underlying code will change enough for the patch to fail. Please do not include formatting or other clean-up changes. These make a patch harder to review and more likely to fail.

=== Path structure ===

It's best practice for your patch to be made on the directory level where the linden folder resides so that the path/file names in your patch will start with '''linden/'''. If you are working from a SVN, a diff in SVN style starting from the '''indra''' directory level [https://lists.secondlife.com/pipermail/sldev/2008-May/009568.html is also fine].

== Creating a Patch ==

Patches should be submitted in unified diff format. This format is similar to simple diffs, but with more detailed information, and it can be automatically integrated into the source. You can generate a unified diff by calling ''diff -u <original file> <new file>'' (under Windows you will find the diff command as part of the CygWin project in C:\CYGWIN\BIN).

Please submit a single plain text uncompressed patch file that affects all of the files you need to modify. This is far easier to review than a collection of tiny one-file patches.

Also bad for reviewability are a compressed patch, or a tarball or zip containing one or more patches.

=== Unified diff of all changed files in a folder tree ===
The easiest way to generate a clean patch is to keep two copies of the source tree. Leave one completely unmodified, and make all of your changes in the second. Then use "diff -urN" to generate the patch. You can use the --exclude option to omit unwanted files. For example:

diff -urN --exclude="*.o" my_untouched_tree my_modified_tree

=== Unified diff of multiple files ===
If for any reason you can not use a whole tree diff as above, you can still merge patches from different files into one, by appending the output of patch commands to the previous output (via '''>>''' redirection for the 2nd and later commands).

diff -u linden-untouched/indra/newview/viewer.h linden/indra/newview/viewer.h >mychanges.patch.txt
diff -u linden-untouched/indra/newview/viewer.cpp linden/indra/newview/viewer.cpp '''>>'''mychanges.patch.txt
diff -u linden-untouched/indra/newview/llviewerwindow.cpp linden/indra/newview/llviewerwindow.cpp '''>>'''mychanges.patch.txt

 

=== CR/LF vs LF and Whitespace===
In some situations, you will find that the patch contains the whole file, rather than just the lines changed. The reason is that sometimes, files in Linux format find their way into the source distribution. With these diff.exe will treat all lines as different from those in your modified file.

There are various options that will help here. You can add ''--strip-trailing-cr'' to the command line to fix this.

diff -u --strip-trailing-cr linden-untouched/indra/newview/viewer.h linden/indra/newview/viewer.h >mychanges.patch.txt

In some situations try the '''w''' (ignore whitespace) and/or '''B''' (ignore empty lines) options are also helpful (e.g. with tabs vs. space or spurious space characters while editing). Type '''diff --help''' for more details.

 

=== Sample output ===
For reference, here's what a unified diff looks like.

--- linden-untouched/indra/newview/viewer.cpp 2007-05-14 16:47:26.000000000 +0200
+++ linden/indra/newview/viewer.cpp 2007-05-22 08:49:50.484375000 +0200
@@ -6302,7 +6326,7 @@

llinfos << "Cleaning Up" << llendflush;

- LLKeyframeMotion::flushKeyframeCache();
+ LLKeyframeMotion::flushKeyframeCache(TRUE);

// Must clean up texture references before viewer window is destroyed.
LLHUDObject::cleanupHUDObjects();
@@ -6562,6 +6586,8 @@
delete gVFS;
gVFS = NULL;

+ LLCurl::cleanup();
+
// This will eventually be done in LLApp
LLCommon::cleanupClass();
}

== Submitting the Patch on JIRA ==

When you are ready for the world to view your patch, submit the patch on the [https://jira.secondlife.com/secure/Dashboard.jspa| JIRA Bug Tracker]. Create a new issue or attach the patch to an existing entry as appropriate. Attach the ''.patch.txt'' file itself as a file attachment and make sure that the check mark for ''Patch attached'' is set (you can do that when creating the issue or by choosing Edit for an existing one). Along with your patch, it helps to provide a brief description explaining your patch from an implementor's view. Non-trivial patches benefit form a simple review plan naming what systems were affected and describing what peers can do to verify that the patch works and doesn't break surrounding systems. Very often, you will find that writing only a few lines will give you pause and make you double-check some code.

For all but the most trivial patches, it is a good idea to submit the patch for peer review on the [[Developer_communication_tools|mailing list]]. This way fellow developers can review the patch, uncover possible bugs, comment on undesired interactions or generally share ideas with you. Subscribe to the mailing list, then write an email to the list with a link to the description of what your patch does.

Good luck!

== Applying patches to your source ==

In case you are interested, the application of other patches to your source is easy. Assuming that you are at the directory level from where the patch references the files (usually in the folder where you see the '''linden''' folder), applying a patch can be done via:

c:\cygwin\bin\patch -p 0 -i changes.patch

or

c:\cygwin\bin\patch -p 0 < changes.patch

On your first attempts, you might also be interested in the '''--verbose''', '''--backup''' or '''--dry-run''' (simulate patch) options. See '''patch --help''' for details.

c:\cygwin\bin\patch -p 0 --verbose --backup --dry-run -i changes.patch

Also, if a patch fails, look for files ending with '''.rej''' in the target folder.

Converting project files for MSVS2005

2008-05-05T16:06:39Z

Nicholaz Beresford: /* Global steps */

{{CompileNav}}

= Manual conversion of the VS2003 solution/projects =
This page describes the steps necessary to fully convert Linden Labs solution and project files from VS2003 to VS2005.

There are canned sets of these available on the [https://jira.secondlife.com/browse/VWR-1151 JIRA bug tracker issue VWR-1151], so downloading these may save you the work described below.

== Global steps ==

* Start Visual Studio 2005 (or VC++ Express).
* Use "File > Open > Project/Solution" to open the linden\indra\indra_complete\indra_complete.sln
* Visual Studio prompts to update your project files. Allow it to do so. When the results are displayed, you may see warnings, but you should not see any errors.
* Right click '''newview''' in the frame Solution Explorer and click "Set as StartUp Project".
* From the Visual Studio menu bar, choose "File > New > File...". On the "New File" dialog box, choose "General", then "Text File". Select the lines from the box below in your browser, copy them, and paste them to the empty file you just created. Save it as a file of the name '''SL-UpgradeFromVC71_vc8.vsprops''' under the folder '''linden/indra/indra_complete''' (where the "indra_complete.sln" file resides.)
* Alternately download the file from [http://www.blueflash.cc/users/nicholaz/~libs/sl-UpgradeFromVC71_vc8.vsprops here] (right click link, Save As, go to the '''linden/indra/indra_complete''' folder)

<?xml version="1.0"?>
<VisualStudioPropertySheet
ProjectType="Visual C++"
Version="8.00"
Name="Upgrade From VC 7.1">
<Tool
Name="VCCLCompilerTool"
PreprocessorDefinitions="_VC80_UPGRADE=0x0710;_CRT_SECURE_NO_DEPRECATE;_CRT_NONSTDC_NO_DEPRECATE;_USE_32BIT_TIME_T;_SECURE_SCL=0"
WarnAsError="false"
TreatWChar_tAsBuiltInType="false"
/>
<Tool
Name="VCResourceCompilerTool"
PreprocessorDefinitions="_VC80_UPGRADE=0x0710;_CRT_SECURE_NO_DEPRECATE;_CRT_NONSTDC_NO_DEPRECATE;_USE_32BIT_TIME_T;_SECURE_SCL=0"
/>
</VisualStudioPropertySheet>

== All Configuration Steps ==
# Select all projects, i.e., llaudio, llcharacter, ..., win_updater, '''except''' for lscript_compile_fb and test. (You can do it by control-clicking on the projects.)
# Right click on the selection and choose Properties.
# A window named Property Pages opens. There single left-click (select) '''Configuration Properties''' in the tree on the left of the window.
# In the upper left corner of Property Pages choose '''All Configurations''' from the Configuration drop down box.
# Now, in the tree select '''Configuration Properties > General''' and change '''Inherited Project Property Sheets''' and set it to '''$(SolutionDir)\SL-UpgradeFromVC71_vc8.vsprops'''. (Write this literally, as opposed to replacing "$(SolutionDir)" with some real path.)
# press enter or click anywhere outside the '''Inherited Project Property Sheets''' field to commit the changes to the field.
# Click Apply button of the dialog. Make sure that the '''Inherited Project Property Sheets''' field keeps your entry (the Apply button will clear the field if the file is wrong or if it was not found).
# Under the '''Configuration Properties > C/C++ > General''', make sure '''Treat Warnings As Errors''' is set to "'''No'''" (this should happen through the above inherited property sheet vsprops file, otherwise do it manually). ([[:Image:MSVS2005_Project_Property_Pages_Config_CPP_General.JPG|'''screen shot''']]).
# Under the '''Configuration Properties > C/C++ > Language''', make sure '''Treat wchar_t as Build-in Type''' is to "'''No (/Zc:wchar_t-)'''" (this should happen through the above inherited property sheet (vsprops) file, otherwise do it manually) ([[:Image:MSVS2005 Project Property Pages Config CPP Language.JPG|'''screen shot''']]).
# Under the '''Configuration Properties > C/C++ > Advanced''', change (if necessary) '''Use Full Paths''' to "'''Yes (/FC)'''" ([[:Image:MSVS2005 Project Property Pages Config CPP Advanced.JPG|'''screen shot''']]).
# Click OK for the dialog.

== Per Configuration Steps ==
* Pick '''ReleaseNoOpt''' in the Solution Configurations drop-down box next to the green arrow under the tool bar, and do the followings on the Solution Explorer frame (on left side of the VS2005 window):
*# Left-click '''newview''' to select it alone.
*# Right-click '''newview''', choose Properties.
*# Under '''Configuration Properties > Linker > Input''', click '''Additional Dependencies''' on the right to show a button labeled "'''...'''" on it at the very right on the line, then click the '''...''' button.
*# Scroll down the list to find '''libboost_regex-vc71-mt-s.lib'''. Rewrite it to libboost_regex-vc'''80'''-mt-s.lib (for 1.20 and later, do the same (i.e. change 71 into 80) for other libboost libraries, like libboost_signals*.lib, libboost_program_options*lib ... to check, these libraries should be found in linden/libraries/i686-win32/lib_release).
*# Scroll down again to find '''llmozlib.lib''' and rewrite it to llmozlib'''-vc80'''.lib. (This step is not needed on viewer version 1.19.1.0 or later.)
*# Click '''OK''' to close the "Additional Dependencies" dialog, then click OK again to close the "newview Property Pages" dialog box.
* Pick '''ReleaseForDownload''' in the Solution Configurations drop-down box (in the toolbar, next to the green arrow). Repeat the same steps (as for ReleaseNoOpt above) again.
* Depending on what you want to do later (or if you want to do a full and complete conversion), you may also need to perform these steps for the Debug and Release configurations, but for a start it is safe to skip these.

== Special configuration steps for llmedia (1.19.1 or later only) ==

* Right click on the llmedia project on the solution explorer, then choose Properties.
* Choose '''Release''' in the Configuration drop down box on the upper loft of the "llmedia Property pages."
* Choose '''Configuration Properties''' > '''Librarian''' > '''General''' on the tree on the left.
* In '''Additional Dependencies''', there is '''llmozlib2.lib'''. Change it to llmozlib2'''-vc80'''.lib.
* Click OK to close the dialog box.
* Right click on the llmedia project, and choose Properties again.
* Choose '''ReleaseNoOpt''' in the Configuration. Do the same thing as for Release again. Click OK to close the dialog box.
* Right click on the llmedia project, and choose Properties, for the third time.
* Choose '''Debug''' in the Configuration. Do the ''similar'' thing, too. However, Additional Dependencies for Debug includes llmozlib2'''d'''.lib. So, you should change it to llmozlib2'''d-vc80'''.lib. Click OK to close the dialog box.

== Optional steps ==
The following steps are not strictly necessary, unless you want a full and ultra clean conversion (e.g. for sharing with others). These instructions are telegram style, assuming you will do this only after you have aquainted yourselves with the project
* In the Configuration manager (Build menu):
** unclick the build column for '''test''', '''win_crash_logger''' and '''win_updater''' in all configurations '''except ReleaseForDownload'''.
** unclick the build column for '''test''' in '''ReleaseForDownload'''
* For all configurations: In newview, properties, linker input: If you find libraries starting with 'll' (e.g. '''llaudio.lib''', '''llcharacter.lib''', etc.) or find the library '''lscript_library.lib'''), remove them from the list (these libraries are linked through the dependency)
* For all configurations: In newview, properties, linker input: Set '''Ignore Specific Library''' to '''msvcrt.lib;msvcrtd.lib;libc.lib;libcd.lib;'''
* In the Debug configuration, under lscript_compile_fb, indra.y, properties, custom build step, general, command line, make sure you have ''C:\cygwin\bin\mv.exe ytab.hpp ytab.h'' (use the command line from the release configuration as reference).
* In the Debug configuration, also add '''libcmt.lib;''' to the list of specific libraries to ignore.
* In all configurations: the libraries need to be changed from vc71 to vc80 (boost, llmozlib) for the '''test''' project as well, but since '''test''' does not seem to work under VC2005 so far, it's optional.

== Done :-) ==
Congratulations! You've converted ''solution file'' and ''project files''.

'''NOTE:''' You need to do this by hand everytime a new viewer version is released...

Converting project files for MSVS2005

2008-05-05T15:55:13Z

Nicholaz Beresford: /* Per Configuration Steps */

{{CompileNav}}

= Manual conversion of the VS2003 solution/projects =
This page describes the steps necessary to fully convert Linden Labs solution and project files from VS2003 to VS2005.

There are canned sets of these available on the [https://jira.secondlife.com/browse/VWR-1151 JIRA bug tracker issue VWR-1151], so downloading these may save you the work described below.

== Global steps ==

* Start Visual Studio 2005 (or VC++ Express).
* Use "File > Open > Project/Solution" to open the linden\indra\indra_complete\indra_complete.sln
* Visual Studio prompts to update your project files. Allow it to do so. When the results are displayed, you may see warnings, but you should not see any errors.
* Right click '''newview''' in the frame Solution Explorer and click "Set as StartUp Project".
* From the Visual Studio menu bar, choose "File > New > File...". On the "New File" dialog box, choose "General", then "Text File". Select the following lines on your browser, copy them, and paste them to the empty file you just created. Save it as a file of the name "SL-UpgradeFromVC71_vc8.vsprops" under the folder "indra_complete" (where the "indra_complete.sln" file resides.)

<?xml version="1.0"?>
<VisualStudioPropertySheet
ProjectType="Visual C++"
Version="8.00"
Name="Upgrade From VC 7.1">
<Tool
Name="VCCLCompilerTool"
PreprocessorDefinitions="_VC80_UPGRADE=0x0710;_CRT_SECURE_NO_DEPRECATE;_CRT_NONSTDC_NO_DEPRECATE;_USE_32BIT_TIME_T;_SECURE_SCL=0"
WarnAsError="false"
TreatWChar_tAsBuiltInType="false"
/>
<Tool
Name="VCResourceCompilerTool"
PreprocessorDefinitions="_VC80_UPGRADE=0x0710;_CRT_SECURE_NO_DEPRECATE;_CRT_NONSTDC_NO_DEPRECATE;_USE_32BIT_TIME_T;_SECURE_SCL=0"
/>
</VisualStudioPropertySheet>

== All Configuration Steps ==
# Select all projects, i.e., llaudio, llcharacter, ..., win_updater, '''except''' for lscript_compile_fb and test. (You can do it by control-clicking on the projects.)
# Right click on the selection and choose Properties.
# A window named Property Pages opens. There single left-click (select) '''Configuration Properties''' in the tree on the left of the window.
# In the upper left corner of Property Pages choose '''All Configurations''' from the Configuration drop down box.
# Now, in the tree select '''Configuration Properties > General''' and change '''Inherited Project Property Sheets''' and set it to '''$(SolutionDir)\SL-UpgradeFromVC71_vc8.vsprops'''. (Write this literally, as opposed to replacing "$(SolutionDir)" with some real path.)
# press enter or click anywhere outside the '''Inherited Project Property Sheets''' field to commit the changes to the field.
# Click Apply button of the dialog. Make sure that the '''Inherited Project Property Sheets''' field keeps your entry (the Apply button will clear the field if the file is wrong or if it was not found).
# Under the '''Configuration Properties > C/C++ > General''', make sure '''Treat Warnings As Errors''' is set to "'''No'''" (this should happen through the above inherited property sheet vsprops file, otherwise do it manually). ([[:Image:MSVS2005_Project_Property_Pages_Config_CPP_General.JPG|'''screen shot''']]).
# Under the '''Configuration Properties > C/C++ > Language''', make sure '''Treat wchar_t as Build-in Type''' is to "'''No (/Zc:wchar_t-)'''" (this should happen through the above inherited property sheet (vsprops) file, otherwise do it manually) ([[:Image:MSVS2005 Project Property Pages Config CPP Language.JPG|'''screen shot''']]).
# Under the '''Configuration Properties > C/C++ > Advanced''', change (if necessary) '''Use Full Paths''' to "'''Yes (/FC)'''" ([[:Image:MSVS2005 Project Property Pages Config CPP Advanced.JPG|'''screen shot''']]).
# Click OK for the dialog.

== Per Configuration Steps ==
* Pick '''ReleaseNoOpt''' in the Solution Configurations drop-down box next to the green arrow under the tool bar, and do the followings on the Solution Explorer frame (on left side of the VS2005 window):
*# Left-click '''newview''' to select it alone.
*# Right-click '''newview''', choose Properties.
*# Under '''Configuration Properties > Linker > Input''', click '''Additional Dependencies''' on the right to show a button labeled "'''...'''" on it at the very right on the line, then click the '''...''' button.
*# Scroll down the list to find '''libboost_regex-vc71-mt-s.lib'''. Rewrite it to libboost_regex-vc'''80'''-mt-s.lib (for 1.20 and later, do the same (i.e. change 71 into 80) for other libboost libraries, like libboost_signals*.lib, libboost_program_options*lib ... to check, these libraries should be found in linden/libraries/i686-win32/lib_release).
*# Scroll down again to find '''llmozlib.lib''' and rewrite it to llmozlib'''-vc80'''.lib. (This step is not needed on viewer version 1.19.1.0 or later.)
*# Click '''OK''' to close the "Additional Dependencies" dialog, then click OK again to close the "newview Property Pages" dialog box.
* Pick '''ReleaseForDownload''' in the Solution Configurations drop-down box (in the toolbar, next to the green arrow). Repeat the same steps (as for ReleaseNoOpt above) again.
* Depending on what you want to do later (or if you want to do a full and complete conversion), you may also need to perform these steps for the Debug and Release configurations, but for a start it is safe to skip these.

== Special configuration steps for llmedia (1.19.1 or later only) ==

* Right click on the llmedia project on the solution explorer, then choose Properties.
* Choose '''Release''' in the Configuration drop down box on the upper loft of the "llmedia Property pages."
* Choose '''Configuration Properties''' > '''Librarian''' > '''General''' on the tree on the left.
* In '''Additional Dependencies''', there is '''llmozlib2.lib'''. Change it to llmozlib2'''-vc80'''.lib.
* Click OK to close the dialog box.
* Right click on the llmedia project, and choose Properties again.
* Choose '''ReleaseNoOpt''' in the Configuration. Do the same thing as for Release again. Click OK to close the dialog box.
* Right click on the llmedia project, and choose Properties, for the third time.
* Choose '''Debug''' in the Configuration. Do the ''similar'' thing, too. However, Additional Dependencies for Debug includes llmozlib2'''d'''.lib. So, you should change it to llmozlib2'''d-vc80'''.lib. Click OK to close the dialog box.

== Optional steps ==
The following steps are not strictly necessary, unless you want a full and ultra clean conversion (e.g. for sharing with others). These instructions are telegram style, assuming you will do this only after you have aquainted yourselves with the project
* In the Configuration manager (Build menu):
** unclick the build column for '''test''', '''win_crash_logger''' and '''win_updater''' in all configurations '''except ReleaseForDownload'''.
** unclick the build column for '''test''' in '''ReleaseForDownload'''
* For all configurations: In newview, properties, linker input: If you find libraries starting with 'll' (e.g. '''llaudio.lib''', '''llcharacter.lib''', etc.) or find the library '''lscript_library.lib'''), remove them from the list (these libraries are linked through the dependency)
* For all configurations: In newview, properties, linker input: Set '''Ignore Specific Library''' to '''msvcrt.lib;msvcrtd.lib;libc.lib;libcd.lib;'''
* In the Debug configuration, under lscript_compile_fb, indra.y, properties, custom build step, general, command line, make sure you have ''C:\cygwin\bin\mv.exe ytab.hpp ytab.h'' (use the command line from the release configuration as reference).
* In the Debug configuration, also add '''libcmt.lib;''' to the list of specific libraries to ignore.
* In all configurations: the libraries need to be changed from vc71 to vc80 (boost, llmozlib) for the '''test''' project as well, but since '''test''' does not seem to work under VC2005 so far, it's optional.

== Done :-) ==
Congratulations! You've converted ''solution file'' and ''project files''.

'''NOTE:''' You need to do this by hand everytime a new viewer version is released...

Converting project files for MSVS2005

2008-05-05T15:48:35Z

Nicholaz Beresford: /* All Configuration Steps */

{{CompileNav}}

= Manual conversion of the VS2003 solution/projects =
This page describes the steps necessary to fully convert Linden Labs solution and project files from VS2003 to VS2005.

There are canned sets of these available on the [https://jira.secondlife.com/browse/VWR-1151 JIRA bug tracker issue VWR-1151], so downloading these may save you the work described below.

== Global steps ==

* Start Visual Studio 2005 (or VC++ Express).
* Use "File > Open > Project/Solution" to open the linden\indra\indra_complete\indra_complete.sln
* Visual Studio prompts to update your project files. Allow it to do so. When the results are displayed, you may see warnings, but you should not see any errors.
* Right click '''newview''' in the frame Solution Explorer and click "Set as StartUp Project".
* From the Visual Studio menu bar, choose "File > New > File...". On the "New File" dialog box, choose "General", then "Text File". Select the following lines on your browser, copy them, and paste them to the empty file you just created. Save it as a file of the name "SL-UpgradeFromVC71_vc8.vsprops" under the folder "indra_complete" (where the "indra_complete.sln" file resides.)

<?xml version="1.0"?>
<VisualStudioPropertySheet
ProjectType="Visual C++"
Version="8.00"
Name="Upgrade From VC 7.1">
<Tool
Name="VCCLCompilerTool"
PreprocessorDefinitions="_VC80_UPGRADE=0x0710;_CRT_SECURE_NO_DEPRECATE;_CRT_NONSTDC_NO_DEPRECATE;_USE_32BIT_TIME_T;_SECURE_SCL=0"
WarnAsError="false"
TreatWChar_tAsBuiltInType="false"
/>
<Tool
Name="VCResourceCompilerTool"
PreprocessorDefinitions="_VC80_UPGRADE=0x0710;_CRT_SECURE_NO_DEPRECATE;_CRT_NONSTDC_NO_DEPRECATE;_USE_32BIT_TIME_T;_SECURE_SCL=0"
/>
</VisualStudioPropertySheet>

== All Configuration Steps ==
# Select all projects, i.e., llaudio, llcharacter, ..., win_updater, '''except''' for lscript_compile_fb and test. (You can do it by control-clicking on the projects.)
# Right click on the selection and choose Properties.
# A window named Property Pages opens. There single left-click (select) '''Configuration Properties''' in the tree on the left of the window.
# In the upper left corner of Property Pages choose '''All Configurations''' from the Configuration drop down box.
# Now, in the tree select '''Configuration Properties > General''' and change '''Inherited Project Property Sheets''' and set it to '''$(SolutionDir)\SL-UpgradeFromVC71_vc8.vsprops'''. (Write this literally, as opposed to replacing "$(SolutionDir)" with some real path.)
# press enter or click anywhere outside the '''Inherited Project Property Sheets''' field to commit the changes to the field.
# Click Apply button of the dialog. Make sure that the '''Inherited Project Property Sheets''' field keeps your entry (the Apply button will clear the field if the file is wrong or if it was not found).
# Under the '''Configuration Properties > C/C++ > General''', make sure '''Treat Warnings As Errors''' is set to "'''No'''" (this should happen through the above inherited property sheet vsprops file, otherwise do it manually). ([[:Image:MSVS2005_Project_Property_Pages_Config_CPP_General.JPG|'''screen shot''']]).
# Under the '''Configuration Properties > C/C++ > Language''', make sure '''Treat wchar_t as Build-in Type''' is to "'''No (/Zc:wchar_t-)'''" (this should happen through the above inherited property sheet (vsprops) file, otherwise do it manually) ([[:Image:MSVS2005 Project Property Pages Config CPP Language.JPG|'''screen shot''']]).
# Under the '''Configuration Properties > C/C++ > Advanced''', change (if necessary) '''Use Full Paths''' to "'''Yes (/FC)'''" ([[:Image:MSVS2005 Project Property Pages Config CPP Advanced.JPG|'''screen shot''']]).
# Click OK for the dialog.

== Per Configuration Steps ==
* Pick '''ReleaseNoOpt''' in the Solution Configurations drop-down box next to the green arrow under the tool bar, and do the followings on the Solution Explorer frame (on left side of the VS2005 window):
*# Left-click '''newview''' to select it alone.
*# Right-click '''newview''', choose Properties.
*# Under '''Configuration Properties > Linker > Input''', click '''Additional Dependencies''' on the right to show a button labeled "'''...'''" on it at the very right on the line, then click the '''...''' button.
*# Scroll down the list to find '''libboost_regex-vc71-mt-s.lib'''. Rewrite it to libboost_regex-vc'''80'''-mt-s.lib.
*# Scroll down again to find '''llmozlib.lib''' and rewrite it to llmozlib'''-vc80'''.lib. (This step is not needed on viewer version 1.19.1.0 or later.)
*# Click '''OK''' to close the "Additional Dependencies" dialog, then click OK again to close the "newview Property Pages" dialog box.
* Pick '''ReleaseForDownload''' in the Solution Configurations drop-down box (in the toolbar, next to the green arrow). Repeat the same steps (as for ReleaseNoOpt above) again.
* Depending on what you want to do later (or if you want to do a full and complete conversion), you may also need to perform these steps for the Debug and Release configurations, but for a start it is safe to skip these.

== Special configuration steps for llmedia (1.19.1 or later only) ==

* Right click on the llmedia project on the solution explorer, then choose Properties.
* Choose '''Release''' in the Configuration drop down box on the upper loft of the "llmedia Property pages."
* Choose '''Configuration Properties''' > '''Librarian''' > '''General''' on the tree on the left.
* In '''Additional Dependencies''', there is '''llmozlib2.lib'''. Change it to llmozlib2'''-vc80'''.lib.
* Click OK to close the dialog box.
* Right click on the llmedia project, and choose Properties again.
* Choose '''ReleaseNoOpt''' in the Configuration. Do the same thing as for Release again. Click OK to close the dialog box.
* Right click on the llmedia project, and choose Properties, for the third time.
* Choose '''Debug''' in the Configuration. Do the ''similar'' thing, too. However, Additional Dependencies for Debug includes llmozlib2'''d'''.lib. So, you should change it to llmozlib2'''d-vc80'''.lib. Click OK to close the dialog box.

== Optional steps ==
The following steps are not strictly necessary, unless you want a full and ultra clean conversion (e.g. for sharing with others). These instructions are telegram style, assuming you will do this only after you have aquainted yourselves with the project
* In the Configuration manager (Build menu):
** unclick the build column for '''test''', '''win_crash_logger''' and '''win_updater''' in all configurations '''except ReleaseForDownload'''.
** unclick the build column for '''test''' in '''ReleaseForDownload'''
* For all configurations: In newview, properties, linker input: If you find libraries starting with 'll' (e.g. '''llaudio.lib''', '''llcharacter.lib''', etc.) or find the library '''lscript_library.lib'''), remove them from the list (these libraries are linked through the dependency)
* For all configurations: In newview, properties, linker input: Set '''Ignore Specific Library''' to '''msvcrt.lib;msvcrtd.lib;libc.lib;libcd.lib;'''
* In the Debug configuration, under lscript_compile_fb, indra.y, properties, custom build step, general, command line, make sure you have ''C:\cygwin\bin\mv.exe ytab.hpp ytab.h'' (use the command line from the release configuration as reference).
* In the Debug configuration, also add '''libcmt.lib;''' to the list of specific libraries to ignore.
* In all configurations: the libraries need to be changed from vc71 to vc80 (boost, llmozlib) for the '''test''' project as well, but since '''test''' does not seem to work under VC2005 so far, it's optional.

== Done :-) ==
Congratulations! You've converted ''solution file'' and ''project files''.

'''NOTE:''' You need to do this by hand everytime a new viewer version is released...

Converting project files for MSVS2005

2008-05-05T15:44:08Z

Nicholaz Beresford: /* Global steps */

{{CompileNav}}

= Manual conversion of the VS2003 solution/projects =
This page describes the steps necessary to fully convert Linden Labs solution and project files from VS2003 to VS2005.

There are canned sets of these available on the [https://jira.secondlife.com/browse/VWR-1151 JIRA bug tracker issue VWR-1151], so downloading these may save you the work described below.

== Global steps ==

* Start Visual Studio 2005 (or VC++ Express).
* Use "File > Open > Project/Solution" to open the linden\indra\indra_complete\indra_complete.sln
* Visual Studio prompts to update your project files. Allow it to do so. When the results are displayed, you may see warnings, but you should not see any errors.
* Right click '''newview''' in the frame Solution Explorer and click "Set as StartUp Project".
* From the Visual Studio menu bar, choose "File > New > File...". On the "New File" dialog box, choose "General", then "Text File". Select the following lines on your browser, copy them, and paste them to the empty file you just created. Save it as a file of the name "SL-UpgradeFromVC71_vc8.vsprops" under the folder "indra_complete" (where the "indra_complete.sln" file resides.)

<?xml version="1.0"?>
<VisualStudioPropertySheet
ProjectType="Visual C++"
Version="8.00"
Name="Upgrade From VC 7.1">
<Tool
Name="VCCLCompilerTool"
PreprocessorDefinitions="_VC80_UPGRADE=0x0710;_CRT_SECURE_NO_DEPRECATE;_CRT_NONSTDC_NO_DEPRECATE;_USE_32BIT_TIME_T;_SECURE_SCL=0"
WarnAsError="false"
TreatWChar_tAsBuiltInType="false"
/>
<Tool
Name="VCResourceCompilerTool"
PreprocessorDefinitions="_VC80_UPGRADE=0x0710;_CRT_SECURE_NO_DEPRECATE;_CRT_NONSTDC_NO_DEPRECATE;_USE_32BIT_TIME_T;_SECURE_SCL=0"
/>
</VisualStudioPropertySheet>

== All Configuration Steps ==
# Select all projects, i.e., llaudio, llcharacter, ..., win_updater, '''except''' for lscript_compile_fb and test. (You can do it by control-clicking on the projects.)
# Right click on the selection and choose Properties.
# A window named Property Pages opens. There single left-click (select) '''Configuration Properties''' in the tree on the left of the window.
# In the upper left corner of Property Pages choose '''All Configurations''' from the Configuration drop down box.
# Now, in the tree select '''Configuration Properties > General''' and change '''Inherited Project Property Sheets''' and set it to '''$(SolutionDir)\SL-UpgradeFromVC71_vc8.vsprops'''. (Write this literally, as opposed to replacing "$(SolutionDir)" with some real path.)
# press enter or click anywhere outside the '''Inherited Project Property Sheets''' field to commit the changes to the field.
# Click Apply button of the dialog. Make sure that the '''Inherited Project Property Sheets''' field keeps your entry (if the file is wrong or not found, the Apply button will clear the field again).
# Under the '''Configuration Properties > C/C++ > General''', change '''Treat Warnings As Errors''' to "'''No'''". ([[:Image:MSVS2005_Project_Property_Pages_Config_CPP_General.JPG|'''screen shot''']]).
# Under the '''Configuration Properties > C/C++ > Language''', change (if necessary) '''Treat wchar_t as Build-in Type''' to "'''No (/Zc:wchar_t-)'''" ([[:Image:MSVS2005 Project Property Pages Config CPP Language.JPG|'''screen shot''']]).
# Under the '''Configuration Properties > C/C++ > Advanced''', change (if necessary) '''Use Full Paths''' to "'''Yes (/FC)'''" ([[:Image:MSVS2005 Project Property Pages Config CPP Advanced.JPG|'''screen shot''']]).
# Click OK for the dialog.

== Per Configuration Steps ==
* Pick '''ReleaseNoOpt''' in the Solution Configurations drop-down box next to the green arrow under the tool bar, and do the followings on the Solution Explorer frame (on left side of the VS2005 window):
*# Left-click '''newview''' to select it alone.
*# Right-click '''newview''', choose Properties.
*# Under '''Configuration Properties > Linker > Input''', click '''Additional Dependencies''' on the right to show a button labeled "'''...'''" on it at the very right on the line, then click the '''...''' button.
*# Scroll down the list to find '''libboost_regex-vc71-mt-s.lib'''. Rewrite it to libboost_regex-vc'''80'''-mt-s.lib.
*# Scroll down again to find '''llmozlib.lib''' and rewrite it to llmozlib'''-vc80'''.lib. (This step is not needed on viewer version 1.19.1.0 or later.)
*# Click '''OK''' to close the "Additional Dependencies" dialog, then click OK again to close the "newview Property Pages" dialog box.
* Pick '''ReleaseForDownload''' in the Solution Configurations drop-down box (in the toolbar, next to the green arrow). Repeat the same steps (as for ReleaseNoOpt above) again.
* Depending on what you want to do later (or if you want to do a full and complete conversion), you may also need to perform these steps for the Debug and Release configurations, but for a start it is safe to skip these.

== Special configuration steps for llmedia (1.19.1 or later only) ==

* Right click on the llmedia project on the solution explorer, then choose Properties.
* Choose '''Release''' in the Configuration drop down box on the upper loft of the "llmedia Property pages."
* Choose '''Configuration Properties''' > '''Librarian''' > '''General''' on the tree on the left.
* In '''Additional Dependencies''', there is '''llmozlib2.lib'''. Change it to llmozlib2'''-vc80'''.lib.
* Click OK to close the dialog box.
* Right click on the llmedia project, and choose Properties again.
* Choose '''ReleaseNoOpt''' in the Configuration. Do the same thing as for Release again. Click OK to close the dialog box.
* Right click on the llmedia project, and choose Properties, for the third time.
* Choose '''Debug''' in the Configuration. Do the ''similar'' thing, too. However, Additional Dependencies for Debug includes llmozlib2'''d'''.lib. So, you should change it to llmozlib2'''d-vc80'''.lib. Click OK to close the dialog box.

== Optional steps ==
The following steps are not strictly necessary, unless you want a full and ultra clean conversion (e.g. for sharing with others). These instructions are telegram style, assuming you will do this only after you have aquainted yourselves with the project
* In the Configuration manager (Build menu):
** unclick the build column for '''test''', '''win_crash_logger''' and '''win_updater''' in all configurations '''except ReleaseForDownload'''.
** unclick the build column for '''test''' in '''ReleaseForDownload'''
* For all configurations: In newview, properties, linker input: If you find libraries starting with 'll' (e.g. '''llaudio.lib''', '''llcharacter.lib''', etc.) or find the library '''lscript_library.lib'''), remove them from the list (these libraries are linked through the dependency)
* For all configurations: In newview, properties, linker input: Set '''Ignore Specific Library''' to '''msvcrt.lib;msvcrtd.lib;libc.lib;libcd.lib;'''
* In the Debug configuration, under lscript_compile_fb, indra.y, properties, custom build step, general, command line, make sure you have ''C:\cygwin\bin\mv.exe ytab.hpp ytab.h'' (use the command line from the release configuration as reference).
* In the Debug configuration, also add '''libcmt.lib;''' to the list of specific libraries to ignore.
* In all configurations: the libraries need to be changed from vc71 to vc80 (boost, llmozlib) for the '''test''' project as well, but since '''test''' does not seem to work under VC2005 so far, it's optional.

== Done :-) ==
Congratulations! You've converted ''solution file'' and ''project files''.

'''NOTE:''' You need to do this by hand everytime a new viewer version is released...

Converting project files for MSVS2005

2008-05-05T15:42:25Z

Nicholaz Beresford: /* All Configuration Steps */

{{CompileNav}}

= Manual conversion of the VS2003 solution/projects =
This page describes the steps necessary to fully convert Linden Labs solution and project files from VS2003 to VS2005.

There are canned sets of these available on the [https://jira.secondlife.com/browse/VWR-1151 JIRA bug tracker issue VWR-1151], so downloading these may save you the work described below.

== Global steps ==

* Start Visual Studio 2005 (or VC++ Express).
* Use "File > Open > Project/Solution" to open the linden\indra\indra_complete\indra_complete.sln
* Visual Studio prompts to update your project files. Allow it to do so. When the results are displayed, you may see warnings, but you should not see any errors.
* Right click '''newview''' in the frame Solution Explorer and click "Set as StartUp Project".
* From the Visual Studio menu bar, choose "File > New > File...". On the "New File" dialog box, choose "General", then "Text File". Select the following lines on your browser, copy them, and paste them to the empty file you just created. Save it as a file of the name "SL-UpgradeFromVC71_vc8.vsprops" under the folder "indra_complete" (where the "indra_complete.sln" file resides.)

<?xml version="1.0"?>
<VisualStudioPropertySheet
ProjectType="Visual C++"
Version="8.00"
Name="Upgrade From VC 7.1">
<Tool
Name="VCCLCompilerTool"
PreprocessorDefinitions="_VC80_UPGRADE=0x0710;_CRT_SECURE_NO_DEPRECATE;_CRT_NONSTDC_NO_DEPRECATE;_USE_32BIT_TIME_T;_SECURE_SCL=0"
TreatWChar_tAsBuiltInType="false"
/>
<Tool
Name="VCResourceCompilerTool"
PreprocessorDefinitions="_VC80_UPGRADE=0x0710;_CRT_SECURE_NO_DEPRECATE;_CRT_NONSTDC_NO_DEPRECATE;_USE_32BIT_TIME_T;_SECURE_SCL=0"
/>
</VisualStudioPropertySheet>

== All Configuration Steps ==
# Select all projects, i.e., llaudio, llcharacter, ..., win_updater, '''except''' for lscript_compile_fb and test. (You can do it by control-clicking on the projects.)
# Right click on the selection and choose Properties.
# A window named Property Pages opens. There single left-click (select) '''Configuration Properties''' in the tree on the left of the window.
# In the upper left corner of Property Pages choose '''All Configurations''' from the Configuration drop down box.
# Now, in the tree select '''Configuration Properties > General''' and change '''Inherited Project Property Sheets''' and set it to '''$(SolutionDir)\SL-UpgradeFromVC71_vc8.vsprops'''. (Write this literally, as opposed to replacing "$(SolutionDir)" with some real path.)
# press enter or click anywhere outside the '''Inherited Project Property Sheets''' field to commit the changes to the field.
# Click Apply button of the dialog. Make sure that the '''Inherited Project Property Sheets''' field keeps your entry (if the file is wrong or not found, the Apply button will clear the field again).
# Under the '''Configuration Properties > C/C++ > General''', change '''Treat Warnings As Errors''' to "'''No'''". ([[:Image:MSVS2005_Project_Property_Pages_Config_CPP_General.JPG|'''screen shot''']]).
# Under the '''Configuration Properties > C/C++ > Language''', change (if necessary) '''Treat wchar_t as Build-in Type''' to "'''No (/Zc:wchar_t-)'''" ([[:Image:MSVS2005 Project Property Pages Config CPP Language.JPG|'''screen shot''']]).
# Under the '''Configuration Properties > C/C++ > Advanced''', change (if necessary) '''Use Full Paths''' to "'''Yes (/FC)'''" ([[:Image:MSVS2005 Project Property Pages Config CPP Advanced.JPG|'''screen shot''']]).
# Click OK for the dialog.

== Per Configuration Steps ==
* Pick '''ReleaseNoOpt''' in the Solution Configurations drop-down box next to the green arrow under the tool bar, and do the followings on the Solution Explorer frame (on left side of the VS2005 window):
*# Left-click '''newview''' to select it alone.
*# Right-click '''newview''', choose Properties.
*# Under '''Configuration Properties > Linker > Input''', click '''Additional Dependencies''' on the right to show a button labeled "'''...'''" on it at the very right on the line, then click the '''...''' button.
*# Scroll down the list to find '''libboost_regex-vc71-mt-s.lib'''. Rewrite it to libboost_regex-vc'''80'''-mt-s.lib.
*# Scroll down again to find '''llmozlib.lib''' and rewrite it to llmozlib'''-vc80'''.lib. (This step is not needed on viewer version 1.19.1.0 or later.)
*# Click '''OK''' to close the "Additional Dependencies" dialog, then click OK again to close the "newview Property Pages" dialog box.
* Pick '''ReleaseForDownload''' in the Solution Configurations drop-down box (in the toolbar, next to the green arrow). Repeat the same steps (as for ReleaseNoOpt above) again.
* Depending on what you want to do later (or if you want to do a full and complete conversion), you may also need to perform these steps for the Debug and Release configurations, but for a start it is safe to skip these.

== Special configuration steps for llmedia (1.19.1 or later only) ==

* Right click on the llmedia project on the solution explorer, then choose Properties.
* Choose '''Release''' in the Configuration drop down box on the upper loft of the "llmedia Property pages."
* Choose '''Configuration Properties''' > '''Librarian''' > '''General''' on the tree on the left.
* In '''Additional Dependencies''', there is '''llmozlib2.lib'''. Change it to llmozlib2'''-vc80'''.lib.
* Click OK to close the dialog box.
* Right click on the llmedia project, and choose Properties again.
* Choose '''ReleaseNoOpt''' in the Configuration. Do the same thing as for Release again. Click OK to close the dialog box.
* Right click on the llmedia project, and choose Properties, for the third time.
* Choose '''Debug''' in the Configuration. Do the ''similar'' thing, too. However, Additional Dependencies for Debug includes llmozlib2'''d'''.lib. So, you should change it to llmozlib2'''d-vc80'''.lib. Click OK to close the dialog box.

== Optional steps ==
The following steps are not strictly necessary, unless you want a full and ultra clean conversion (e.g. for sharing with others). These instructions are telegram style, assuming you will do this only after you have aquainted yourselves with the project
* In the Configuration manager (Build menu):
** unclick the build column for '''test''', '''win_crash_logger''' and '''win_updater''' in all configurations '''except ReleaseForDownload'''.
** unclick the build column for '''test''' in '''ReleaseForDownload'''
* For all configurations: In newview, properties, linker input: If you find libraries starting with 'll' (e.g. '''llaudio.lib''', '''llcharacter.lib''', etc.) or find the library '''lscript_library.lib'''), remove them from the list (these libraries are linked through the dependency)
* For all configurations: In newview, properties, linker input: Set '''Ignore Specific Library''' to '''msvcrt.lib;msvcrtd.lib;libc.lib;libcd.lib;'''
* In the Debug configuration, under lscript_compile_fb, indra.y, properties, custom build step, general, command line, make sure you have ''C:\cygwin\bin\mv.exe ytab.hpp ytab.h'' (use the command line from the release configuration as reference).
* In the Debug configuration, also add '''libcmt.lib;''' to the list of specific libraries to ignore.
* In all configurations: the libraries need to be changed from vc71 to vc80 (boost, llmozlib) for the '''test''' project as well, but since '''test''' does not seem to work under VC2005 so far, it's optional.

== Done :-) ==
Congratulations! You've converted ''solution file'' and ''project files''.

'''NOTE:''' You need to do this by hand everytime a new viewer version is released...

Compiling the viewer (MSVS2005)

2008-05-05T15:39:49Z

Nicholaz Beresford: /* Using pre-built solution/project files */

{{Languages}}
{{CompileNav}}

This page explains how you can compile the viewer on Microsoft Windows using Visual Studio 2005 or Visual C++ Express 2005. Note that Lindens are using VS2003 and the whole setup is a bit easier there, so if you have Visual Studio 2003 available, you should read the list of [[Microsoft Visual Studio|supported Visual studio editions]] and you will get less trouble with it than with VS2005.

Currently, only 32 bit binary is tested. There seems to be several trials to produce 64 bit Windows .EXE of the viewer. If you did, please write your experience on this wiki (regardless it was successful or not!)

The following explanation is adjusted for Viewer releases 1.16.0.5 or later. See an [http://wiki.secondlife.com/w/index.php?title=Compiling_the_viewer_%28MSVS2005%29&oldid=22294 older version of this page] for the Viewer releases 1.15 or before.

= Preparing the Development Environment =

== Installing/Configuring VS2005 ==

You need to setup the compiler and Microsoft Development tools as follows:
* Setup [[Microsoft Visual Studio]]

== Getting other Development Tools ==
You will also need some open source development tools.
* [http://www.cygwin.com/ 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. (If you missed one of these, the easiest thing to do is to re-run the entire installation.) Older releases (< r79209) had several hardcoded references that expect Cygwin to be installed at '''C:\cygwin''' in the project files, however current releases rely on the build environment configuration instead.
* [http://www.activestate.com/Products/ActivePython/?mp=1 ActivePython 2.3x or later] - Latest Version is 2.5.1.1
** It is required but can be avoided if you are compiling 1.18 or later viewers. Either download and install or hack the prebuild.bat files as described in [http://jira.secondlife.com/browse/VWR-1267 VWR-1267].
* ActivePerl was recommended for previous versions on this Wiki, but it currently appears, that it is not strictly necessary unless you are planning to build your own version of all libraries (which most likely you don't want to do). So for a start it may be safe to skip it.
*: [http://www.activestate.com/Products/ActivePerl/?mp=1 ActivePerl]

 
 
 

= Downloading Source Code =

You can download the Viewer source codes on the [[source downloads]] page. You can also use a [[version control repository]].

At a minimum, grab the source package and the artwork package, but for a start, also grab the library archive. Many of the libraries can either be compiled from source or downloaded from other sites (see below), but this will take hours and thus it is easiest to also get the package with libraries compiled by the Lindens.

'''WARNING:'''
* If the directory path you keep the SL source in has a space in it, the batch file that copies message_template.msg will fail. So, if you unzip or checkout the source tree into, e.g., "C:\Projects\Dir with space in name\Etc\linden", it won't work!
* You should also avoid using non-ASCII (national) characters in the paths, although some localized versions of the tool puts some as a default...
* Unzip or checkout your source tree into a directory that has as short full pathname as possible, since long paths cause some unexpected trouble during the build.

In other words, the easiest way to get this working is to get ''source'', ''artwork'' and ''libraries'' from the [[source downloads]] page and unpack them all into the same directory/folder, which ideally would be a folder in (or near) the root directory with a short name like ''sl_1_16_0_5''.
 
 
 
 

= Installing Libraries =

SL Viewer depends on some third party libraries. Some of them are open source, some others are not.

== Open Source Libraries ==

You can download the pre-build open source libraries from LL. They are available on [[source downloads]] page. Unzip them into your SL viewer source code directory, maintaining the same directory structure.

'''Note: The VS2003 libraries provided in the [[source downloads]] do not fully work with VS2005 compiled binaries. They will compile with the viewer under VS2005, but the VS2003 libraries are not fully STL compliant. The differences of [http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vclang/html/vclrfnonstandardbehavior.asp non-standard behavior in MSVS] are the known cause.'''

Alternatively, it may be possible to get the source files for the libraries and build by yourself. See [[Compiling the viewer libraries (MSVS 2003)|the instruction for VS2003 users]] if you try it. Please note, however, it is not known that VS2005 can successfully compile the libraries. '''You have been warned.''' (If you can make it, please write the info on this wiki...)
 
 

== Proprietary Libraries ==

Lindens does not inlcude the following proprietary libraries. You will need to follow the instructions to acquire below and copy them to the source path.

However, it probably is 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 (like ''XCOPY OLIB SL_1_16_0_5 /S''). The reason is, that these steps are cumbersome and will have to be repeated for each new release (at least if you keep the source for each release in it's own folder). If you do not want to do this, of course you can just copy the files directly into the linden source paths.

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
 
=== Fmod ===
* Download & extract [http://www.fmod.org/index.php/download fmod 3.75 api for win32] (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\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"
 

=== OpenGL ===
* Download [http://oss.sgi.com/projects/ogl-sample/sdk.html glext.h, glxext.h, and wglext.h]
* Copy them to "linden\libraries\i686-win32\include\GL"
* You don't need any additional *.lib or *.dll for OpenGL.
 

=== ares (viewer 1.18.4 ... for later releases first check if the ares.h and .lib files are in the Linden library package) ===
* download c-ares 1.4 from [http://daniel.haxx.se/projects/c-ares/ here] and unpack it somewhere
* open vc.dsw from the c-ares/vc folder
* remove the adig and ahost projects from the vc workspace
* add ares_getnameinfo.c to the areslib project
* for areslib right-click, properties, Code Generation and set Runtime Library to /MT (release) and /MTd (debug)
* compile debug and release
* copy all c-ares\*.h files to linden\libraries\include\ares\*.h
* copy vc\areslib\Debug\*lib to linden\libraries\i686-win32\lib_debug
* copy vc\areslib\Release\*lib to linden\libraries\i686-win32\lib_release
 

=== openjpeg (viewer 1.18.4 ... for later releases first check if the openjpeg.lib files are in the Linden library package) ===
* download the latest OpenJPEG from [http://www.openjpeg.org/ here]
* open the libopenjpeg.dsw, let it convert and compile it (you'll need the files from the dllopenjpeg sub-project)
* copy debug\openjpeg.lib to linden\libraries\i686-win32\lib_debug
* copy release\openjpeg.lib to linden\libraries\i686-win32\lib_release
* copy release\openjpeg.dll to linden\indra\newview
 

=== Quicktime ''(optional)'' ===
'''Note:''' This download requires a registration at the Apple Quicktime website and take a bit of time. You can avoid using QuickTime if you want, see [[#QuickTime removal|below]] for details. Remember that your viewer '''can't play in-world movies''' if you do so.
* Download & install the [http://connect.apple.com/cgi-bin/WebObjects/MemberSite.woa/203/wa/getSoftware?fileID=20525&code=y&source=x&wosid=4h16WcyMtVfd2P1EffGafkoxFcr 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".
 
 
 

= Configuring for VS2005 =

Lindens use VS2003 to develop the viewer.

You either need to convert ''solution file'' and ''project files'' from VS2003 format to VS2005 format or obtain files compatible with VS2005. You may also need to modify source files to work around the incompatibility between VS2003 and VS2005.

'''Note''': linden\indra\indra_complete_vs8.sln is a solution file already included in the source archive and intended for the Visual Studio 2005, but it '''does not work''' (at least between 1.14.0 and 1.17.0.9 distribution). This may change in a future release, if Lindens include an updated versions of the '''_vc8''' files.

 
 
== Using pre-built solution/project files ==

Currently there is a ZIP file with solution/project files available on the [https://jira.secondlife.com/browse/VWR-1151 JIRA bug tracker issue VWR-1151].

If you are building 1.16 or later, the easiest way towards compiling SL on MS2005 will be to use the zip file mentioned above. The details is as follows:
* Download the appropriate ZIP archive from JIRA.
* Unpack it and copy it onto your linden source tree (allow to overwrite files that have '''_vc8''' in the name).
* Start Visual Studio 2005 (or VC++ Express).
* Use "File > Open > Project/Solution" to open the linden\indra\indra_complete\indra_complete'''_vc8'''.sln (Note: If you plan to work with multiple versions over time, you will find it useful to rename '''indra_complete_vc8.sln''' to something which contains the version number, e.g. '''indra_1_17_0_11_vc8.sln''' before opening.)
* Right click '''newview''' in the frame Solution Explorer and click "Set as StartUp Project".
* Proceed with applying the '''Workarounds''' below (skip '''Manual conversion''').

'''Note:''' The solution/project files depends on the viewer release version. If you are compiling some specific version of the viewer, and the {{JIRA|VWR-1151}} doesn't list the zip file for you version, you can try using the most close one. If, while compiling, you later encounter errors or problems regarding the projects, you may have to do the manual conversion instead.

'''Note:''' If you don't find a matching solution or if it does not work right away, try the manual conversion (see below) because most likely it will be quicker than trying to figure out what's wrong with someone else's patched files.

 

== Manual conversion of the solution/projects ==

If you can not find a set of project files (see above), there are instructions available how to manually do it: [[Converting_project_files_for_MSVS2005]] (this step will take about 5-15 minutes, depending on how proficient you are using VS2005).

 
 
 

== Workarounds ==

There are more compatibility problems between VS2003 and VS2005. You need the following code edits.
 
=== test project/crash_logger/updater ===

For whatever reason, the '''test''' project doesn't work under VS2005. Workaround is to disable it as follows: Right click on the '''test''' and choose '''Unload Project'''.

If you do not plan to create a full download build, you can exclude the '''win_crash_logger''' and '''win_updater''' from newview's project dependencies and unload them also. But be careful with unloading these projects without removing them from the dependencies, because I have seen VS2005 act highly erratic while linking then project when I tried this.
 
=== QuickTime removal ===

If you don't want to get Apple QuickTime SDK, you can disable it as follows:
*linden\indra\llcommon\llpreprocessor.h - near line 58 (the line below '''#elif LL_WINDOWS''')
--50: #define LL_QUICKTIME_ENABLED 1
++50: #define LL_QUICKTIME_ENABLED '''''0'''''

[[LearCale]]: this appears to be in linden\indra\llmedia\llmediabase.h as of client 1.20

* Pick '''ReleaseNoOpt''' in the Solution Configurations drop-down box beside the green arrow under the tool bar, and do the followings on the Solution Explorer frame:
*Click '''newview''' to select it alone.
**Choose Properties.
**Under Configuration Properties > Linker > Input, click '''Additional Dependencies''' on the right to show a button labeled "'''...'''" on it at the very right on the line, then click the '''...''' button.
**Scroll down the list to find '''qtmlclient.lib'''. Delete this single line.
**Click '''OK''' to close the "Additional Dependencies" dialog, then click OK again to close the "newview Property Pages" dialog box.
* Pick '''ReleaseForDownload''' in the Solution Configurations drop-down box. Click '''newview''' to select it alone and do the same thing again.
 
 
 

= Ready, Set, Build! =

== Building ==
* Build either '''ReleaseNoOpt''' (for debugging) or '''ReleaseForDownload''' (for production code).
* To do this, pick either in the Solution Configurations drop-down box beside the green arrow under the tool bar.
* Make sure '''newview''' is set as the startup project (otherwise set from newview's right-click menu).
* Select Build-Menu > Build Solution or press F7.
* newview_noopt.exe will be built in linden\indra\newview\ReleaseNoOpt or SecondLife.exe will be linden\indra\newview\ReleaseForDownload.
 

== Common compile errors ==
* See [[common compilation problems]] if you run into other errors while building.
 
== Running ==
* You can run the viewer by '''Debug > Start Debugging''' or '''Debug > Start Without Debugging''' in Visual Studio.
* To run it outside VS, create a shortcut to SecondLife.exe, and change the start location to linden\indra\newview\ (All the .dll will be found there.)
* Alternately copy the exe (possibly rename it) to your "c:\program files\secondlife" folder.
 
== Debugging Info/Configurations ==
* Usually you will either use '''ReleaseNoOpt''' or the '''ReleaseForDownload''' configuration.
* '''ReleaseNoOpt''' (not optimized) compiles faster and has more debugging information, but this comes at a runtime penalty of about 50% of your FPS in busy areas, compared to ReleaseForDownload build.
* '''ReleaseForDownload''' also has debugging information and runs fine in the debugger (although at times you may miss access to some local variables).
* '''ReleaseNoOpt''' comes with a seperate debugging console window opens and stays open for the duration of your session, but you can access the same information also by pressing Shift+Ctrl+4 in the viewer (all builds).
* The debug console log can also be redirected to a file if you add "2>secondlife.log" to the command line (Newview, Properties, Debugging, Command line arguments).
* If you want to build a '''Debug''' configuration, see the specific section with compile instructions on [[finding leaks]]
 

== Problems Running? ==
* '''Inventory errors''': If you're getting errors while trying to load your inventory, try [[Help:Stuck logging in|clearing your cache and deleting other temporary files]].
* '''Missing smime3 DLL''': Those are parts of the integrated web browser. Copy 'smime3.dll', 'nss3.dll', 'softokn3.dll', and 'ssl3.dll' files from your official client's main folder to "linden\indra\newview".
* '''Can't connect''': In the debug builds there is a selection box on the login screen to select the server to connect to. '''Agni''' is the production grid, '''aditi''' is the beta grid. (There seems to be a bug in this part of the code, you may have to make your selection, close the viewer and repoen it, before you can connect to the selected grid).
 
 
= Submit Patches =
This is probably faaar down the road, but if you make changes to the source and want to submit them, see the page about [[submitting patches]].

Alternate viewers

2008-04-15T12:18:54Z

Nicholaz Beresford: wrap up for the nichoalz edition

== Introduction ==

The [[Extended_FAQ|Extended FAQ]] states that it is okay to create and distribute homebrew viewers as long they adhere to the respective licenses for code usage and server usage.

The code itself is licensed under {{OSWebsite|gplv2|alt=the GNU General Public License (GPL)}}, which governs modification and redistribuition of the source code. Use of Linden Lab's servers will still be governed by [http://secondlife.com/corporate/tos.php the Second Life Terms of Service]].

'''Homebrew viewers are obviously not associated with LindenLab, are governed by their own respective licenses. LindenLab is not responsible for any desired or undesired results in association with those viewers.'''

''Note to authors: If you make a viewer available make sure to include platform, version numbers and dates.''

 
 
 

== Able Edition ==

=== Description ===

This is a Windows viewer is an unofficial build which adds a [https://jira.secondlife.com/browse/VWR-1017 Mute Visibility] feature, which allows objects in-world to be rendered partially or entirely invisible.

=== Extra Features ===
* Mute Visibility
* Improvements to the Mute List
* Muting objects applies to entire linksets

=== Links ===
* Website: [http://ablewhitman.blogspot.com/ Able Whitman on Blogspot]
* Direct download link: http://ablewhitman.org/viewer/
* Source code: http://ablewhitman.org/viewer/

 
 
 

== Dale Glass Edition ==

=== Description ===

This is a Windows (soon Linux) viewer which adds new experimental features. The features are intended to give users more information about the world and to simplify moderation by making it easier to tell where people are and what they're doing.

=== Extra Features ===
* Avatar Scanner
** Shows nearby avatars, roughly in drawing distance range.
** Shows name, age, payment info, current activity.
** Land and estate commands for ejecting/banning multiple avatars at once
** Integration with Luskwood moderation tools
** Buttons to open profile, IM, teleport to or track selected avatars
* Event Log: Experimental feature, shows a list of active particle effects (soon sounds too), and their owners. Allows moving camera to emitter.
* Branding: Replaces LL branding with my own. Different login page, checks for updates against my server.
* Logging of the owner and location of speaking objects

=== Links ===
* Website: http://sl.daleglass.net
* Blog: http://daleglass.wordpress.com
* Direct download link: http://sl.daleglass.net/download
* Source code: http://svn.daleglass.net/sl/release/ ( [[User:Dale_Glass#Subversion_Repository|subversion]] )

 
 
 

== Nicholaz Edition (Discontinued) ==

=== Description ===

These are Windows viewer based on SL builds with a focus on stability, usability and performance (see [http://www.blueflash.cc/users/nicholaz/EyeCandy/!!Installation.txt Installation.txt] for homebrew disclaimer). Mac and Linux variants are available through other open sourcers (links on the website).

'''Note:''' Development of this viewer is discontinued as of 1.19.1. Older versions are still working, download links can be found [http://nicholaz-beresford.blogspot.com/ here] (look for "Release" posts).

=== Extra Features ===
* Improved stability
* Lower memory footprint
* GUI redesigns
* Workarounds for common annoyances (Group IM Filtering, "Release Key" button, etc.)
* see [http://www.blueflash.cc/users/nicholaz/EyeCandy/!Changes.txt Changes.txt] for all details

=== Links ===
* Website: [http://nicholaz-beresford.blogspot.com/ Nicholaz Beresford on Blogspot]
* Direct download link: [http://www.blueflash.cc/users/nicholaz Download versions of this viewer]
* Source code: Look at the [http://www.blueflash.cc/users/nicholaz download site] for the source-xxx-zip files in the respective folders and see the readme.txt inside the archives

 
 
 

== Marine Edition ==

=== Description ===

This viewer, codename "'''RestrainedLife'''" is an attempt at enhancing the experience of people who practice BDSM in Second Life. It is used jointly with simple scripts made to use its features in-world, such as making an attached object undetachable, preventing chat and such. An '''API''' (Application Programming Interface, a text file) is provided so that every content creator can create their own scripts to interface their own items to the viewer and use its features.

=== Extra Features ===
* Attachments can be made undetachable
* Chat and IM prevention on demand, with exceptions if needed
* Teleport and sit-tp prevention on demand, with exceptions if needed
* Editing and Rezzing prevention on demand
* Adding/Removing clothes on demand, + force remove clothes and force remove unlocked attachments
* Force sit and prevent stand up (even after a relog) on demand
* Manual (by IM) and automatic (by script) version checking
* API for content creators

=== Links ===
* Website: [http://realrestraint.blogspot.com/ Marine Kelley's blog on Blogspot]
* Direct download link to the Windows viewer: [http://www.erestraint.com/realrestraint Download for Windows] (Executable and readme)
* Direct download link to the MacOS X viewer: [http://www.erestraint.com/realrestraint Download for MacOS X] (Executable and readme, courtesy of Mo Noel)
* Direct download link to the Linux viewer: [http://www.loomiverse.net/RestrainedLife Download for Linux] (Executable and readme, courtesy of Loom Kish)
* Source code and text API : [http://www.erestraint.com/realrestraint Download] (Text files)
* API as a wiki page : [https://wiki.secondlife.com/wiki/RestrainedLifeAPI API] (Wiki format)
* Specification to interface cages & furnitures with the viewer through the use of a relay : [https://wiki.secondlife.com/wiki/LSL_Protocol/RestrainedLifeRelaySpecs Relay Spec] (Wiki format)

=== Version and timestamp ===

* Version : 1.10.4, compiled on SL official viewer 1.19.0.5
* Date : 02/15/2008

 
 
 

== Henri Beauchamp Edition ==

=== Description ===

This viewer, codename "'''Cool SL Viewer'''" combines elements of several of the other viewers, as well as some extra patches very carefully tested.

=== Extra Features ===
* Reverses many of the unpopular interface changes made in the transition to voice being standard (including reinstating the packet loss and bandwidth indicators, and optionally reinstating the old, more visible, tracking dots in the mini-map).
* Implements the "Restrained Life" API discussed more fully in the Marine Edition client.
* Defines double-click default actions for many types of inventory.
* Allows to optionally prevent IMs to show in the main chat.
* Allows to hide the "Release Keys" and/or the "Master volume" in the panel overlay.
* MUD/MUSH/MUCK/MU* style "poses"
* Various patches by Nicholaz Beresford, Gigs Taggart, Blakar Ogre, and others.

=== Links ===
* Website: [http://sldev.free.fr/ The Cool SL Viewer homepage]
* Direct download link to the Linux viewer: [http://sldev.free.fr/SecondLife_i686_1_19_0_5_CoolRelease_6-diff_files.tar.bz2 Download for Linux]
* MacOS X viewer: [http://radio-boomslang.shacknet.nu/~bb/articles/cool-viewer-mac/index.html See Barney Boomslang's site] for files and instructions.
* Windows viewer: [http://my.opera.com/boylane/blog/ See Boy Lane's site] for files and instructions.
* Source code: The standard Linden codebase is used, with the addition of the patches listed and linked to on the homepage.

=== Version and timestamp ===

* Version : i686 1.19.0.5 CoolRelease 6
* Date : 2008/04/10

* Version : i686 1.19.1.4 CoolRelease 3
* Date : 2008/04/10

 
 
 

== Onrez Viewer ==

=== Description ===

The Onrez viewer was made by the Onrez company in connection with a Second Life themed story on the high tech forensics based TV show "CSI: New York".

=== Extra Features ===
* A back and history button for teleports
* In-viewer web browsing.

=== Links ===
* http://viewer.onrez.com for the download

=== Comment ===
The source code for this viewer is closed source.

== RealXtend Edition ==

=== Description ===

The realXtend viewer is a heavily modified version of the Linden Labs' Second Life client by a partnership of two Finnish companies, ADMINO technologies and LudoCraft.

=== Extra Features ===
* Second life compatibility mode for use in SL and Opensim worlds
* Teleports between realXtend and Secondlife

=== Links ===
* Website: [http://www.realxtend.org/]
* Direct download link: http://www.realxtend.org/downloads.html
* Source code: http://sourceforge.net/projects/realxtendviewer/

Alternate viewers

2008-04-06T23:43:16Z

Nicholaz Beresford:

== Introduction ==

The [[Extended_FAQ|Extended FAQ]] states that it is okay to create and distribute homebrew viewers as long they adhere to the respective licenses for code usage and server usage.

The code itself is licensed under {{OSWebsite|gplv2|alt=the GNU General Public License (GPL)}}, which governs modification and redistribuition of the source code. Use of Linden Lab's servers will still be governed by [http://secondlife.com/corporate/tos.php the Second Life Terms of Service]].

'''Homebrew viewers are obviously not associated with LindenLab, are governed by their own respective licenses. LindenLab is not responsible for any desired or undesired results in association with those viewers.'''

''Note to authors: If you make a viewer available make sure to include platform, version numbers and dates.''

 
 
 

== Able Edition ==

=== Description ===

This is a Windows viewer is an unofficial build which adds a [https://jira.secondlife.com/browse/VWR-1017 Mute Visibility] feature, which allows objects in-world to be rendered partially or entirely invisible.

=== Extra Features ===
* Mute Visibility
* Improvements to the Mute List
* Muting objects applies to entire linksets

=== Links ===
* Website: [http://ablewhitman.blogspot.com/ Able Whitman on Blogspot]
* Direct download link: http://ablewhitman.org/viewer/
* Source code: http://ablewhitman.org/viewer/

 
 
 

== Dale Glass Edition ==

=== Description ===

This is a Windows (soon Linux) viewer which adds new experimental features. The features are intended to give users more information about the world and to simplify moderation by making it easier to tell where people are and what they're doing.

=== Extra Features ===
* Avatar Scanner
** Shows nearby avatars, roughly in drawing distance range.
** Shows name, age, payment info, current activity.
** Land and estate commands for ejecting/banning multiple avatars at once
** Integration with Luskwood moderation tools
** Buttons to open profile, IM, teleport to or track selected avatars
* Event Log: Experimental feature, shows a list of active particle effects (soon sounds too), and their owners. Allows moving camera to emitter.
* Branding: Replaces LL branding with my own. Different login page, checks for updates against my server.
* Logging of the owner and location of speaking objects

=== Links ===
* Website: http://sl.daleglass.net
* Blog: http://daleglass.wordpress.com
* Direct download link: http://sl.daleglass.net/download
* Source code: http://svn.daleglass.net/sl/release/ ( [[User:Dale_Glass#Subversion_Repository|subversion]] )
 
 
 

== Nicholaz Edition (Discontinued) ==

=== Description ===

Note: Development of this viewer is discontinued.

This is a Windows viewer based on SL builds with various preliminary bug fix patches applied. Nonetheless it is of course an unofficial build. See [http://www.blueflash.cc/users/nicholaz/!!Installation.txt Installation.txt], [http://www.blueflash.cc/users/nicholaz/!Changes.txt Changes.txt] for more information.

=== Extra Features ===
* Particle system improved
* Different memory management for image list
* Many patches from the bug tracker which are not yet in the official viewer
* Old style GUI and GUI redesigns for the voice viewer

=== Links ===
* Website: [http://nicholaz-beresford.blogspot.com/ Nicholaz Beresford on Blogspot]
* Direct download link: [http://www.blueflash.cc/users/nicholaz Download versions of this viewer]
* Source code: Look at the download site for the source-xxx-zip archive

 
 
 

== Marine Edition ==

=== Description ===

This viewer, codename "'''RestrainedLife'''" is an attempt at enhancing the experience of people who practice BDSM in Second Life. It is used jointly with simple scripts made to use its features in-world, such as making an attached object undetachable, preventing chat and such. An '''API''' (Application Programming Interface, a text file) is provided so that every content creator can create their own scripts to interface their own items to the viewer and use its features.

=== Extra Features ===
* Attachments can be made undetachable
* Chat and IM prevention on demand, with exceptions if needed
* Teleport and sit-tp prevention on demand, with exceptions if needed
* Editing and Rezzing prevention on demand
* Adding/Removing clothes on demand, + force remove clothes and force remove unlocked attachments
* Force sit and prevent stand up (even after a relog) on demand
* Manual (by IM) and automatic (by script) version checking
* API for content creators

=== Links ===
* Website: [http://realrestraint.blogspot.com/ Marine Kelley's blog on Blogspot]
* Direct download link to the Windows viewer: [http://www.erestraint.com/realrestraint Download for Windows] (Executable and readme)
* Direct download link to the MacOS X viewer: [http://www.erestraint.com/realrestraint Download for MacOS X] (Executable and readme, courtesy of Mo Noel)
* Direct download link to the Linux viewer: [http://www.loomiverse.net/RestrainedLife Download for Linux] (Executable and readme, courtesy of Loom Kish)
* Source code and text API : [http://www.erestraint.com/realrestraint Download] (Text files)
* API as a wiki page : [https://wiki.secondlife.com/wiki/RestrainedLifeAPI API] (Wiki format)
* Specification to interface cages & furnitures with the viewer through the use of a relay : [https://wiki.secondlife.com/wiki/LSL_Protocol/RestrainedLifeRelaySpecs Relay Spec] (Wiki format)

=== Version and timestamp ===

* Version : 1.10.4, compiled on SL official viewer 1.19.0.5
* Date : 02/15/2008

 
 
 

== Henri Beauchamp Edition ==

=== Description ===

This viewer, codename "'''Cool SL Viewer'''" combines elements of several of the other viewers, as well as some extra patches very carefully tested.

=== Extra Features ===
* Reverses many of the unpopular interface changes made in the transition to voice being standard (including reinstating the packet loss and bandwidth indicators, and optionally reinstating the old, more visible, tracking dots in the mini-map).
* Implements the "Restrained Life" API discussed more fully in the Marine Edition client.
* Defines double-click default actions for many types of inventory.
* Allows to optionally prevent IMs to show in the main chat.
* Allows to hide the "Release Keys" and/or the "Master volume" in the panel overlay.
* MUD/MUSH/MUCK/MU* style "poses"
* Various patches by Nicholaz Beresford, Gigs Taggart, Blakar Ogre, and others.

=== Links ===
* Website: [http://sldev.free.fr/ The Cool SL Viewer homepage]
* Direct download link to the Linux viewer: [http://sldev.free.fr/SecondLife_i686_1_19_0_5_CoolRelease_4-diff_files.tar.bz2 Download for Linux]
* Direct download link to the MacOS X viewer: None available yet
* Windows viewer: [http://my.opera.com/boylane/blog/ See Boy Lane's site] for files and instructions.
* Source code: The standard Linden codebase is used, with the addition of the patches listed and linked to on the homepage.

=== Version and timestamp ===

* Version : i686 1.19.0.5 CoolRelease 4
* Date : 2008/03/29

* Version : i686 1.19.1.4 CoolRelease 1
* Date : 2008/03/30

 
 
 

== Kirstens Viewers ==

=== Description ===

These Viewers are custom built for win32 platforms, and take code from the SVN and patches from 3rd parties or jira, and should be considered experimental compared to the standard release client, they are however compiled more or less exclusively for high end intel based machines for best performance or to fix specific problems and have proved very stable with minor performance increases and added stability in some cases.

Kirsten also builds Viewers based off snapshots, very experimental and sometimes not yet available from the official website.

=== Extra Features ===
* Compiled For Maximum Performance on Intel P4's or better
* Quicker Loading,less memory leaks (19hours login with no relog or crash, Thanks to Phantium Longwell for the Test )
* Congrats Also To Paulo on a 20hr+ Session on Kirstens Windlight
* Specific Viewers to Fix specific problems
* Viewers released in line with official releases,usually within hours.
* Snapshots of the Dazzle FL viewer, and WL snapshots

* Redesigned Skins on Certain Viewers

=== Links ===
* http://code.google.com/p/kirstens-secondlife-viewers/
* http://www.armyof4.com/Kirstenlee/

=== Version and timestamp ===

* Version : Kirstens Dazzle(VERY stable viewer with custom UI )
* Version : Kirstens Windlight 1-19-1 build 83563 Snapshot & 1-19-1-2 Sldev r386 custom also available
* Version : Kirstens Ext Edition - Intel Dual/Quad Core only(NO AMD)
* Date : 03/25/2008

== Onrez Viewer ==

=== Description ===

The Onrez viewer was made by the Onrez company in connection with a Second Life themed story on the high tech forensics based TV show "CSI: New York".

=== Extra Features ===
* A back and history button for teleports
* In-viewer web browsing.

=== Links ===
* http://viewer.onrez.com for the download

=== Comment ===
The source code for this viewer is closed source.

Common compilation problems

2007-12-21T14:22:08Z

Nicholaz Beresford: /* Cannot open include file: 'glh/glh_linear.h' or 'glh/glh_convenience.h' */

{{CompileNav}}

= General Problems =

* Make sure you download not only the source, but the artwork zipfile, and the appropriate zipfile/tarball of libraries for your platform

= Windows =

== Unresolved external symbol _CLSID_DxDiagProvider/_IID_IDxDiagProvider ==
* ''newview error LNK2001: unresolved external symbol _CLSID_DxDiagProvider''
* ''newview error LNK2001: unresolved external symbol _IID_IDxDiagProvider''

These errors reportedly occur with MSVC 2003 and certain versions of the DirectX SDK. To workaround, edit lldxhardware.cpp and replace the following (line 35):

#include <dxdiag.h>
with...
#define INITGUID
#include <dxdiag.h>
#undef INITGUID

== Cannot open input file 'dxguid.lib' ==
* ''fatal error LNK1181: cannot open input file 'dxguid.lib' in ...''

If you are using a fairly recent DirectX SDK ("December 2006" or newer), your VC++ Libraries Directory may be wrong because the SDK's lib folder now has 2 sub-folders for x64 and x86. Try changing the path from ''C:\Program Files\Microsoft DirectX SDK (December 2006)\Lib'' to ''C:\Program Files\Microsoft DirectX SDK (December 2006)\'' '''Lib\x86'''
 
 
== Cannot open input file 'dxerr8.lib' ==
* ''fatal error LNK1104: cannot open file 'dxerr8.lib'''

If you are using the most recent DirectX SDK ("November 2007"), the file dxerr8.lib does no longer exist. To fix this, you'll need to change the newview project to include 'dxerr9.lib' instead. To do this, right-lick newview > Configuration Properties > Linker > Input, click Additional Dependencies on the right to show a button labeled "..." on it at the very right on the line, then click the ... button. Scroll down the list to find 'dxerr8.lib'. Rewrite it to 'dxerr9.lib'. Remember to do this for both the ReleaseForDownload and the ReleaseNoOpt Configurations.
 
 

== Cannot open include file: 'ytab.h': No such file or directory ==
* ''indra.l (20) : fatal error C1083: Cannot open include file: 'ytab.h': No such file or directory.''
Workaround: Manually copy "linden\indra\lscript\lscript_compile\ytab.hpp" to "linden\indra\lscript\lscript_compile\ytab.h" and build again.

Note: The underlying issue is that in indra.y there is a postbuild step which should do this automatically, but which is missing in some configurations (e.g. in Debug builds).
 
 
== Cannot open include file: 'png.h': No such file or directory ==
* ''imagepng.cpp : fatal error C1083: Cannot open include file: 'libpng12/png.h': No such file or directory.''
There are a couple of files missing since the 1.17. distribution. You can either get the missing files from the internet (from the libpng and zlib projects) or download a set with just the missing files from [http://www.blueflash.cc/users/nicholaz/~libs here] (see the readme.txt inside the png archive there).
 
 
== Cannot open include file: 'glh/glh_linear.h' or 'glh/glh_convenience.h' ==
These files are currently missing from Linden Windlight distributions. See [https://jira.secondlife.com/browse/VWR-3415 JIRA VWR-3415] or grab a copy from [http://www.blueflash.cc/users/nicholaz/~libs here] and put the files into a folder named linden/libraries/include/glh.
 
 

== Errors relating to "template_verifier.py" ==
With version 1.18 a template verifier script written in Python is used to ensure the message template is correct. In some distributions the file was missing. You will also get an error if you have skipped the Python install. In both cases it is safe to hack the prebuild.bat file in the newview folder as described on the JIRA [http://jira.secondlife.com/browse/VWR-1267 VWR-1267]
 
 

== Missing resources ==
* ''.\res\newViewRes.rc(64) : error RC2135 : file not found: ll_icon.ico''
Some releases have missing files, which were reported to be last seen in the '''1.14.0.1''' release.
* Go to the [[source downloads]] page and grab the [[http://secondlife.com/developers/opensource/downloads/2007/04/slviewer-src-1.14.0.1.zip '''1.14.0.1''' viewer]] sources.
* Explore the archive to "linden/indra/newview/res" folder and extract content to your "linden/indra/newview/res" folder into current revision.
Missing folder in recent release, "'''1.17.0.12'''" which causes the SecondLife to hang while loading into the world.
* Go to the previous source and copy the missing folder, "Character" and place it into the "newview" folder
 
== Error code from "Copying message template" ==
* ''newview error PRJ0019: A tool returned an error code from "Copying message template"''
This is caused by the script trying to do a copy command, but the source path isn't in quotes. Open up newview.vcproj in notepad, and near the bottom there are 4 line that say:
CommandLine="copy $(InputPath) .\app_settings\message_template.msg
replace them with
CommandLine="copy &quot;$(InputPath)&quot; .\app_settings\message_template.msg
The source and destination paths on line 158 may also require wrapping in quotes. In which case:
CommandLine="copy $(TargetDir)\$(TargetFileName) $(ProjectDir)
should become:
CommandLine="copy &quot;$(TargetDir)\$(TargetFileName)&quot; &quot;$(ProjectDir)&quot;
 
== Can not find library ll*.lib ==
If you get a compile error for missing libraries with names of the projects (lscript_compile.lib, llaudio.lib, llcharacter.lib, etc.) go to newview > Properties > Linker > Input and remove these from the list of input libraries (they will be linked through the dependencies and should not be in the list).
 
 
== Cannot open include file: 'windows.h' ==
If you run into this problem:
..\..\..\boost/regex/v4/fileiter.hpp(44) : fatal error C1083: Cannot open include file: 'windows.h': No such file or directory
Fix it with this: (thanks Fairlight!)
set INCLUDE=C:\Program Files\Microsoft Platform SDK for Windows Server 2003 R2\Include;%INCLUDE%
set LIB=C:\Program Files\Microsoft Platform SDK for Windows Server 2003 R2\Lib;%LIB%

 
== Unresolved external symbol "int __cdecl lscript_compile" (VS2005) ==
* ''llcompilequeue.obj : error LNK2019: unresolved external symbol "int __cdecl lscript_compile(char const *,char const *,char const *,int)" (?lscript_compile@@YAHPBD00H@Z) referenced in function "protected: void __thiscall LLFloaterCompileQueue::compile(char const *,class LLUUID const &)" (?compile@LLFloaterCompileQueue@@IAEXPBDABVLLUUID@@@Z)''
* ''llpreviewscript.obj : error LNK2001: unresolved external symbol "int __cdecl lscript_compile(char const *,char const *,char const *,int)" (?lscript_compile@@YAHPBD00H@Z)''

This is not entirely clear, but there seems to be a problem with VS2005 if projects are unloaded while being in the dependency tree. I have seen this error while I had win_crash_logger and win_updater unloaded from the project tree and the problem went away when I loaded them back and excluded them from the newview dependency first.

Also make sure that in newview, properties, linker, input, input libraries, no libraries named ll*.lib and lscript_compile.lib are listed there (remove them if you find them).
 
 

== Unresolved external symbol __invalid_parameter_noinfo (VS2005) ==
* ''llmozlib-vc80.lib(llembeddedbrowserwindow.obj) : error LNK2019: unresolved external symbol __invalid_parameter_noinfo referenced''

You are most likely trying a debug build under VS2005. For debug builds, see the compile instruction section on [[finding_leaks]]
 
 

== Cannot open include file: 'ares.h' ==
download src from http://daniel.haxx.se/projects/c-ares/

compile c-ares-1.4.0/vc/areslib

copy c-ares-1.4.0/vc/areslib/Release/areslib.lib to linden/libraries/i686-win32/lib_release and to lib_debug

copy c-ares-1.4.0/*.h to linden/libraries/i686-win32/include/ares
 
 

== Other (older) notes ==
* Mozilla is not compatible with visual studio 2005, so we have not migrated the codebase, so we do not know if it works.

* Added my errors at [[User:Adam_Zaius/MSVS2005 Errors]] [[User:Adam Zaius|Adam Zaius]] 09:40, 8 January 2007 (PST)

* To minimize the number of warnings for now: in C/C++-Preprocessor add ';_CRT_SECURE_NO_DEPRECATE' to the Preprocessor Definitions, that will supress deprecation warnings --[[User:Artm Udal|Artm Udal]] 12:42, 8 January 2007 (PST)

 

= Mac OS X =

Getting:

*/linden/indra/newview/../llwindow/llglheaders.h:377:31: error: GL/glh_extensions.h: No such file or directory
** This means you didn't [[Compiling the viewer (Mac OS X)#Viewer Source, Libraries, and Artwork|merge the libraries]] right.

 

= Linux =

==== Packaging errors ====

The final packaging step may fail with errors about the manifest if you are not using the slviewer-linux-libs bundle; in this case, if you still wish to end up with an end-user viewer package incorporating your own libraries, you can edit the manifest file found at indra/newview/viewer_manifest.py

==== Various Compilation problems ====

* "Unable to initialize communications"
** If the viewer just displays the error message " Unable to initialize communications" and exits, it can't find message_template.msg. You did remember to copy it over, right?

* Blino's SL build/linking patches for '''gcc4''': http://svn.mandriva.com/cgi-bin/viewvc.cgi/packages/cooker/secondlife/current/
* objcopy: 'newview/linux_tools/exposed-symbols.txt': No such file
** Tofu says... 'This is an omission from our manifest which I'll fix. Meanwhile it's a safe fix to create an empty file with that name.'

* Something like: /usr/bin/ld: cannot find -lz
** Nadia says: Install the zlib development headers. (Ubuntu package zlib1g-dev, Red Hat zlib-devel.)

* Something like: indra.y.cpp:17: error: previous declaration of `int yyparse()'
** Tofu says... 'This appears to be a problem with some versions of flex/bison. A resident reports success when comment out the #ifdef __cplusplus lines in lscript/lscript_compile/indra.y'
** Nadia says: install the zlib development headers first and try recompiling. Commenting out those lines results in a error indra.l:666: undefined
* Linking failures ("script not found") due to spaces in the LINKFLAGS variable?
** I saw a [http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4665538 report], and modified the SConstruct file to drop the trailing arguments (and spaces) in LINKFLAGS.

* Building [https://lists.secondlife.com/pipermail/sldev/2007-January/000091.html 20070112a] using ''BUILD=releasefordownload'' I get many ''[: 89: ==: unexpected operator'' errors; ''cp: target `SecondLife_i686_1_13_1_7/app_settings/*’ is not a directory'' error, and same thing for character, fonts, help, skins, res-sdl; ''[: 111: ==: unexpected operator, [: 120: SecondLife_i686_1_13_1_7.tar.bz2: unexpected operator''. I can succesfully run the client from the source tree.
** i think this has been fixed --[[User:Signore Iredell|Signore Iredell]] 06:09, 9 June 2007 (PDT)

* scons: *** While building `['.../linden/indra/i686-linux-client-release/lscript/lscript_compile/indra.l.cpp']': Don't know how to build a file with suffix `.l'.
** You probably don't have all the dependencies installed (I had the same problem). Check that you have flex and bison. --[[User:Random73 Janus|Random73 Janus]] 07:43, 16 May 2007 (PDT)

* Something like: linden/indra/i686-linux-client-release/llrender/llimagegl.cpp:122: error: `glActiveTextureARB' was not declared in this scope
** Tofu says... 'You'll need to install OpenGL headers if you don't already have them: gl.h, glext.h, glu.h (The ones from 'mesa' should work)
** two residents report good luck on Gentoo after doing 'eselect opengl set xorg-x11' (but note!! You must know what you're doing; this may change your default system OpenGL drivers, and you will probably want to change them back again after the compile, e.g. 'eselect opengl set nvidia')'

*Building Shared Library ELFIO [[Compiling_the_viewer_%28Linux%29]] on AMD64 ubuntu 6.10
g++-3.4 -shared *.o -o libelfio.so
/usr/bin/ld: ELFIDynamic.o: relocation R_X86_64_32 against `a local symbol' can
not be used when making a shared object; recompile with -fPIC
ELFIDynamic.o: could not read symbols: Bad value'''

* Building Client on Ubuntu 7.04 AMD64
/usr/bin/ld: skipping incompatible /home/dereck/Desktop/SLdev/linden/libraries/i686-linux/lib_release_client/libopenjpeg.a when searching for -lopenjpeg
/usr/bin/ld: cannot find -lopenjpeg
collect2: ld returned 1 exit status
** I went to the OpenJPEG website, downloaded the source, compiled for my system, installed it. The VWR compile was happy after that. Although it's not done yet and I'm still fixing another error, that I assume is unrelated.

==== scons got wild ====

* AttributeError: SConsEnvironment instance has no attribute 'CFile'
: This probably means you have no bison, flex, or equivalent tools installed on the standard locations on your system.
:* When your system has no bison installed, the above message will be supplemented as:
env.CFile(target=build_dir+'/lscript/lscript_compile/indra.y.c', source='lscript/lscript_compile/indra.y')
:* When your system has no flex installed, the above message will be supplemented as:
env.CFile(target=build_dir+'/lscript/lscript_compile/indra.l.cpp', source='lscript/lscript_compile/indra.l')
: Installing the appropriate package should solve this issue.

Common compilation problems

2007-12-21T14:21:07Z

Nicholaz Beresford: glh includes missing

{{CompileNav}}

= General Problems =

* Make sure you download not only the source, but the artwork zipfile, and the appropriate zipfile/tarball of libraries for your platform

= Windows =

== Unresolved external symbol _CLSID_DxDiagProvider/_IID_IDxDiagProvider ==
* ''newview error LNK2001: unresolved external symbol _CLSID_DxDiagProvider''
* ''newview error LNK2001: unresolved external symbol _IID_IDxDiagProvider''

These errors reportedly occur with MSVC 2003 and certain versions of the DirectX SDK. To workaround, edit lldxhardware.cpp and replace the following (line 35):

#include <dxdiag.h>
with...
#define INITGUID
#include <dxdiag.h>
#undef INITGUID

== Cannot open input file 'dxguid.lib' ==
* ''fatal error LNK1181: cannot open input file 'dxguid.lib' in ...''

If you are using a fairly recent DirectX SDK ("December 2006" or newer), your VC++ Libraries Directory may be wrong because the SDK's lib folder now has 2 sub-folders for x64 and x86. Try changing the path from ''C:\Program Files\Microsoft DirectX SDK (December 2006)\Lib'' to ''C:\Program Files\Microsoft DirectX SDK (December 2006)\'' '''Lib\x86'''
 
 
== Cannot open input file 'dxerr8.lib' ==
* ''fatal error LNK1104: cannot open file 'dxerr8.lib'''

If you are using the most recent DirectX SDK ("November 2007"), the file dxerr8.lib does no longer exist. To fix this, you'll need to change the newview project to include 'dxerr9.lib' instead. To do this, right-lick newview > Configuration Properties > Linker > Input, click Additional Dependencies on the right to show a button labeled "..." on it at the very right on the line, then click the ... button. Scroll down the list to find 'dxerr8.lib'. Rewrite it to 'dxerr9.lib'. Remember to do this for both the ReleaseForDownload and the ReleaseNoOpt Configurations.
 
 

== Cannot open include file: 'ytab.h': No such file or directory ==
* ''indra.l (20) : fatal error C1083: Cannot open include file: 'ytab.h': No such file or directory.''
Workaround: Manually copy "linden\indra\lscript\lscript_compile\ytab.hpp" to "linden\indra\lscript\lscript_compile\ytab.h" and build again.

Note: The underlying issue is that in indra.y there is a postbuild step which should do this automatically, but which is missing in some configurations (e.g. in Debug builds).
 
 
== Cannot open include file: 'png.h': No such file or directory ==
* ''imagepng.cpp : fatal error C1083: Cannot open include file: 'libpng12/png.h': No such file or directory.''
There are a couple of files missing since the 1.17. distribution. You can either get the missing files from the internet (from the libpng and zlib projects) or download a set with just the missing files from [http://www.blueflash.cc/users/nicholaz/~libs here] (see the readme.txt inside the png archive there).
 
 
== Cannot open include file: 'glh/glh_linear.h' or 'glh/glh_convenience.h' ==
These files are currently missing from Linden Windlight distributions. See [https://jira.secondlife.com/browse/VWR-3415 JIRA VWR-3415] or grab a copy from [http://www.blueflash.cc/users/nicholaz/~libs here].
 
 
== Errors relating to "template_verifier.py" ==
With version 1.18 a template verifier script written in Python is used to ensure the message template is correct. In some distributions the file was missing. You will also get an error if you have skipped the Python install. In both cases it is safe to hack the prebuild.bat file in the newview folder as described on the JIRA [http://jira.secondlife.com/browse/VWR-1267 VWR-1267]
 
 

== Missing resources ==
* ''.\res\newViewRes.rc(64) : error RC2135 : file not found: ll_icon.ico''
Some releases have missing files, which were reported to be last seen in the '''1.14.0.1''' release.
* Go to the [[source downloads]] page and grab the [[http://secondlife.com/developers/opensource/downloads/2007/04/slviewer-src-1.14.0.1.zip '''1.14.0.1''' viewer]] sources.
* Explore the archive to "linden/indra/newview/res" folder and extract content to your "linden/indra/newview/res" folder into current revision.
Missing folder in recent release, "'''1.17.0.12'''" which causes the SecondLife to hang while loading into the world.
* Go to the previous source and copy the missing folder, "Character" and place it into the "newview" folder
 
== Error code from "Copying message template" ==
* ''newview error PRJ0019: A tool returned an error code from "Copying message template"''
This is caused by the script trying to do a copy command, but the source path isn't in quotes. Open up newview.vcproj in notepad, and near the bottom there are 4 line that say:
CommandLine="copy $(InputPath) .\app_settings\message_template.msg
replace them with
CommandLine="copy &quot;$(InputPath)&quot; .\app_settings\message_template.msg
The source and destination paths on line 158 may also require wrapping in quotes. In which case:
CommandLine="copy $(TargetDir)\$(TargetFileName) $(ProjectDir)
should become:
CommandLine="copy &quot;$(TargetDir)\$(TargetFileName)&quot; &quot;$(ProjectDir)&quot;
 
== Can not find library ll*.lib ==
If you get a compile error for missing libraries with names of the projects (lscript_compile.lib, llaudio.lib, llcharacter.lib, etc.) go to newview > Properties > Linker > Input and remove these from the list of input libraries (they will be linked through the dependencies and should not be in the list).
 
 
== Cannot open include file: 'windows.h' ==
If you run into this problem:
..\..\..\boost/regex/v4/fileiter.hpp(44) : fatal error C1083: Cannot open include file: 'windows.h': No such file or directory
Fix it with this: (thanks Fairlight!)
set INCLUDE=C:\Program Files\Microsoft Platform SDK for Windows Server 2003 R2\Include;%INCLUDE%
set LIB=C:\Program Files\Microsoft Platform SDK for Windows Server 2003 R2\Lib;%LIB%

 
== Unresolved external symbol "int __cdecl lscript_compile" (VS2005) ==
* ''llcompilequeue.obj : error LNK2019: unresolved external symbol "int __cdecl lscript_compile(char const *,char const *,char const *,int)" (?lscript_compile@@YAHPBD00H@Z) referenced in function "protected: void __thiscall LLFloaterCompileQueue::compile(char const *,class LLUUID const &)" (?compile@LLFloaterCompileQueue@@IAEXPBDABVLLUUID@@@Z)''
* ''llpreviewscript.obj : error LNK2001: unresolved external symbol "int __cdecl lscript_compile(char const *,char const *,char const *,int)" (?lscript_compile@@YAHPBD00H@Z)''

This is not entirely clear, but there seems to be a problem with VS2005 if projects are unloaded while being in the dependency tree. I have seen this error while I had win_crash_logger and win_updater unloaded from the project tree and the problem went away when I loaded them back and excluded them from the newview dependency first.

Also make sure that in newview, properties, linker, input, input libraries, no libraries named ll*.lib and lscript_compile.lib are listed there (remove them if you find them).
 
 

== Unresolved external symbol __invalid_parameter_noinfo (VS2005) ==
* ''llmozlib-vc80.lib(llembeddedbrowserwindow.obj) : error LNK2019: unresolved external symbol __invalid_parameter_noinfo referenced''

You are most likely trying a debug build under VS2005. For debug builds, see the compile instruction section on [[finding_leaks]]
 
 

== Cannot open include file: 'ares.h' ==
download src from http://daniel.haxx.se/projects/c-ares/

compile c-ares-1.4.0/vc/areslib

copy c-ares-1.4.0/vc/areslib/Release/areslib.lib to linden/libraries/i686-win32/lib_release and to lib_debug

copy c-ares-1.4.0/*.h to linden/libraries/i686-win32/include/ares
 
 

== Other (older) notes ==
* Mozilla is not compatible with visual studio 2005, so we have not migrated the codebase, so we do not know if it works.

* Added my errors at [[User:Adam_Zaius/MSVS2005 Errors]] [[User:Adam Zaius|Adam Zaius]] 09:40, 8 January 2007 (PST)

* To minimize the number of warnings for now: in C/C++-Preprocessor add ';_CRT_SECURE_NO_DEPRECATE' to the Preprocessor Definitions, that will supress deprecation warnings --[[User:Artm Udal|Artm Udal]] 12:42, 8 January 2007 (PST)

 

= Mac OS X =

Getting:

*/linden/indra/newview/../llwindow/llglheaders.h:377:31: error: GL/glh_extensions.h: No such file or directory
** This means you didn't [[Compiling the viewer (Mac OS X)#Viewer Source, Libraries, and Artwork|merge the libraries]] right.

 

= Linux =

==== Packaging errors ====

The final packaging step may fail with errors about the manifest if you are not using the slviewer-linux-libs bundle; in this case, if you still wish to end up with an end-user viewer package incorporating your own libraries, you can edit the manifest file found at indra/newview/viewer_manifest.py

==== Various Compilation problems ====

* "Unable to initialize communications"
** If the viewer just displays the error message " Unable to initialize communications" and exits, it can't find message_template.msg. You did remember to copy it over, right?

* Blino's SL build/linking patches for '''gcc4''': http://svn.mandriva.com/cgi-bin/viewvc.cgi/packages/cooker/secondlife/current/
* objcopy: 'newview/linux_tools/exposed-symbols.txt': No such file
** Tofu says... 'This is an omission from our manifest which I'll fix. Meanwhile it's a safe fix to create an empty file with that name.'

* Something like: /usr/bin/ld: cannot find -lz
** Nadia says: Install the zlib development headers. (Ubuntu package zlib1g-dev, Red Hat zlib-devel.)

* Something like: indra.y.cpp:17: error: previous declaration of `int yyparse()'
** Tofu says... 'This appears to be a problem with some versions of flex/bison. A resident reports success when comment out the #ifdef __cplusplus lines in lscript/lscript_compile/indra.y'
** Nadia says: install the zlib development headers first and try recompiling. Commenting out those lines results in a error indra.l:666: undefined
* Linking failures ("script not found") due to spaces in the LINKFLAGS variable?
** I saw a [http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4665538 report], and modified the SConstruct file to drop the trailing arguments (and spaces) in LINKFLAGS.

* Building [https://lists.secondlife.com/pipermail/sldev/2007-January/000091.html 20070112a] using ''BUILD=releasefordownload'' I get many ''[: 89: ==: unexpected operator'' errors; ''cp: target `SecondLife_i686_1_13_1_7/app_settings/*’ is not a directory'' error, and same thing for character, fonts, help, skins, res-sdl; ''[: 111: ==: unexpected operator, [: 120: SecondLife_i686_1_13_1_7.tar.bz2: unexpected operator''. I can succesfully run the client from the source tree.
** i think this has been fixed --[[User:Signore Iredell|Signore Iredell]] 06:09, 9 June 2007 (PDT)

* scons: *** While building `['.../linden/indra/i686-linux-client-release/lscript/lscript_compile/indra.l.cpp']': Don't know how to build a file with suffix `.l'.
** You probably don't have all the dependencies installed (I had the same problem). Check that you have flex and bison. --[[User:Random73 Janus|Random73 Janus]] 07:43, 16 May 2007 (PDT)

* Something like: linden/indra/i686-linux-client-release/llrender/llimagegl.cpp:122: error: `glActiveTextureARB' was not declared in this scope
** Tofu says... 'You'll need to install OpenGL headers if you don't already have them: gl.h, glext.h, glu.h (The ones from 'mesa' should work)
** two residents report good luck on Gentoo after doing 'eselect opengl set xorg-x11' (but note!! You must know what you're doing; this may change your default system OpenGL drivers, and you will probably want to change them back again after the compile, e.g. 'eselect opengl set nvidia')'

*Building Shared Library ELFIO [[Compiling_the_viewer_%28Linux%29]] on AMD64 ubuntu 6.10
g++-3.4 -shared *.o -o libelfio.so
/usr/bin/ld: ELFIDynamic.o: relocation R_X86_64_32 against `a local symbol' can
not be used when making a shared object; recompile with -fPIC
ELFIDynamic.o: could not read symbols: Bad value'''

* Building Client on Ubuntu 7.04 AMD64
/usr/bin/ld: skipping incompatible /home/dereck/Desktop/SLdev/linden/libraries/i686-linux/lib_release_client/libopenjpeg.a when searching for -lopenjpeg
/usr/bin/ld: cannot find -lopenjpeg
collect2: ld returned 1 exit status
** I went to the OpenJPEG website, downloaded the source, compiled for my system, installed it. The VWR compile was happy after that. Although it's not done yet and I'm still fixing another error, that I assume is unrelated.

==== scons got wild ====

* AttributeError: SConsEnvironment instance has no attribute 'CFile'
: This probably means you have no bison, flex, or equivalent tools installed on the standard locations on your system.
:* When your system has no bison installed, the above message will be supplemented as:
env.CFile(target=build_dir+'/lscript/lscript_compile/indra.y.c', source='lscript/lscript_compile/indra.y')
:* When your system has no flex installed, the above message will be supplemented as:
env.CFile(target=build_dir+'/lscript/lscript_compile/indra.l.cpp', source='lscript/lscript_compile/indra.l')
: Installing the appropriate package should solve this issue.

Compiling the viewer (MSVS2003)

2007-12-21T14:10:22Z

Nicholaz Beresford: glh includes/windlight assert

{{CompileNav}}

The following instructions are for compiling the Second Life viewer on Windows for Visual Studio .Net 2003. If you are using more recent versions of Visual Studio, see [[Compiling the viewer (MSVS2005)]]. For other platforms including MacOS and Linux, see [[Compiling the viewer]].

If you get lost, or these instructions are incomplete, see [[communication tools]] for a list of ways to get in touch with people that can help.
 
 
== Development Environment ==
The following dev environment is what LL uses for Windows development. There is no reason that the Second Life viewer can not be built using other environments, but it will take some extra work.

(Instructions for building the viewer using Microsoft's Visual Studio .NET 2005 Express can be found [[Compiling the viewer (MSVS2005)|on another page]]. At the time of writing, Express was freely available.)
 
=== Visual Studio .NET 2003 Professional ===
* Download and install [http://www.microsoft.com/downloads/details.aspx?familyid=0BAF2B35-C656-4969-ACE8-E4C0C0716ADB&displaylang=en Microsoft Platform SDK]
* Download and install a DirectX 9.0 SDK released on or after Summer of 2003 [http://download.microsoft.com/download/5/1/f/51ff8357-0af3-418b-9d0b-e9a5cdc39759/dxsdk_dec2006.EXE DirectX 9.0 SDK (December 2006)] [http://www.microsoft.com/downloads/details.aspx?FamilyID=9216652f-51e0-402e-b7b5-feb68d00f298&displaylang=en DirectX 9.0 SDK Update (Summer 2003)]
** If you have previously installed an older version of the DirectX 9.0 SDK, remove it first (from Control Panel -> Add or Remove Programs) before installing this version. Installing the new SDK "on top" of an older version may cause problems.
** Upon installing, it is sufficient to install the '''include''' and '''libraries''' part. Other DX development tools are not necessary.
* Set up the project globals:
** Start Visual C++
** Go to Tools/Options/Projects/VC++ Directories
** Make sure that the '''includes''' and '''libraries''' paths are there (or otherwise add them) in the following order: 1) Platform SDK paths, 2) DirectX SDK paths, 3) Visual C++ paths
** If you are adding DirectX SDK paths, be aware that later versions of the DirectX SDK have subfolders inside the lib directory. With those make sure you select '''lib/x86''', not just '''lib'''.

=== Other Development Tools ===
You will also need some open source development tools.
* [http://www.cygwin.com/ 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. The project files use several hardcoded references that expect Cygwin to be installed at '''C:\cygwin''', if it's not you'll need to edit those references.
* [http://www.activestate.com/Products/ActivePython/?mp=1 ActivePython 2.3x or later] - Latest Version is 2.5.1.1
** You should install this if compiling 1.18 or later viewers, or else hack the prebuild .bat files as in [http://jira.secondlife.com/browse/VWR-1267 VWR-1267].
* ActivePerl was recommended for previous versions on this Wiki, but it currently appears, that it is not strictly necessary unless you are planning to build your own version of all libraries (which most likely you don't want to do). So for a start it may be safe to skip it.
*: [http://www.activestate.com/Products/ActivePerl/?mp=1 ActivePerl]
 
 
 

== Source Code ==
The easiest way to get this working is to get '''source''', '''artwork''' and '''libraries''' for the same version from the [[source downloads]] page and unpack them all into the same directory/folder, which ideally would be a folder in (or near) the root directory with a short name like ''sl_1_16_0_5''.
'''Note:''' Avoid folder names with spaces in them (this means avoid putting the project into your ''My Documents'' folder).
 
 
 
== Open Source Libraries ==

Some libraries can be distributed with the SL source and there is a library package available with the source. As mentioned above (about the source), you can simply extract the '''library''' archive and copy the files to your code directory, maintaining the same directory structure.

If instead you are interested in compiling these libraries from their source (instead of using the above zipfile of precompiled libraries provided by Linden Lab), see [[Compiling the viewer libraries (MSVS 2003)]]
 
 
== Other Libraries ==

Linden Lab included all the libraries/includes they can ship with their source, but we can not distribute the source to the following , and you will need to follow the instructions to acquire below.

However, it probably is 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 (like ''XCOPY olibs sl_1_16_0_5 /S''). The reason is, that these steps are cumbersome and will have to be repeated for each new release (at least if you keep the source for each release in it's own folder).

If you do not want to do this, of course you can just copy the files directly into the linden source paths.

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

==== Fmod ====
* Download & extract [http://www.fmod.org/index.php/download fmod 3.75 api for win32].
* Copy "fmodapi375win\api\inc\fmod.h" to "linden\libraries\include"
* Copy "fmodapi375win\api\inc\fmod_errors.h" to "linden\libraries\include"
* Copy "fmodapi375win\api\lib\fmodvc.lib" to "linden\libraries\i686-win32\lib_release"
* Copy "fmodapi375win\api\lib\fmodvc.lib" to "linden\libraries\i686-win32\lib_debug"
* Copy "fmodapi375win\api\fmod.dll" to "linden\indra\newview"

==== gl ====
* Download [http://oss.sgi.com/projects/ogl-sample/sdk.html glext.h, glxext.h, and wglext.h]
* Copy them to "linden\libraries\i686-win32\include\GL"

==== ares (viewer 1.18.4 ... for later releases first check if the ares.h and .lib files are already in the Linden library package) ====
* download c-ares 1.4 from [http://daniel.haxx.se/projects/c-ares/ here] and unpack it somewhere
* open vc.dsw from the c-ares/vc folder
* remove the adig and ahost projects from the vc workspace
* add ares_getnameinfo.c to the areslib project
* for areslib right-click, properties, Code Generation and set Runtime Library to /MT (release) and /MTd (debug)
* compile debug and release
* copy all c-ares\*.h files to linden\libraries\include\ares\*.h
* copy vc\areslib\Debug\*lib to linden\libraries\i686-win32\lib_debug
* copy vc\areslib\Release\*lib to linden\libraries\i686-win32\lib_release

==== openjpeg (viewer 1.18.4 ... for later releases first check if the openjpeg.lib files are already in the Linden library package) ====
* download the latest OpenJPEG from [http://www.openjpeg.org/ here]
* open the libopenjpeg.dsw, let it convert and compile it (you'll need the files from the dllopenjpeg sub-project)
* copy debug\openjpeg.lib to linden\libraries\i686-win32\lib_debug
* copy release\openjpeg.lib to linden\libraries\i686-win32\lib_release
* copy release\openjpeg.dll to linden\indra\newview

==== glh (Windlight only) ====
There are currently (as of Windlight 1.18.6.75762) glh-include files missing from the source distribution. You should be able to grab them [http://www.blueflash.cc/users/nicholaz/~libs/ here] or download a patch from the [https://jira.secondlife.com/browse/VWR-3415 JIRA]. The files need to go into linden/libraries/include/glh/*.h

==== Quicktime (Optional) ====
* '''Note:''' Quicktime download can be skipped '''if you can live with a build that does not play in-world movies''' (some minor modifications to the project are necessary then, see "QuickTime removal" on the build instructions for [[Compiling the viewer (MSVS2005)|Visual Studio 2005]]).
* Download & install the [http://developer.apple.com/quicktime/download/ Quicktime SDK for Windows]
* Copy "QuicktimeSDK\Libraries\QTMLClient.lib" to "linden\libraries\i686-win32\lib_release".
* Copy "QuicktimeSDK\Libraries\QTMLClient.lib" to "linden\libraries\i686-win32\lib_debug".
* Copy the contents of "QuicktimeSDK\CIncludes" into "linden\libraries\i686-win32\include\quicktime".
 
 
== Building ==
* Open the '''indra\indra_complete\indra_complete.sln''' solution in Visual Studio (Note: If you plan to work with multiple versions over time, you will find it useful to rename '''indra_complete.sln''' to something which contains the version number, e.g. '''indra_1_17_0_11.sln''' before opening)
* Set newview to be the startup project.
* Build either '''ReleaseNoOpt''' (for debugging) or '''ReleaseForDownload''' (for running/debugging production code).
* Note that the ReleaseForDownload build also contains debug information and can be run in the debugger.
* newview_noopt.exe will be built in \indra\newview\ReleaseNoOpt, or SecondLife.exe will be built in \indra\newview\ReleaseForDownload
* To run it outside VS, create a shortcut to SecondLife.exe, and change the start location to linden\indra\newview\ (all the .dll will be found there.)
* Alternately copy the exe (possibly rename it) to your "c:\program files\second life" folder.
* There were additional steps required in version 1.15 which seem to be fixed now. If you are trying to build 1.15 see an [https://wiki.secondlife.com/w/index.php?title=Compiling_the_viewer_%28MSVS2003%29&oldid=23026 older version of this page].
 
 

== Errors while building? ==
See [[Common compilation problems]] if you run into errors while building.
 
 
 
== Configurations/Debugging Info ==
* You will usually compile/debug the '''ReleaseNoOpt''' or ReleaseForDownload configuration ('''Debug''' should also work but should not really be necessary).
* '''ReleaseNoOpt''' compiles faster and has more debugging information, but this comes at a runtime penalty of about 50% of your FPS in busy areas, compared to ReleaseForDownload build.
* '''ReleaseForDownload''' runs fine in the debugger, but times you may miss debugger access to some local variables or the debugger may even show wrong values for objects and members, because it is confused by the optimizations.
* '''ReleaseNoOpt''' comes with a seperate debugging console window opens and stays open for the duration of your session.
* You can see the last few lines from the debugger console also by pressing Shift+Ctrl+4 in the viewer (all builds).
* The debug log (usually in application data) can also be redirected to a more file if you add "-log secondlife.log" to the command line (Newview, Properties, Debugging, Command line arguments).
* If you want to build a '''Debug''' configuration, see the specific section with compile instructions on [[Finding_leaks]]
 
 
== Problems Running? ==
* Viewer Error: '''Second Life is unable to access a file that it needs.''': Did you neglect to download the Artworks archive from the [[source downloads]] page? It is in the Viewer column, below the OS-specific Viewer archives.
* '''Can't connect''': In the debug builds there is a selection box on the login screen to select the server to connect to. '''Agni''' is the production grid, '''aditi''' is the beta grid. (There seems to be a bug in this part of the code, you may have to make your selection, close the viewer and repoen it, before you can connect to the selected grid).
* '''Inventory errors''': If you're getting errors while trying to load your inventory, try [[Help:Stuck logging in|clearing your cache and deleting other temporary files]].
* If you want to connect to the beta grid, add '''--aditi''' to the command line (Newview, Properties, Debugging, Command line argument).
* '''Missing smime3 DLL''': Those are parts of the integrated web browser. Copy 'smime3.dll', 'nss3.dll', 'softokn3.dll', and 'ssl3.dll' files from your official client's main folder to "linden\indra\newview".
* '''assert with star_brightness''' and/or '''Black Screen''' under '''Windlight''': Current distributions of the Windlight source are missing files from the app_settings/windlight folder. Download the Linden Windlight viewer, install it and copy the files (and subfolders) into your development environment (linden/indra/newview/app_settings/windlight)
 
 

== Submit Patches ==
This is probably far down the road, but if you make changes to the source and want to submit them, see the page about [[Submitting patches|submitting patches]].

Bug triage/2007-12-10

2007-12-10T22:08:31Z

Nicholaz Beresford:

{{Bug triage}}

Next meeting: 2007-12-10 at Hippotropolis at noon SLT. See [[Bug triage]] for details.

== Fast Track Import ==

(Move bugs here that have solid repros, or valid patches that you have reviewed)

== Hot by Vote ==
* {{jira|VWR-3561}} - Votes: 13 - Blue Dialogs can overload the viewer. - {{User|WarKirby Magojiro}}
* {{jira|VWR-3559}} - Votes: 11 - Limit llMapDestination to one call per event. - {{User|WarKirby Magojiro}}
* {{jira|SVC-1038}} - Votes: 11 - Limit llMapDestination to one call per event. - {{User|WarKirby Magojiro}}
* {{jira|SVC-1041}} - Votes: 18 - (havok4) VEHICLE_FLAG_MOUSELOOK_STEER/VEHICLE_FLAG_MOUSELOOK_BANK flags broken - {{User|Drew Dwi}}
* {{jira|VWR-3634}} - Votes: 18 - Avatar shadows are too dark (pictures included) - {{User|hulk ah}}
* {{jira|VWR-1286}} - Votes: 12 - alt-zooming on hollow face mishandled - {{User|Lex Neva}}
* {{jira|SVC-459}} - Votes: 13 - De-Link on Border Crossing - {{User|Smith Fizz}}

== Patches ==
* {{jira|VWR-3616}} - Votes: 3 - The New (given) Landmark floater misses the ""Discard"" button in v1.18.5 viewers. - {{User|Henri Beauchamp}}
* {{jira|VWR-3619}} - Votes: 0 - An incorrect comment in llfont.h - {{User|Alissa Sabre}}
* {{jira|VWR-3748}} - Votes: 0 - Builds fail on 1.18.6 RC if not using MOZLIB due to missing #if LL_LIBXUL_ENABLED in 3 places in indra/newview/llpanellogin.cpp - {{User|Scrippy Scofield}}
* {{jira|VWR-3655}} - Votes: 0 - Extra qualifier in LLWaterParamSet definition, making gcc choke (considered an error). - {{User|Henri Beauchamp}}
* {{jira|SVC-1047}} - Votes: 0 - Quaternion multiplication works in reverse order in LSL as in maths - {{User|catherine pfeffer}}
* {{jira|VWR-3777}} - Votes: 1 - memory leak: LLVoiceVisualizer instances are immortal - {{User|Mm Alder}}
*: ([[User:Nicholaz Beresford|Nicholaz]] 14:08, 10 December 2007 (PST) : has my vote, I verified it (with and without patch) in the debugger )

== Misc Pool ==
* {{jira|VWR-3433}} - Votes: 0 - Camera ""underwater mode"" activated on water level of region agent is in - {{User|Daedalus Young}}
* {{jira|VWR-2841}} - Votes: 3 - Packet loss - {{User|DBDigital Epsilon}}
* {{jira|SVC-1006}} - Votes: 0 - Unable to revoke permissions - {{User|Monica Balut}}
* {{jira|WEB-405}} - Votes: 0 - SLMAP API - disableVoiceInfo not working - {{User|Gypsy Paz}}
* {{jira|VWR-3507}} - Votes: 0 - Windlight: Lifespan of ""growing"" particles less than the PSYS_PART_MAX_AGE requested - {{User|Leendert Meriman}}
* {{jira|VWR-3509}} - Votes: 0 - RenderUI Takes up 75% of rendering time. - {{User|Radian Artaud}}
* {{jira|VWR-2498}} - Votes: 2 - llTargetOmega() does not rotate object on some drivers - {{User|Dzonatas Sol}}
* {{jira|SVC-1027}} - Votes: 0 - llSetParcelMusicURL will unload video playing. - {{User|anthony reisman}}
* {{jira|SVC-1019}} - Votes: 0 - Objects moved off parcel and autoreturned, ownership of many other objects changed - {{User|Maximillian Desoto}}
* {{jira|MISC-831}} - Votes: 0 - Mac OS X RC & WL Disk Images have no background - {{User|Daedalus Young}}
* {{jira|VWR-3416}} - Votes: 1 - Dramatic performance drop when avatar is in view - {{User|Umbra Lunardi}}
* {{jira|SVC-961}} - Votes: 3 - can easily walk up walls in havok 4 beta - {{User|Lex Neva}}
* {{jira|WEB-406}} - Votes: 0 - SLMAP API - Map images very outdated - {{User|Gypsy Paz}}
* {{jira|WEB-309}} - Votes: 1 - Transaction History .xls is unable to be opened by iWorks 08 - {{User|Drew Dwi}}
* {{jira|VWR-3627}} - Votes: 0 - Graphics Card Crashes on logout. - {{User|Kilmarac Drago}}
* {{jira|VWR-3521}} - Votes: 0 - Oddly shapes Horizons in Windlight above about 600 meters and very well defined sim corners above just 50 meters - {{User|sean marsi}}
* {{jira|VWR-3514}} - Votes: 0 - Windlight client 1.18.5 (74642) graphics rendering problem on medium quality settings with nVidia chipset at high altitudes - {{User|Dark Troglodite}}
* {{jira|VWR-3523}} - Votes: 0 - The Void water is rendered at too high of a level for me - {{User|sean marsi}}
* {{jira|VWR-3522}} - Votes: 0 - Object-Object Occlusion Possible Memory Leak - Windlight 1.18.5 (74642) - {{User|fa nyak}}
* {{jira|VWR-3629}} - Votes: 0 - Extreme lag and crash on logout - {{User|Barrett Slade}}
* {{jira|VWR-3373}} - Votes: 2 - Daylight settings in Estate tools missing - {{User|Ralf Haifisch}}
* {{jira|VWR-3118}} - Votes: 2 - Windlight: Bump Mapping and Shiny display problems - {{User|Braya White}}
* {{jira|SVC-1030}} - Votes: 0 - Particle objects are not working correctly on Sim Galactica and working correctly on other sims - {{User|cammi hudson}}
* {{jira|VWR-3630}} - Votes: 0 - Avatar disspears when camera zooms out - {{User|Nadja Travanti}}
* {{jira|VWR-3362}} - Votes: 4 - WindLight: avatar imposters not being rendered; avatars completely disappear - {{User|Shirley Marquez}}
* {{jira|SVC-976}} - Votes: 3 - Repeated Crashes - {{User|MyoKa Murakami}}
* {{jira|SVC-872}} - Votes: 0 - Havok4 Beta: Eye texture not loaded. - {{User|Kitto Flora}}
* {{jira|VWR-3633}} - Votes: 0 - Avatar impostor of not-yet-rezzed avatar not appearing - {{User|Shirley Marquez}}
* {{jira|VWR-3527}} - Votes: 1 - Windlight 1.18.5.74642 reports insufficient hardware on first start with more than adequate hardware - {{User|Hiri Nurmi}}
* {{jira|VWR-3134}} - Votes: 5 - Windlight viewer : new water not working - {{User|Atsuko Otsuka}}
* {{jira|VWR-3105}} - Votes: 2 - Graphical tearing has gotten worse - {{User|Feynt Mistral}}
* {{jira|VWR-3536}} - Votes: 0 - Highlights on objects dissappear when moving while using land info tools - {{User|Ryder Dryke}}
* {{jira|VWR-3532}} - Votes: 0 - New water shaders + reflections no longer work with ""Atmospheric Shaders"" unchecked - {{User|Kitty Barnett}}
* {{jira|VWR-3636}} - Votes: 0 - UPDATE- prim(s) Data corruption issue - {{User|Rascal Ratelle}}

== Pre-meeting activity ==

Some issues will be resolved in the course of building this agenda. Rather than deleting them from the proposed agenda, move the issue and associated discussion into the appropriate section below.

=== Imported ===

=== Resolved ===

== Transcript ==
Transcript is/will be at [[{{PAGENAME}}/Transcript]]

== Creating An Agenda ==
{{Bug List Instructions}}

Compiling the viewer (MSVS2003)

2007-11-24T18:55:53Z

Nicholaz Beresford: ares/openjpeg for releases after 1.18.4

{{CompileNav}}

The following instructions are for compiling the Second Life viewer on Windows for Visual Studio .Net 2003. If you are using more recent versions of Visual Studio, see [[Compiling the viewer (MSVS2005)]]. For other platforms including MacOS and Linux, see [[Compiling the viewer]].

If you get lost, or these instructions are incomplete, see [[communication tools]] for a list of ways to get in touch with people that can help.
 
 
== Development Environment ==
The following dev environment is what LL uses for Windows development. There is no reason that the Second Life viewer can not be built using other environments, but it will take some extra work.

(Instructions for building the viewer using Microsoft's Visual Studio .NET 2005 Express can be found [[Compiling the viewer (MSVS2005)|on another page]]. At the time of writing, Express was freely available.)
 
=== Visual Studio .NET 2003 Professional ===
* Download and install [http://www.microsoft.com/downloads/details.aspx?familyid=0BAF2B35-C656-4969-ACE8-E4C0C0716ADB&displaylang=en Microsoft Platform SDK]
* Download and install a DirectX 9.0 SDK released on or after Summer of 2003 [http://download.microsoft.com/download/5/1/f/51ff8357-0af3-418b-9d0b-e9a5cdc39759/dxsdk_dec2006.EXE DirectX 9.0 SDK (December 2006)] [http://www.microsoft.com/downloads/details.aspx?FamilyID=9216652f-51e0-402e-b7b5-feb68d00f298&displaylang=en DirectX 9.0 SDK Update (Summer 2003)]
** If you have previously installed an older version of the DirectX 9.0 SDK, remove it first (from Control Panel -> Add or Remove Programs) before installing this version. Installing the new SDK "on top" of an older version may cause problems.
** Upon installing, it is sufficient to install the '''include''' and '''libraries''' part. Other DX development tools are not necessary.
* Set up the project globals:
** Start Visual C++
** Go to Tools/Options/Projects/VC++ Directories
** Make sure that the '''includes''' and '''libraries''' paths are there (or otherwise add them) in the following order: 1) Platform SDK paths, 2) DirectX SDK paths, 3) Visual C++ paths
** If you are adding DirectX SDK paths, be aware that later versions of the DirectX SDK have subfolders inside the lib directory. With those make sure you select '''lib/x86''', not just '''lib'''.

=== Other Development Tools ===
You will also need some open source development tools.
* [http://www.cygwin.com/ 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. The project files use several hardcoded references that expect Cygwin to be installed at '''C:\cygwin''', if it's not you'll need to edit those references.
* [http://www.activestate.com/Products/ActivePython/?mp=1 ActivePython 2.3x or later] - Latest Version is 2.5.1.1
** You should install this if compiling 1.18 or later viewers, or else hack the prebuild .bat files as in [http://jira.secondlife.com/browse/VWR-1267 VWR-1267].
* ActivePerl was recommended for previous versions on this Wiki, but it currently appears, that it is not strictly necessary unless you are planning to build your own version of all libraries (which most likely you don't want to do). So for a start it may be safe to skip it.
*: [http://www.activestate.com/Products/ActivePerl/?mp=1 ActivePerl]
 
 
 

== Source Code ==
The easiest way to get this working is to get '''source''', '''artwork''' and '''libraries''' for the same version from the [[source downloads]] page and unpack them all into the same directory/folder, which ideally would be a folder in (or near) the root directory with a short name like ''sl_1_16_0_5''.
'''Note:''' Avoid folder names with spaces in them (this means avoid putting the project into your ''My Documents'' folder).
 
 
 
== Open Source Libraries ==

Some libraries can be distributed with the SL source and there is a library package available with the source. As mentioned above (about the source), you can simply extract the '''library''' archive and copy the files to your code directory, maintaining the same directory structure.

If instead you are interested in compiling these libraries from their source (instead of using the above zipfile of precompiled libraries provided by Linden Lab), see [[Compiling the viewer libraries (MSVS 2003)]]
 
 
== Other Libraries ==

Linden Lab included all the libraries/includes they can ship with their source, but we can not distribute the source to the following , and you will need to follow the instructions to acquire below.

However, it probably is 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 (like ''XCOPY olibs sl_1_16_0_5 /S''). The reason is, that these steps are cumbersome and will have to be repeated for each new release (at least if you keep the source for each release in it's own folder).

If you do not want to do this, of course you can just copy the files directly into the linden source paths.

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

==== Fmod ====
* Download & extract [http://www.fmod.org/index.php/download fmod 3.75 api for win32].
* Copy "fmodapi375win\api\inc\fmod.h" to "linden\libraries\include"
* Copy "fmodapi375win\api\inc\fmod_errors.h" to "linden\libraries\include"
* Copy "fmodapi375win\api\lib\fmodvc.lib" to "linden\libraries\i686-win32\lib_release"
* Copy "fmodapi375win\api\lib\fmodvc.lib" to "linden\libraries\i686-win32\lib_debug"
* Copy "fmodapi375win\api\fmod.dll" to "linden\indra\newview"

==== gl ====
* Download [http://oss.sgi.com/projects/ogl-sample/sdk.html glext.h, glxext.h, and wglext.h]
* Copy them to "linden\libraries\i686-win32\include\GL"

==== ares (viewer 1.18.4 ... for later releases first check if the ares.h and .lib files are already in the Linden library package) ====
* download c-ares 1.4 from [http://daniel.haxx.se/projects/c-ares/ here] and unpack it somewhere
* open vc.dsw from the c-ares/vc folder
* remove the adig and ahost projects from the vc workspace
* add ares_getnameinfo.c to the areslib project
* for areslib right-click, properties, Code Generation and set Runtime Library to /MT (release) and /MTd (debug)
* compile debug and release
* copy all c-ares\*.h files to linden\libraries\include\ares\*.h
* copy vc\areslib\Debug\*lib to linden\libraries\i686-win32\lib_debug
* copy vc\areslib\Release\*lib to linden\libraries\i686-win32\lib_release

==== openjpeg (viewer 1.18.4 ... for later releases first check if the openjpeg.lib files are already in the Linden library package) ====
* download the latest OpenJPEG from [http://www.openjpeg.org/ here]
* open the libopenjpeg.dsw, let it convert and compile it (you'll need the files from the dllopenjpeg sub-project)
* copy debug\openjpeg.lib to linden\libraries\i686-win32\lib_debug
* copy release\openjpeg.lib to linden\libraries\i686-win32\lib_release
* copy release\openjpeg.dll to linden\indra\newview

==== Quicktime (Optional) ====
* '''Note:''' Quicktime download can be skipped '''if you can live with a build that does not play in-world movies''' (some minor modifications to the project are necessary then, see "QuickTime removal" on the build instructions for [[Compiling the viewer (MSVS2005)|Visual Studio 2005]]).
* Download & install the [http://developer.apple.com/quicktime/download/ Quicktime SDK for Windows]
* Copy "QuicktimeSDK\Libraries\QTMLClient.lib" to "linden\libraries\i686-win32\lib_release".
* Copy "QuicktimeSDK\Libraries\QTMLClient.lib" to "linden\libraries\i686-win32\lib_debug".
* Copy the contents of "QuicktimeSDK\CIncludes" into "linden\libraries\i686-win32\include\quicktime".
 
 
== Building ==
* Open the '''indra\indra_complete\indra_complete.sln''' solution in Visual Studio (Note: If you plan to work with multiple versions over time, you will find it useful to rename '''indra_complete.sln''' to something which contains the version number, e.g. '''indra_1_17_0_11.sln''' before opening)
* Set newview to be the startup project.
* Build either '''ReleaseNoOpt''' (for debugging) or '''ReleaseForDownload''' (for running/debugging production code).
* Note that the ReleaseForDownload build also contains debug information and can be run in the debugger.
* newview_noopt.exe will be built in \indra\newview\ReleaseNoOpt, or SecondLife.exe will be built in \indra\newview\ReleaseForDownload
* To run it outside VS, create a shortcut to SecondLife.exe, and change the start location to linden\indra\newview\ (all the .dll will be found there.)
* Alternately copy the exe (possibly rename it) to your "c:\program files\second life" folder.
* There were additional steps required in version 1.15 which seem to be fixed now. If you are trying to build 1.15 see an [https://wiki.secondlife.com/w/index.php?title=Compiling_the_viewer_%28MSVS2003%29&oldid=23026 older version of this page].
 
 

== Errors while building? ==
See [[Common compilation problems]] if you run into errors while building.
 
 
 
== Configurations/Debugging Info ==
* You will usually compile/debug the '''ReleaseNoOpt''' or ReleaseForDownload configuration ('''Debug''' should also work but should not really be necessary).
* '''ReleaseNoOpt''' compiles faster and has more debugging information, but this comes at a runtime penalty of about 50% of your FPS in busy areas, compared to ReleaseForDownload build.
* '''ReleaseForDownload''' runs fine in the debugger, but times you may miss debugger access to some local variables or the debugger may even show wrong values for objects and members, because it is confused by the optimizations.
* '''ReleaseNoOpt''' comes with a seperate debugging console window opens and stays open for the duration of your session.
* You can see the last few lines from the debugger console also by pressing Shift+Ctrl+4 in the viewer (all builds).
* The debug log (usually in application data) can also be redirected to a more file if you add "-log secondlife.log" to the command line (Newview, Properties, Debugging, Command line arguments).
* If you want to build a '''Debug''' configuration, see the specific section with compile instructions on [[Finding_leaks]]
 
 
== Problems Running? ==
* Viewer Error: '''Second Life is unable to access a file that it needs.''': Did you neglect to download the Artworks archive from the [[source downloads]] page? It is in the Viewer column, below the OS-specific Viewer archives.
* '''Can't connect''': In the debug builds there is a selection box on the login screen to select the server to connect to. '''Agni''' is the production grid, '''aditi''' is the beta grid. (There seems to be a bug in this part of the code, you may have to make your selection, close the viewer and repoen it, before you can connect to the selected grid).
* '''Inventory errors''': If you're getting errors while trying to load your inventory, try [[Help:Stuck logging in|clearing your cache and deleting other temporary files]].
* If you want to connect to the beta grid, add '''--aditi''' to the command line (Newview, Properties, Debugging, Command line argument).
* '''Missing smime3 DLL''': Those are parts of the integrated web browser. Copy 'smime3.dll', 'nss3.dll', 'softokn3.dll', and 'ssl3.dll' files from your official client's main folder to "linden\indra\newview".
 
 

== Submit Patches ==
This is probably far down the road, but if you make changes to the source and want to submit them, see the page about [[Submitting patches|submitting patches]].

Compiling the viewer (MSVS2005)

2007-11-24T18:54:43Z

Nicholaz Beresford: ares/openjpeg for releases after 1.18.4

{{Languages}}
{{CompileNav}}

This page explains how you can compile the viewer on Microsoft Windows using Visual Studio 2005 or Visual C++ Express 2005. Note that Lindens are using VS2003 and the whole setup is a bit easier there, so if you have Visual Studio 2003 available, you should read [[Compiling the viewer (MSVS2003)|compiling with VS2003]] and you will get less trouble with it than with VS2005.

Currently, only 32 bit binary is tested. There seems to be several trials to produce 64 bit Windows .EXE of the viewer. If you did, please write your experience on this wiki (regardless it was successful or not!)

The following explanation is adjusted for Viewer releases 1.16.0.5 or later. See an [http://wiki.secondlife.com/w/index.php?title=Compiling_the_viewer_%28MSVS2005%29&oldid=22294 older version of this page] for the Viewer releases 1.15 or before.

= Preparing the Development Environment =

== Installing/Configuring VS2005 ==

You need to setup the compiler and Microsoft Development tools as follows:
* Visual Studio 2005 '''''-or-''''' [http://msdn.microsoft.com/vstudio/express/visualc/download/ Visual C++ 2005 Express](Free) (Also, although not strictly necessary, eventually pick up and install SP1 for VS2005.)
* [http://www.microsoft.com/downloads/details.aspx?familyid=0BAF2B35-C656-4969-ACE8-E4C0C0716ADB&displaylang=en Microsoft Platform SDK]
* A DirectX 9.0 SDK released on or after Summer of 2003 [http://download.microsoft.com/download/5/1/f/51ff8357-0af3-418b-9d0b-e9a5cdc39759/dxsdk_dec2006.EXE DirectX 9.0 SDK (December 2006)] [http://www.microsoft.com/downloads/details.aspx?FamilyID=9216652f-51e0-402e-b7b5-feb68d00f298&displaylang=en DirectX 9.0 SDK Update (Summer 2003)]
: '''Note''': If you have previously installed an older version of the DirectX 9.0 SDK, remove it first (from Control Panel -> Add or Remove Programs) before installing this version. Installing the new SDK "on top" of an older version may cause problems.
* Set up the project globals:
** Start Microsoft Visual Studio 2005
** Go to Tools > Options > Projects > VC++ Directories
** Make sure that the '''includes''' ([[:Image:MSVS2005 Global Project Options Include Files.JPG|'''screen shot''']]) and '''libraries''' ([[:Image:MSVS2005 Global Project Options Library Files.JPG|'''screen shot''']]) paths have the Platform SDK paths first, then the DirectX SDK paths, and then the Visual C++ paths. You may need to check "Show All Settings" at the bottom for VC++ Directories to show.
*** Default installation of both Platform SDK and DirectX SDK can be found in '''C:\Program Files\Microsoft Platform SDK for Windows Server 2003 R2''' and '''C:\Program Files\Microsoft DirectX SDK (December 2006)''' respectively.
** If the DirectX SDK paths aren't present, add them to both '''includes''' and '''libraries'''.
*: Note: The newest DirectX SDK ("December 2006") lib folder has two sub-folders, x64 and x86. Make sure your path goes to one of them (select '''lib/x86''', not just '''lib'''), or you will get a Link error.
 

== Getting other Development Tools ==
You will also need some open source development tools.
* [http://www.cygwin.com/ 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. The project files use several hardcoded references that expect Cygwin to be installed at '''C:\cygwin''', if it's not you'll need to edit those references.
* [http://www.activestate.com/Products/ActivePython/?mp=1 ActivePython 2.3x or later] - Latest Version is 2.5.1.1
** It is required but can be avoided if you are compiling 1.18 or later viewers. Either download and install or hack the prebuild.bat files as described in [http://jira.secondlife.com/browse/VWR-1267 VWR-1267].
* ActivePerl was recommended for previous versions on this Wiki, but it currently appears, that it is not strictly necessary unless you are planning to build your own version of all libraries (which most likely you don't want to do). So for a start it may be safe to skip it.
*: [http://www.activestate.com/Products/ActivePerl/?mp=1 ActivePerl]

 
 
 

= Downloading Source Code =

You can download the Viewer source codes on the [[source downloads]] page. You can also use a [[version control repository]].

At a minimum, grab the source package and the artwork package, but for a start, also grab the library archive. Many of the libraries can either be compiled from source or downloaded from other sites (see below), but this will take hours and thus it is easiest to also get the package with libraries compiled by the Lindens.

'''WARNING:'''
* If the directory path you keep the SL source in has a space in it, the batch file that copies message_template.msg will fail. So, if you unzip or checkout the source tree into, e.g., "C:\Projects\Dir with space in name\Etc\linden", it won't work!
* You should also avoid using non-ASCII (national) characters in the paths, although some localized versions of the tool puts some as a default...
* Unzip or checkout your source tree into a directory that has as short full pathname as possible, since long paths cause some unexpected trouble during the build.

In other words, the easiest way to get this working is to get ''source'', ''artwork'' and ''libraries'' from the [[source downloads]] page and unpack them all into the same directory/folder, which ideally would be a folder in (or near) the root directory with a short name like ''sl_1_16_0_5''.
 
 
 
 

= Installing Libraries =

SL Viewer depends on some third party libraries. Some of them are open source, some others are not.

== Open Source Libraries ==

You can download the pre-build open source libraries from LL. They are available on [[source downloads]] page. Unzip them into your SL viewer source code directory, maintaining the same directory structure.

'''Note: The VS2003 libraries provided in the [[source downloads]] do not fully work with VS2005 compiled binaries. They will compile with the viewer under VS2005, but the VS2003 libraries are not fully STL compliant. The differences of [http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vclang/html/vclrfnonstandardbehavior.asp non-standard behavior in MSVS] are the known cause.'''

Alternatively, it may be possible to get the source files for the libraries and build by yourself. See [[Compiling the viewer libraries (MSVS 2003)|the instruction for VS2003 users]] if you try it. Please note, however, it is not known that VS2005 can successfully compile the libraries. '''You have been warned.''' (If you can make it, please write the info on this wiki...)
 
 

== Proprietary Libraries ==

Lindens does not inlcude the following proprietary libraries. You will need to follow the instructions to acquire below and copy them to the source path.

However, it probably is 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 (like ''XCOPY OLIB SL_1_16_0_5 /S''). The reason is, that these steps are cumbersome and will have to be repeated for each new release (at least if you keep the source for each release in it's own folder). If you do not want to do this, of course you can just copy the files directly into the linden source paths.

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
 
=== Fmod ===
* Download & extract [http://www.fmod.org/index.php/download fmod 3.75 api for win32] (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\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"
 

=== OpenGL ===
* Download [http://oss.sgi.com/projects/ogl-sample/sdk.html glext.h, glxext.h, and wglext.h]
* Copy them to "linden\libraries\i686-win32\include\GL"
* You don't need any additional *.lib or *.dll for OpenGL.
 

=== ares (viewer 1.18.4 ... for later releases first check if the ares.h and .lib files are in the Linden library package) ===
* download c-ares 1.4 from [http://daniel.haxx.se/projects/c-ares/ here] and unpack it somewhere
* open vc.dsw from the c-ares/vc folder
* remove the adig and ahost projects from the vc workspace
* add ares_getnameinfo.c to the areslib project
* for areslib right-click, properties, Code Generation and set Runtime Library to /MT (release) and /MTd (debug)
* compile debug and release
* copy all c-ares\*.h files to linden\libraries\include\ares\*.h
* copy vc\areslib\Debug\*lib to linden\libraries\i686-win32\lib_debug
* copy vc\areslib\Release\*lib to linden\libraries\i686-win32\lib_release
 

=== openjpeg (viewer 1.18.4 ... for later releases first check if the openjpeg.lib files are in the Linden library package) ===
* download the latest OpenJPEG from [http://www.openjpeg.org/ here]
* open the libopenjpeg.dsw, let it convert and compile it (you'll need the files from the dllopenjpeg sub-project)
* copy debug\openjpeg.lib to linden\libraries\i686-win32\lib_debug
* copy release\openjpeg.lib to linden\libraries\i686-win32\lib_release
* copy release\openjpeg.dll to linden\indra\newview
 

=== Quicktime ''(optional)'' ===
'''Note:''' This download requires a registration at the Apple Quicktime website and take a bit of time. You can avoid using QuickTime if you want, see [[#QuickTime removal|below]] for details. Remember that your viewer '''can't play in-world movies''' if you do so.
* Download & install the [http://connect.apple.com/cgi-bin/WebObjects/MemberSite.woa/203/wa/getSoftware?fileID=20525&code=y&source=x&wosid=4h16WcyMtVfd2P1EffGafkoxFcr 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".
 
 
 

= Configuring for VS2005 =

Lindens use VS2003 to develop the viewer.

You either need to convert ''solution file'' and ''project files'' from VS2003 format to VS2005 format or obtain files compatible with VS2005. You may also need to modify source files to work around the incompatibility between VS2003 and VS2005.

'''Note''': linden\indra\indra_complete_vs8.sln is a solution file already included in the source archive and intended for the Visual Studio 2005, but it '''does not work''' (at least between 1.14.0 and 1.17.0.9 distribution). This may change in a future release, if Lindens include an updated versions of the '''_vc8''' files.

 
 
== Using pre-built solution/project files ==

Currently there is a ZIP file with solution/project files available on the [https://jira.secondlife.com/browse/VWR-1151 JIRA bug tracker issue VWR-1151].

If you are building 1.16 or later, the easiest way towards compiling SL on MS2005 will be to use the zip file mentioned above. The details is as follows:
* Download the appropriate ZIP archive from JIRA.
* Unpack it and copy it onto your linden source tree (allow to overwrite files that have '''_vc8''' in the name).
* Start Visual Studio 2005 (or VC++ Express).
* Use "File > Open > Project/Solution" to open the linden\indra\indra_complete\indra_complete'''_vc8'''.sln (Note: If you plan to work with multiple versions over time, you will find it useful to rename '''indra_complete_vc8.sln''' to something which contains the version number, e.g. '''indra_1_17_0_11_vc8.sln''' before opening.)
* Right click '''newview''' in the frame Solution Explorer and click "Set as StartUp Project".
* Proceed with applying the '''Workarounds''' below (skip '''Manual conversion''').

'''Note:''' The solution/project files depends on the viewer release version. If you are compiling some specific version of the viewer, and the {{JIRA|VWR-1151}} doesn't list the zip file for you version, you can try using the most close one. If, while compiling, you later encounter errors or problems regarding the projects, you may have to do the manual conversion instead.

 

== Manual conversion of the solution/projects ==

If you can not find a set of project files (see above), there are instructions available how to manually do it: [[Converting_project_files_for_MSVS2005]] (this step will take about 5-15 minutes, depending on how proficient you are using VS2005).

 
 
 

== Workarounds ==

There are more compatibility problems between VS2003 and VS2005. You need the following code edits.
 
=== test project/crash_logger/updater ===

For whatever reason, the '''test''' project doesn't work under VS2005. Workaround is to disable it as follows: Right click on the '''test''' and choose '''Unload Project'''.

If you do not plan to create a full download build, you can exclude the '''win_crash_logger''' and '''win_updater''' from newview's project dependencies and unload them also. But be careful with unloading these projects without removing them from the dependencies, because I have seen VS2005 act highly erratic while linking then project when I tried this.
 
=== QuickTime removal ===

If you don't want to get Apple QuickTime SDK, you can disable it as follows:
*linden\indra\llcommon\llpreprocessor.h - near line 58 (the line below '''#elif LL_WINDOWS''')
--50: #define LL_QUICKTIME_ENABLED 1
++50: #define LL_QUICKTIME_ENABLED '''''0'''''

* Pick '''ReleaseNoOpt''' in the Solution Configurations drop-down box beside the green arrow under the tool bar, and do the followings on the Solution Explorer frame:
*Click '''newview''' to select it alone.
**Choose Properties.
**Under Configuration Properties > Linker > Input, click '''Additional Dependencies''' on the right to show a button labeled "'''...'''" on it at the very right on the line, then click the '''...''' button.
**Scroll down the list to find '''qtmlclient.lib'''. Delete this single line.
**Click '''OK''' to close the "Additional Dependencies" dialog, then click OK again to close the "newview Property Pages" dialog box.
* Pick '''ReleaseForDownload''' in the Solution Configurations drop-down box. Click '''newview''' to select it alone and do the same thing again.
 
 
 
= Ready, Set, Build! =

== Building ==
* Build either '''ReleaseNoOpt''' (for debugging) or '''ReleaseForDownload''' (for production code).
* To do this, pick either in the Solution Configurations drop-down box beside the green arrow under the tool bar.
* Make sure '''newview''' is set as the active project (otherwise set from newview's right-click menu).
* Select Build-Menu > Build Solution or press F7.
* newview_noopt.exe will be built in linden\indra\newview\ReleaseNoOpt or SecondLife.exe will be linden\indra\newview\ReleaseForDownload.
 
== Common compile errors ==
* See [[common compilation problems]] if you run into other errors while building.
 
== Running ==
* You can run the viewer by '''Debug > Start Debugging''' or '''Debug > Start Without Debugging''' in Visual Studio.
* To run it outside VS, create a shortcut to SecondLife.exe, and change the start location to linden\indra\newview\ (All the .dll will be found there.)
* Alternately copy the exe (possibly rename it) to your "c:\program files\secondlife" folder.
 
== Debugging Info/Configurations ==
* Usually you will either use '''ReleaseNoOpt''' or the '''ReleaseForDownload''' configuration.
* '''ReleaseNoOpt''' (not optimized) compiles faster and has more debugging information, but this comes at a runtime penalty of about 50% of your FPS in busy areas, compared to ReleaseForDownload build.
* '''ReleaseForDownload''' also has debugging information and runs fine in the debugger (although at times you may miss access to some local variables).
* '''ReleaseNoOpt''' comes with a seperate debugging console window opens and stays open for the duration of your session, but you can access the same information also by pressing Shift+Ctrl+4 in the viewer (all builds).
* The debug console log can also be redirected to a file if you add "2>secondlife.log" to the command line (Newview, Properties, Debugging, Command line arguments).
* If you want to build a '''Debug''' configuration, see the specific section with compile instructions on [[finding leaks]]
 

== Problems Running? ==
* '''Inventory errors''': If you're getting errors while trying to load your inventory, try [[Help:Stuck logging in|clearing your cache and deleting other temporary files]].
* '''Missing smime3 DLL''': Those are parts of the integrated web browser. Copy 'smime3.dll', 'nss3.dll', 'softokn3.dll', and 'ssl3.dll' files from your official client's main folder to "linden\indra\newview".
* '''Can't connect''': In the debug builds there is a selection box on the login screen to select the server to connect to. '''Agni''' is the production grid, '''aditi''' is the beta grid. (There seems to be a bug in this part of the code, you may have to make your selection, close the viewer and repoen it, before you can connect to the selected grid).
 
 
= Submit Patches =
This is probably faaar down the road, but if you make changes to the source and want to submit them, see the page about [[submitting patches]].

Compiling the viewer (MSVS2005)

2007-11-13T17:50:43Z

Nicholaz Beresford:

{{Languages}}
{{CompileNav}}

This page explains how you can compile the viewer on Microsoft Windows using Visual Studio 2005 or Visual C++ Express 2005. Note that Lindens are using VS2003 and the whole setup is a bit easier there, so if you have Visual Studio 2003 available, you should read [[Compiling the viewer (MSVS2003)|compiling with VS2003]] and you will get less trouble with it than with VS2005.

Currently, only 32 bit binary is tested. There seems to be several trials to produce 64 bit Windows .EXE of the viewer. If you did, please write your experience on this wiki (regardless it was successful or not!)

The following explanation is adjusted for Viewer releases 1.16.0.5 or later. See an [http://wiki.secondlife.com/w/index.php?title=Compiling_the_viewer_%28MSVS2005%29&oldid=22294 older version of this page] for the Viewer releases 1.15 or before.

= Preparing the Development Environment =

== Installing/Configuring VS2005 ==

You need to setup the compiler and Microsoft Development tools as follows:
* Visual Studio 2005 '''''-or-''''' [http://msdn.microsoft.com/vstudio/express/visualc/download/ Visual C++ 2005 Express](Free) (Also, although not strictly necessary, eventually pick up and install SP1 for VS2005.)
* [http://www.microsoft.com/downloads/details.aspx?familyid=0BAF2B35-C656-4969-ACE8-E4C0C0716ADB&displaylang=en Microsoft Platform SDK]
* A DirectX 9.0 SDK released on or after Summer of 2003 [http://download.microsoft.com/download/5/1/f/51ff8357-0af3-418b-9d0b-e9a5cdc39759/dxsdk_dec2006.EXE DirectX 9.0 SDK (December 2006)] [http://www.microsoft.com/downloads/details.aspx?FamilyID=9216652f-51e0-402e-b7b5-feb68d00f298&displaylang=en DirectX 9.0 SDK Update (Summer 2003)]
: '''Note''': If you have previously installed an older version of the DirectX 9.0 SDK, remove it first (from Control Panel -> Add or Remove Programs) before installing this version. Installing the new SDK "on top" of an older version may cause problems.
* Set up the project globals:
** Start Microsoft Visual Studio 2005
** Go to Tools > Options > Projects > VC++ Directories
** Make sure that the '''includes''' ([[:Image:MSVS2005 Global Project Options Include Files.JPG|'''screen shot''']]) and '''libraries''' ([[:Image:MSVS2005 Global Project Options Library Files.JPG|'''screen shot''']]) paths have the Platform SDK paths first, then the DirectX SDK paths, and then the Visual C++ paths. You may need to check "Show All Settings" at the bottom for VC++ Directories to show.
*** Default installation of both Platform SDK and DirectX SDK can be found in '''C:\Program Files\Microsoft Platform SDK for Windows Server 2003 R2''' and '''C:\Program Files\Microsoft DirectX SDK (December 2006)''' respectively.
** If the DirectX SDK paths aren't present, add them to both '''includes''' and '''libraries'''.
*: Note: The newest DirectX SDK ("December 2006") lib folder has two sub-folders, x64 and x86. Make sure your path goes to one of them (select '''lib/x86''', not just '''lib'''), or you will get a Link error.
 

== Getting other Development Tools ==
You will also need some open source development tools.
* [http://www.cygwin.com/ 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. The project files use several hardcoded references that expect Cygwin to be installed at '''C:\cygwin''', if it's not you'll need to edit those references.
* [http://www.activestate.com/Products/ActivePython/?mp=1 ActivePython 2.3x or later] - Latest Version is 2.5.1.1
** It is required but can be avoided if you are compiling 1.18 or later viewers. Either download and install or hack the prebuild.bat files as described in [http://jira.secondlife.com/browse/VWR-1267 VWR-1267].
* ActivePerl was recommended for previous versions on this Wiki, but it currently appears, that it is not strictly necessary unless you are planning to build your own version of all libraries (which most likely you don't want to do). So for a start it may be safe to skip it.
*: [http://www.activestate.com/Products/ActivePerl/?mp=1 ActivePerl]

 
 
 

= Downloading Source Code =

You can download the Viewer source codes on the [[source downloads]] page. You can also use a [[version control repository]].

At a minimum, grab the source package and the artwork package, but for a start, also grab the library archive. Many of the libraries can either be compiled from source or downloaded from other sites (see below), but this will take hours and thus it is easiest to also get the package with libraries compiled by the Lindens.

'''WARNING:'''
* If the directory path you keep the SL source in has a space in it, the batch file that copies message_template.msg will fail. So, if you unzip or checkout the source tree into, e.g., "C:\Projects\Dir with space in name\Etc\linden", it won't work!
* You should also avoid using non-ASCII (national) characters in the paths, although some localized versions of the tool puts some as a default...
* Unzip or checkout your source tree into a directory that has as short full pathname as possible, since long paths cause some unexpected trouble during the build.

In other words, the easiest way to get this working is to get ''source'', ''artwork'' and ''libraries'' from the [[source downloads]] page and unpack them all into the same directory/folder, which ideally would be a folder in (or near) the root directory with a short name like ''sl_1_16_0_5''.
 
 
 
 

= Installing Libraries =

SL Viewer depends on some third party libraries. Some of them are open source, some others are not.

== Open Source Libraries ==

You can download the pre-build open source libraries from LL. They are available on [[source downloads]] page. Unzip them into your SL viewer source code directory, maintaining the same directory structure.

'''Note: The VS2003 libraries provided in the [[source downloads]] do not fully work with VS2005 compiled binaries. They will compile with the viewer under VS2005, but the VS2003 libraries are not fully STL compliant. The differences of [http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vclang/html/vclrfnonstandardbehavior.asp non-standard behavior in MSVS] are the known cause.'''

Alternatively, it may be possible to get the source files for the libraries and build by yourself. See [[Compiling the viewer libraries (MSVS 2003)|the instruction for VS2003 users]] if you try it. Please note, however, it is not known that VS2005 can successfully compile the libraries. '''You have been warned.''' (If you can make it, please write the info on this wiki...)
 
 

== Proprietary Libraries ==

Lindens does not inlcude the following proprietary libraries. You will need to follow the instructions to acquire below and copy them to the source path.

However, it probably is 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 (like ''XCOPY OLIB SL_1_16_0_5 /S''). The reason is, that these steps are cumbersome and will have to be repeated for each new release (at least if you keep the source for each release in it's own folder). If you do not want to do this, of course you can just copy the files directly into the linden source paths.

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
 
=== Fmod ===
* Download & extract [http://www.fmod.org/index.php/download fmod 3.75 api for win32] (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\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"
 

=== OpenGL ===
* Download [http://oss.sgi.com/projects/ogl-sample/sdk.html glext.h, glxext.h, and wglext.h]
* Copy them to "linden\libraries\i686-win32\include\GL"
* You don't need any additional *.lib or *.dll for OpenGL.
 

=== ares (viewer 1.18.4 and later) ===
* download c-ares 1.4 from [http://daniel.haxx.se/projects/c-ares/ here] and unpack it somewhere
* open vc.dsw from the c-ares/vc folder
* remove the adig and ahost projects from the vc workspace
* add ares_getnameinfo.c to the areslib project
* for areslib right-click, properties, Code Generation and set Runtime Library to /MT (release) and /MTd (debug)
* compile debug and release
* copy all c-ares\*.h files to linden\libraries\include\ares\*.h
* copy vc\areslib\Debug\*lib to linden\libraries\i686-win32\lib_debug
* copy vc\areslib\Release\*lib to linden\libraries\i686-win32\lib_release
 

=== openjpeg (viewer 1.18.4 and later) ===
* download the latest OpenJPEG from [http://www.openjpeg.org/ here]
* open the libopenjpeg.dsw, let it convert and compile it (you'll need the files from the dllopenjpeg sub-project)
* copy debug\openjpeg.lib to linden\libraries\i686-win32\lib_debug
* copy release\openjpeg.lib to linden\libraries\i686-win32\lib_release
* copy release\openjpeg.dll to linden\indra\newview
 

=== Quicktime ''(optional)'' ===
'''Note:''' This download requires a registration at the Apple Quicktime website and take a bit of time. You can avoid using QuickTime if you want, see [[#QuickTime removal|below]] for details. Remember that your viewer '''can't play in-world movies''' if you do so.
* Download & install the [http://connect.apple.com/cgi-bin/WebObjects/MemberSite.woa/203/wa/getSoftware?fileID=20525&code=y&source=x&wosid=4h16WcyMtVfd2P1EffGafkoxFcr 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".
 
 
 

= Configuring for VS2005 =

Lindens use VS2003 to develop the viewer.

You either need to convert ''solution file'' and ''project files'' from VS2003 format to VS2005 format or obtain files compatible with VS2005. You may also need to modify source files to work around the incompatibility between VS2003 and VS2005.

'''Note''': linden\indra\indra_complete_vs8.sln is a solution file already included in the source archive and intended for the Visual Studio 2005, but it '''does not work''' (at least between 1.14.0 and 1.17.0.9 distribution). This may change in a future release, if Lindens include an updated versions of the '''_vc8''' files.

 
 
== Using pre-built solution/project files ==

Currently there is a ZIP file with solution/project files available on the [https://jira.secondlife.com/browse/VWR-1151 JIRA bug tracker issue VWR-1151].

If you are building 1.16 or later, the easiest way towards compiling SL on MS2005 will be to use the zip file mentioned above. The details is as follows:
* Download the appropriate ZIP archive from JIRA.
* Unpack it and copy it onto your linden source tree (allow to overwrite files that have '''_vc8''' in the name).
* Start Visual Studio 2005 (or VC++ Express).
* Use "File > Open > Project/Solution" to open the linden\indra\indra_complete\indra_complete'''_vc8'''.sln (Note: If you plan to work with multiple versions over time, you will find it useful to rename '''indra_complete_vc8.sln''' to something which contains the version number, e.g. '''indra_1_17_0_11_vc8.sln''' before opening.)
* Right click '''newview''' in the frame Solution Explorer and click "Set as StartUp Project".
* Proceed with applying the '''Workarounds''' below (skip '''Manual conversion''').

'''Note:''' The solution/project files depends on the viewer release version. If you are compiling some specific version of the viewer, and the {{JIRA|VWR-1151}} doesn't list the zip file for you version, you can try using the most close one. If, while compiling, you later encounter errors or problems regarding the projects, you may have to do the manual conversion instead.

 

== Manual conversion of the solution/projects ==

If you can not find a set of project files (see above), there are instructions available how to manually do it: [[Converting_project_files_for_MSVS2005]] (this step will take about 5-15 minutes, depending on how proficient you are using VS2005).

 
 
 

== Workarounds ==

There are more compatibility problems between VS2003 and VS2005. You need the following code edits.
 
=== test project/crash_logger/updater ===

For whatever reason, the '''test''' project doesn't work under VS2005. Workaround is to disable it as follows: Right click on the '''test''' and choose '''Unload Project'''.

If you do not plan to create a full download build, you can exclude the '''win_crash_logger''' and '''win_updater''' from newview's project dependencies and unload them also. But be careful with unloading these projects without removing them from the dependencies, because I have seen VS2005 act highly erratic while linking then project when I tried this.
 
=== QuickTime removal ===

If you don't want to get Apple QuickTime SDK, you can disable it as follows:
*linden\indra\llcommon\llpreprocessor.h - near line 58 (the line below '''#elif LL_WINDOWS''')
--50: #define LL_QUICKTIME_ENABLED 1
++50: #define LL_QUICKTIME_ENABLED '''''0'''''

* Pick '''ReleaseNoOpt''' in the Solution Configurations drop-down box beside the green arrow under the tool bar, and do the followings on the Solution Explorer frame:
*Click '''newview''' to select it alone.
**Choose Properties.
**Under Configuration Properties > Linker > Input, click '''Additional Dependencies''' on the right to show a button labeled "'''...'''" on it at the very right on the line, then click the '''...''' button.
**Scroll down the list to find '''qtmlclient.lib'''. Delete this single line.
**Click '''OK''' to close the "Additional Dependencies" dialog, then click OK again to close the "newview Property Pages" dialog box.
* Pick '''ReleaseForDownload''' in the Solution Configurations drop-down box. Click '''newview''' to select it alone and do the same thing again.
 
 
 
= Ready, Set, Build! =

== Building ==
* Build either '''ReleaseNoOpt''' (for debugging) or '''ReleaseForDownload''' (for production code).
* To do this, pick either in the Solution Configurations drop-down box beside the green arrow under the tool bar.
* Make sure '''newview''' is set as the active project (otherwise set from newview's right-click menu).
* Select Build-Menu > Build Solution or press F7.
* newview_noopt.exe will be built in linden\indra\newview\ReleaseNoOpt or SecondLife.exe will be linden\indra\newview\ReleaseForDownload.
 
== Common compile errors ==
* See [[common compilation problems]] if you run into other errors while building.
 
== Running ==
* You can run the viewer by '''Debug > Start Debugging''' or '''Debug > Start Without Debugging''' in Visual Studio.
* To run it outside VS, create a shortcut to SecondLife.exe, and change the start location to linden\indra\newview\ (All the .dll will be found there.)
* Alternately copy the exe (possibly rename it) to your "c:\program files\secondlife" folder.
 
== Debugging Info/Configurations ==
* Usually you will either use '''ReleaseNoOpt''' or the '''ReleaseForDownload''' configuration.
* '''ReleaseNoOpt''' (not optimized) compiles faster and has more debugging information, but this comes at a runtime penalty of about 50% of your FPS in busy areas, compared to ReleaseForDownload build.
* '''ReleaseForDownload''' also has debugging information and runs fine in the debugger (although at times you may miss access to some local variables).
* '''ReleaseNoOpt''' comes with a seperate debugging console window opens and stays open for the duration of your session, but you can access the same information also by pressing Shift+Ctrl+4 in the viewer (all builds).
* The debug console log can also be redirected to a file if you add "2>secondlife.log" to the command line (Newview, Properties, Debugging, Command line arguments).
* If you want to build a '''Debug''' configuration, see the specific section with compile instructions on [[finding leaks]]
 

== Problems Running? ==
* '''Inventory errors''': If you're getting errors while trying to load your inventory, try [[Help:Stuck logging in|clearing your cache and deleting other temporary files]].
* '''Missing smime3 DLL''': Those are parts of the integrated web browser. Copy 'smime3.dll', 'nss3.dll', 'softokn3.dll', and 'ssl3.dll' files from your official client's main folder to "linden\indra\newview".
* '''Can't connect''': In the debug builds there is a selection box on the login screen to select the server to connect to. '''Agni''' is the production grid, '''aditi''' is the beta grid. (There seems to be a bug in this part of the code, you may have to make your selection, close the viewer and repoen it, before you can connect to the selected grid).
 
 
= Submit Patches =
This is probably faaar down the road, but if you make changes to the source and want to submit them, see the page about [[submitting patches]].

Compiling the viewer (MSVS2005)

2007-11-13T17:49:47Z

Nicholaz Beresford: ares, openjpeg

{{Languages}}
{{CompileNav}}

This page explains how you can compile the viewer on Microsoft Windows using Visual Studio 2005 or Visual C++ Express 2005. Note that Lindens are using VS2003 and the whole setup is a bit easier there, so if you have Visual Studio 2003 available, you should read [[Compiling the viewer (MSVS2003)|compiling with VS2003]] and you will get less trouble with it than with VS2005.

Currently, only 32 bit binary is tested. There seems to be several trials to produce 64 bit Windows .EXE of the viewer. If you did, please write your experience on this wiki (regardless it was successful or not!)

The following explanation is adjusted for Viewer releases 1.16.0.5 or later. See an [http://wiki.secondlife.com/w/index.php?title=Compiling_the_viewer_%28MSVS2005%29&oldid=22294 older version of this page] for the Viewer releases 1.15 or before.

= Preparing the Development Environment =

== Installing/Configuring VS2005 ==

You need to setup the compiler and Microsoft Development tools as follows:
* Visual Studio 2005 '''''-or-''''' [http://msdn.microsoft.com/vstudio/express/visualc/download/ Visual C++ 2005 Express](Free) (Also, although not strictly necessary, eventually pick up and install SP1 for VS2005.)
* [http://www.microsoft.com/downloads/details.aspx?familyid=0BAF2B35-C656-4969-ACE8-E4C0C0716ADB&displaylang=en Microsoft Platform SDK]
* A DirectX 9.0 SDK released on or after Summer of 2003 [http://download.microsoft.com/download/5/1/f/51ff8357-0af3-418b-9d0b-e9a5cdc39759/dxsdk_dec2006.EXE DirectX 9.0 SDK (December 2006)] [http://www.microsoft.com/downloads/details.aspx?FamilyID=9216652f-51e0-402e-b7b5-feb68d00f298&displaylang=en DirectX 9.0 SDK Update (Summer 2003)]
: '''Note''': If you have previously installed an older version of the DirectX 9.0 SDK, remove it first (from Control Panel -> Add or Remove Programs) before installing this version. Installing the new SDK "on top" of an older version may cause problems.
* Set up the project globals:
** Start Microsoft Visual Studio 2005
** Go to Tools > Options > Projects > VC++ Directories
** Make sure that the '''includes''' ([[:Image:MSVS2005 Global Project Options Include Files.JPG|'''screen shot''']]) and '''libraries''' ([[:Image:MSVS2005 Global Project Options Library Files.JPG|'''screen shot''']]) paths have the Platform SDK paths first, then the DirectX SDK paths, and then the Visual C++ paths. You may need to check "Show All Settings" at the bottom for VC++ Directories to show.
*** Default installation of both Platform SDK and DirectX SDK can be found in '''C:\Program Files\Microsoft Platform SDK for Windows Server 2003 R2''' and '''C:\Program Files\Microsoft DirectX SDK (December 2006)''' respectively.
** If the DirectX SDK paths aren't present, add them to both '''includes''' and '''libraries'''.
*: Note: The newest DirectX SDK ("December 2006") lib folder has two sub-folders, x64 and x86. Make sure your path goes to one of them (select '''lib/x86''', not just '''lib'''), or you will get a Link error.
 

== Getting other Development Tools ==
You will also need some open source development tools.
* [http://www.cygwin.com/ 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. The project files use several hardcoded references that expect Cygwin to be installed at '''C:\cygwin''', if it's not you'll need to edit those references.
* [http://www.activestate.com/Products/ActivePython/?mp=1 ActivePython 2.3x or later] - Latest Version is 2.5.1.1
** It is required but can be avoided if you are compiling 1.18 or later viewers. Either download and install or hack the prebuild.bat files as described in [http://jira.secondlife.com/browse/VWR-1267 VWR-1267].
* ActivePerl was recommended for previous versions on this Wiki, but it currently appears, that it is not strictly necessary unless you are planning to build your own version of all libraries (which most likely you don't want to do). So for a start it may be safe to skip it.
*: [http://www.activestate.com/Products/ActivePerl/?mp=1 ActivePerl]

 
 
 

= Downloading Source Code =

You can download the Viewer source codes on the [[source downloads]] page. You can also use a [[version control repository]].

At a minimum, grab the source package and the artwork package, but for a start, also grab the library archive. Many of the libraries can either be compiled from source or downloaded from other sites (see below), but this will take hours and thus it is easiest to also get the package with libraries compiled by the Lindens.

'''WARNING:'''
* If the directory path you keep the SL source in has a space in it, the batch file that copies message_template.msg will fail. So, if you unzip or checkout the source tree into, e.g., "C:\Projects\Dir with space in name\Etc\linden", it won't work!
* You should also avoid using non-ASCII (national) characters in the paths, although some localized versions of the tool puts some as a default...
* Unzip or checkout your source tree into a directory that has as short full pathname as possible, since long paths cause some unexpected trouble during the build.

In other words, the easiest way to get this working is to get ''source'', ''artwork'' and ''libraries'' from the [[source downloads]] page and unpack them all into the same directory/folder, which ideally would be a folder in (or near) the root directory with a short name like ''sl_1_16_0_5''.
 
 
 
 

= Installing Libraries =

SL Viewer depends on some third party libraries. Some of them are open source, some others are not.

== Open Source Libraries ==

You can download the pre-build open source libraries from LL. They are available on [[source downloads]] page. Unzip them into your SL viewer source code directory, maintaining the same directory structure.

'''Note: The VS2003 libraries provided in the [[source downloads]] do not fully work with VS2005 compiled binaries. They will compile with the viewer under VS2005, but the VS2003 libraries are not fully STL compliant. The differences of [http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vclang/html/vclrfnonstandardbehavior.asp non-standard behavior in MSVS] are the known cause.'''

Alternatively, it may be possible to get the source files for the libraries and build by yourself. See [[Compiling the viewer libraries (MSVS 2003)|the instruction for VS2003 users]] if you try it. Please note, however, it is not known that VS2005 can successfully compile the libraries. '''You have been warned.''' (If you can make it, please write the info on this wiki...)
 
 

== Proprietary Libraries ==

Lindens does not inlcude the following proprietary libraries. You will need to follow the instructions to acquire below and copy them to the source path.

However, it probably is 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 (like ''XCOPY OLIB SL_1_16_0_5 /S''). The reason is, that these steps are cumbersome and will have to be repeated for each new release (at least if you keep the source for each release in it's own folder). If you do not want to do this, of course you can just copy the files directly into the linden source paths.

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
 
=== Fmod ===
* Download & extract [http://www.fmod.org/index.php/download fmod 3.75 api for win32] (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\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"
 

=== OpenGL ===
* Download [http://oss.sgi.com/projects/ogl-sample/sdk.html glext.h, glxext.h, and wglext.h]
* Copy them to "linden\libraries\i686-win32\include\GL"
* You don't need any additional *.lib or *.dll for OpenGL.
 

==== ares (viewer 1.18.4 and later) ====
* download c-ares 1.4 from [http://daniel.haxx.se/projects/c-ares/ here] and unpack it somewhere
* open vc.dsw from the c-ares/vc folder
* remove the adig and ahost projects from the vc workspace
* add ares_getnameinfo.c to the areslib project
* for areslib right-click, properties, Code Generation and set Runtime Library to /MT (release) and /MTd (debug)
* compile debug and release
* copy all c-ares\*.h files to linden\libraries\include\ares\*.h
* copy vc\areslib\Debug\*lib to linden\libraries\i686-win32\lib_debug
* copy vc\areslib\Release\*lib to linden\libraries\i686-win32\lib_release
 

==== openjpeg (viewer 1.18.4 and later) ====
* download the latest OpenJPEG from [http://www.openjpeg.org/ here]
* open the libopenjpeg.dsw, let it convert and compile it (you'll need the files from the dllopenjpeg sub-project)
* copy debug\openjpeg.lib to linden\libraries\i686-win32\lib_debug
* copy release\openjpeg.lib to linden\libraries\i686-win32\lib_release
* copy release\openjpeg.dll to linden\indra\newview
 

=== Quicktime ''(optional)'' ===
'''Note:''' This download requires a registration at the Apple Quicktime website and take a bit of time. You can avoid using QuickTime if you want, see [[#QuickTime removal|below]] for details. Remember that your viewer '''can't play in-world movies''' if you do so.
* Download & install the [http://connect.apple.com/cgi-bin/WebObjects/MemberSite.woa/203/wa/getSoftware?fileID=20525&code=y&source=x&wosid=4h16WcyMtVfd2P1EffGafkoxFcr 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".
 
 
 

= Configuring for VS2005 =

Lindens use VS2003 to develop the viewer.

You either need to convert ''solution file'' and ''project files'' from VS2003 format to VS2005 format or obtain files compatible with VS2005. You may also need to modify source files to work around the incompatibility between VS2003 and VS2005.

'''Note''': linden\indra\indra_complete_vs8.sln is a solution file already included in the source archive and intended for the Visual Studio 2005, but it '''does not work''' (at least between 1.14.0 and 1.17.0.9 distribution). This may change in a future release, if Lindens include an updated versions of the '''_vc8''' files.

 
 
== Using pre-built solution/project files ==

Currently there is a ZIP file with solution/project files available on the [https://jira.secondlife.com/browse/VWR-1151 JIRA bug tracker issue VWR-1151].

If you are building 1.16 or later, the easiest way towards compiling SL on MS2005 will be to use the zip file mentioned above. The details is as follows:
* Download the appropriate ZIP archive from JIRA.
* Unpack it and copy it onto your linden source tree (allow to overwrite files that have '''_vc8''' in the name).
* Start Visual Studio 2005 (or VC++ Express).
* Use "File > Open > Project/Solution" to open the linden\indra\indra_complete\indra_complete'''_vc8'''.sln (Note: If you plan to work with multiple versions over time, you will find it useful to rename '''indra_complete_vc8.sln''' to something which contains the version number, e.g. '''indra_1_17_0_11_vc8.sln''' before opening.)
* Right click '''newview''' in the frame Solution Explorer and click "Set as StartUp Project".
* Proceed with applying the '''Workarounds''' below (skip '''Manual conversion''').

'''Note:''' The solution/project files depends on the viewer release version. If you are compiling some specific version of the viewer, and the {{JIRA|VWR-1151}} doesn't list the zip file for you version, you can try using the most close one. If, while compiling, you later encounter errors or problems regarding the projects, you may have to do the manual conversion instead.

 

== Manual conversion of the solution/projects ==

If you can not find a set of project files (see above), there are instructions available how to manually do it: [[Converting_project_files_for_MSVS2005]] (this step will take about 5-15 minutes, depending on how proficient you are using VS2005).

 
 
 

== Workarounds ==

There are more compatibility problems between VS2003 and VS2005. You need the following code edits.
 
=== test project/crash_logger/updater ===

For whatever reason, the '''test''' project doesn't work under VS2005. Workaround is to disable it as follows: Right click on the '''test''' and choose '''Unload Project'''.

If you do not plan to create a full download build, you can exclude the '''win_crash_logger''' and '''win_updater''' from newview's project dependencies and unload them also. But be careful with unloading these projects without removing them from the dependencies, because I have seen VS2005 act highly erratic while linking then project when I tried this.
 
=== QuickTime removal ===

If you don't want to get Apple QuickTime SDK, you can disable it as follows:
*linden\indra\llcommon\llpreprocessor.h - near line 58 (the line below '''#elif LL_WINDOWS''')
--50: #define LL_QUICKTIME_ENABLED 1
++50: #define LL_QUICKTIME_ENABLED '''''0'''''

* Pick '''ReleaseNoOpt''' in the Solution Configurations drop-down box beside the green arrow under the tool bar, and do the followings on the Solution Explorer frame:
*Click '''newview''' to select it alone.
**Choose Properties.
**Under Configuration Properties > Linker > Input, click '''Additional Dependencies''' on the right to show a button labeled "'''...'''" on it at the very right on the line, then click the '''...''' button.
**Scroll down the list to find '''qtmlclient.lib'''. Delete this single line.
**Click '''OK''' to close the "Additional Dependencies" dialog, then click OK again to close the "newview Property Pages" dialog box.
* Pick '''ReleaseForDownload''' in the Solution Configurations drop-down box. Click '''newview''' to select it alone and do the same thing again.
 
 
 
= Ready, Set, Build! =

== Building ==
* Build either '''ReleaseNoOpt''' (for debugging) or '''ReleaseForDownload''' (for production code).
* To do this, pick either in the Solution Configurations drop-down box beside the green arrow under the tool bar.
* Make sure '''newview''' is set as the active project (otherwise set from newview's right-click menu).
* Select Build-Menu > Build Solution or press F7.
* newview_noopt.exe will be built in linden\indra\newview\ReleaseNoOpt or SecondLife.exe will be linden\indra\newview\ReleaseForDownload.
 
== Common compile errors ==
* See [[common compilation problems]] if you run into other errors while building.
 
== Running ==
* You can run the viewer by '''Debug > Start Debugging''' or '''Debug > Start Without Debugging''' in Visual Studio.
* To run it outside VS, create a shortcut to SecondLife.exe, and change the start location to linden\indra\newview\ (All the .dll will be found there.)
* Alternately copy the exe (possibly rename it) to your "c:\program files\secondlife" folder.
 
== Debugging Info/Configurations ==
* Usually you will either use '''ReleaseNoOpt''' or the '''ReleaseForDownload''' configuration.
* '''ReleaseNoOpt''' (not optimized) compiles faster and has more debugging information, but this comes at a runtime penalty of about 50% of your FPS in busy areas, compared to ReleaseForDownload build.
* '''ReleaseForDownload''' also has debugging information and runs fine in the debugger (although at times you may miss access to some local variables).
* '''ReleaseNoOpt''' comes with a seperate debugging console window opens and stays open for the duration of your session, but you can access the same information also by pressing Shift+Ctrl+4 in the viewer (all builds).
* The debug console log can also be redirected to a file if you add "2>secondlife.log" to the command line (Newview, Properties, Debugging, Command line arguments).
* If you want to build a '''Debug''' configuration, see the specific section with compile instructions on [[finding leaks]]
 

== Problems Running? ==
* '''Inventory errors''': If you're getting errors while trying to load your inventory, try [[Help:Stuck logging in|clearing your cache and deleting other temporary files]].
* '''Missing smime3 DLL''': Those are parts of the integrated web browser. Copy 'smime3.dll', 'nss3.dll', 'softokn3.dll', and 'ssl3.dll' files from your official client's main folder to "linden\indra\newview".
* '''Can't connect''': In the debug builds there is a selection box on the login screen to select the server to connect to. '''Agni''' is the production grid, '''aditi''' is the beta grid. (There seems to be a bug in this part of the code, you may have to make your selection, close the viewer and repoen it, before you can connect to the selected grid).
 
 
= Submit Patches =
This is probably faaar down the road, but if you make changes to the source and want to submit them, see the page about [[submitting patches]].

Compiling the viewer (MSVS2003)

2007-11-13T17:48:47Z

Nicholaz Beresford: openjpeg

{{CompileNav}}

The following instructions are for compiling the Second Life viewer on Windows for Visual Studio .Net 2003. If you are using more recent versions of Visual Studio, see [[Compiling the viewer (MSVS2005)]]. For other platforms including MacOS and Linux, see [[Compiling the viewer]].

If you get lost, or these instructions are incomplete, see [[communication tools]] for a list of ways to get in touch with people that can help.
 
 
== Development Environment ==
The following dev environment is what LL uses for Windows development. There is no reason that the Second Life viewer can not be built using other environments, but it will take some extra work.

(Instructions for building the viewer using Microsoft's Visual Studio .NET 2005 Express can be found [[Compiling the viewer (MSVS2005)|on another page]]. At the time of writing, Express was freely available.)
 
=== Visual Studio .NET 2003 Professional ===
* Download and install [http://www.microsoft.com/downloads/details.aspx?familyid=0BAF2B35-C656-4969-ACE8-E4C0C0716ADB&displaylang=en Microsoft Platform SDK]
* Download and install a DirectX 9.0 SDK released on or after Summer of 2003 [http://download.microsoft.com/download/5/1/f/51ff8357-0af3-418b-9d0b-e9a5cdc39759/dxsdk_dec2006.EXE DirectX 9.0 SDK (December 2006)] [http://www.microsoft.com/downloads/details.aspx?FamilyID=9216652f-51e0-402e-b7b5-feb68d00f298&displaylang=en DirectX 9.0 SDK Update (Summer 2003)]
** If you have previously installed an older version of the DirectX 9.0 SDK, remove it first (from Control Panel -> Add or Remove Programs) before installing this version. Installing the new SDK "on top" of an older version may cause problems.
** Upon installing, it is sufficient to install the '''include''' and '''libraries''' part. Other DX development tools are not necessary.
* Set up the project globals:
** Start Visual C++
** Go to Tools/Options/Projects/VC++ Directories
** Make sure that the '''includes''' and '''libraries''' paths are there (or otherwise add them) in the following order: 1) Platform SDK paths, 2) DirectX SDK paths, 3) Visual C++ paths
** If you are adding DirectX SDK paths, be aware that later versions of the DirectX SDK have subfolders inside the lib directory. With those make sure you select '''lib/x86''', not just '''lib'''.

=== Other Development Tools ===
You will also need some open source development tools.
* [http://www.cygwin.com/ 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. The project files use several hardcoded references that expect Cygwin to be installed at '''C:\cygwin''', if it's not you'll need to edit those references.
* [http://www.activestate.com/Products/ActivePython/?mp=1 ActivePython 2.3x or later] - Latest Version is 2.5.1.1
** You should install this if compiling 1.18 or later viewers, or else hack the prebuild .bat files as in [http://jira.secondlife.com/browse/VWR-1267 VWR-1267].
* ActivePerl was recommended for previous versions on this Wiki, but it currently appears, that it is not strictly necessary unless you are planning to build your own version of all libraries (which most likely you don't want to do). So for a start it may be safe to skip it.
*: [http://www.activestate.com/Products/ActivePerl/?mp=1 ActivePerl]
 
 
 

== Source Code ==
The easiest way to get this working is to get '''source''', '''artwork''' and '''libraries''' for the same version from the [[source downloads]] page and unpack them all into the same directory/folder, which ideally would be a folder in (or near) the root directory with a short name like ''sl_1_16_0_5''.
'''Note:''' Avoid folder names with spaces in them (this means avoid putting the project into your ''My Documents'' folder).
 
 
 
== Open Source Libraries ==

Some libraries can be distributed with the SL source and there is a library package available with the source. As mentioned above (about the source), you can simply extract the '''library''' archive and copy the files to your code directory, maintaining the same directory structure.

If instead you are interested in compiling these libraries from their source (instead of using the above zipfile of precompiled libraries provided by Linden Lab), see [[Compiling the viewer libraries (MSVS 2003)]]
 
 
== Other Libraries ==

Linden Lab included all the libraries/includes they can ship with their source, but we can not distribute the source to the following , and you will need to follow the instructions to acquire below.

However, it probably is 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 (like ''XCOPY olibs sl_1_16_0_5 /S''). The reason is, that these steps are cumbersome and will have to be repeated for each new release (at least if you keep the source for each release in it's own folder).

If you do not want to do this, of course you can just copy the files directly into the linden source paths.

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

==== Fmod ====
* Download & extract [http://www.fmod.org/index.php/download fmod 3.75 api for win32].
* Copy "fmodapi375win\api\inc\fmod.h" to "linden\libraries\include"
* Copy "fmodapi375win\api\inc\fmod_errors.h" to "linden\libraries\include"
* Copy "fmodapi375win\api\lib\fmodvc.lib" to "linden\libraries\i686-win32\lib_release"
* Copy "fmodapi375win\api\lib\fmodvc.lib" to "linden\libraries\i686-win32\lib_debug"
* Copy "fmodapi375win\api\fmod.dll" to "linden\indra\newview"

==== gl ====
* Download [http://oss.sgi.com/projects/ogl-sample/sdk.html glext.h, glxext.h, and wglext.h]
* Copy them to "linden\libraries\i686-win32\include\GL"

==== ares (viewer 1.18.4 and later) ====
* download c-ares 1.4 from [http://daniel.haxx.se/projects/c-ares/ here] and unpack it somewhere
* open vc.dsw from the c-ares/vc folder
* remove the adig and ahost projects from the vc workspace
* add ares_getnameinfo.c to the areslib project
* for areslib right-click, properties, Code Generation and set Runtime Library to /MT (release) and /MTd (debug)
* compile debug and release
* copy all c-ares\*.h files to linden\libraries\include\ares\*.h
* copy vc\areslib\Debug\*lib to linden\libraries\i686-win32\lib_debug
* copy vc\areslib\Release\*lib to linden\libraries\i686-win32\lib_release

==== openjpeg (viewer 1.18.4 and later) ====
* download the latest OpenJPEG from [http://www.openjpeg.org/ here]
* open the libopenjpeg.dsw, let it convert and compile it (you'll need the files from the dllopenjpeg sub-project)
* copy debug\openjpeg.lib to linden\libraries\i686-win32\lib_debug
* copy release\openjpeg.lib to linden\libraries\i686-win32\lib_release
* copy release\openjpeg.dll to linden\indra\newview

==== Quicktime (Optional) ====
* '''Note:''' Quicktime download can be skipped '''if you can live with a build that does not play in-world movies''' (some minor modifications to the project are necessary then, see "QuickTime removal" on the build instructions for [[Compiling the viewer (MSVS2005)|Visual Studio 2005]]).
* Download & install the [http://developer.apple.com/quicktime/download/ Quicktime SDK for Windows]
* Copy "QuicktimeSDK\Libraries\QTMLClient.lib" to "linden\libraries\i686-win32\lib_release".
* Copy "QuicktimeSDK\Libraries\QTMLClient.lib" to "linden\libraries\i686-win32\lib_debug".
* Copy the contents of "QuicktimeSDK\CIncludes" into "linden\libraries\i686-win32\include\quicktime".
 
 
== Building ==
* Open the '''indra\indra_complete\indra_complete.sln''' solution in Visual Studio (Note: If you plan to work with multiple versions over time, you will find it useful to rename '''indra_complete.sln''' to something which contains the version number, e.g. '''indra_1_17_0_11.sln''' before opening)
* Set newview to be the startup project.
* Build either '''ReleaseNoOpt''' (for debugging) or '''ReleaseForDownload''' (for running/debugging production code).
* Note that the ReleaseForDownload build also contains debug information and can be run in the debugger.
* newview_noopt.exe will be built in \indra\newview\ReleaseNoOpt, or SecondLife.exe will be built in \indra\newview\ReleaseForDownload
* To run it outside VS, create a shortcut to SecondLife.exe, and change the start location to linden\indra\newview\ (all the .dll will be found there.)
* Alternately copy the exe (possibly rename it) to your "c:\program files\second life" folder.
* There were additional steps required in version 1.15 which seem to be fixed now. If you are trying to build 1.15 see an [https://wiki.secondlife.com/w/index.php?title=Compiling_the_viewer_%28MSVS2003%29&oldid=23026 older version of this page].
 
 

== Errors while building? ==
See [[Common compilation problems]] if you run into errors while building.
 
 
 
== Configurations/Debugging Info ==
* You will usually compile/debug the '''ReleaseNoOpt''' or ReleaseForDownload configuration ('''Debug''' should also work but should not really be necessary).
* '''ReleaseNoOpt''' compiles faster and has more debugging information, but this comes at a runtime penalty of about 50% of your FPS in busy areas, compared to ReleaseForDownload build.
* '''ReleaseForDownload''' runs fine in the debugger, but times you may miss debugger access to some local variables or the debugger may even show wrong values for objects and members, because it is confused by the optimizations.
* '''ReleaseNoOpt''' comes with a seperate debugging console window opens and stays open for the duration of your session.
* You can see the last few lines from the debugger console also by pressing Shift+Ctrl+4 in the viewer (all builds).
* The debug log (usually in application data) can also be redirected to a more file if you add "-log secondlife.log" to the command line (Newview, Properties, Debugging, Command line arguments).
* If you want to build a '''Debug''' configuration, see the specific section with compile instructions on [[Finding_leaks]]
 
 
== Problems Running? ==
* Viewer Error: '''Second Life is unable to access a file that it needs.''': Did you neglect to download the Artworks archive from the [[source downloads]] page? It is in the Viewer column, below the OS-specific Viewer archives.
* '''Can't connect''': In the debug builds there is a selection box on the login screen to select the server to connect to. '''Agni''' is the production grid, '''aditi''' is the beta grid. (There seems to be a bug in this part of the code, you may have to make your selection, close the viewer and repoen it, before you can connect to the selected grid).
* '''Inventory errors''': If you're getting errors while trying to load your inventory, try [[Help:Stuck logging in|clearing your cache and deleting other temporary files]].
* If you want to connect to the beta grid, add '''--aditi''' to the command line (Newview, Properties, Debugging, Command line argument).
* '''Missing smime3 DLL''': Those are parts of the integrated web browser. Copy 'smime3.dll', 'nss3.dll', 'softokn3.dll', and 'ssl3.dll' files from your official client's main folder to "linden\indra\newview".
 
 

== Submit Patches ==
This is probably far down the road, but if you make changes to the source and want to submit them, see the page about [[Submitting patches|submitting patches]].

Compiling the viewer (MSVS2003)

2007-11-11T14:32:17Z

Nicholaz Beresford: c-ares

{{CompileNav}}

The following instructions are for compiling the Second Life viewer on Windows for Visual Studio .Net 2003. If you are using more recent versions of Visual Studio, see [[Compiling the viewer (MSVS2005)]]. For other platforms including MacOS and Linux, see [[Compiling the viewer]].

If you get lost, or these instructions are incomplete, see [[communication tools]] for a list of ways to get in touch with people that can help.
 
 
== Development Environment ==
The following dev environment is what LL uses for Windows development. There is no reason that the Second Life viewer can not be built using other environments, but it will take some extra work.

(Instructions for building the viewer using Microsoft's Visual Studio .NET 2005 Express can be found [[Compiling the viewer (MSVS2005)|on another page]]. At the time of writing, Express was freely available.)
 
=== Visual Studio .NET 2003 Professional ===
* Download and install [http://www.microsoft.com/downloads/details.aspx?familyid=0BAF2B35-C656-4969-ACE8-E4C0C0716ADB&displaylang=en Microsoft Platform SDK]
* Download and install a DirectX 9.0 SDK released on or after Summer of 2003 [http://download.microsoft.com/download/5/1/f/51ff8357-0af3-418b-9d0b-e9a5cdc39759/dxsdk_dec2006.EXE DirectX 9.0 SDK (December 2006)] [http://www.microsoft.com/downloads/details.aspx?FamilyID=9216652f-51e0-402e-b7b5-feb68d00f298&displaylang=en DirectX 9.0 SDK Update (Summer 2003)]
** If you have previously installed an older version of the DirectX 9.0 SDK, remove it first (from Control Panel -> Add or Remove Programs) before installing this version. Installing the new SDK "on top" of an older version may cause problems.
** Upon installing, it is sufficient to install the '''include''' and '''libraries''' part. Other DX development tools are not necessary.
* Set up the project globals:
** Start Visual C++
** Go to Tools/Options/Projects/VC++ Directories
** Make sure that the '''includes''' and '''libraries''' paths are there (or otherwise add them) in the following order: 1) Platform SDK paths, 2) DirectX SDK paths, 3) Visual C++ paths
** If you are adding DirectX SDK paths, be aware that later versions of the DirectX SDK have subfolders inside the lib directory. With those make sure you select '''lib/x86''', not just '''lib'''.

=== Other Development Tools ===
You will also need some open source development tools.
* [http://www.cygwin.com/ 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. The project files use several hardcoded references that expect Cygwin to be installed at '''C:\cygwin''', if it's not you'll need to edit those references.
* [http://www.activestate.com/Products/ActivePython/?mp=1 ActivePython 2.3x or later] - Latest Version is 2.5.1.1
** You should install this if compiling 1.18 or later viewers, or else hack the prebuild .bat files as in [http://jira.secondlife.com/browse/VWR-1267 VWR-1267].
* ActivePerl was recommended for previous versions on this Wiki, but it currently appears, that it is not strictly necessary unless you are planning to build your own version of all libraries (which most likely you don't want to do). So for a start it may be safe to skip it.
*: [http://www.activestate.com/Products/ActivePerl/?mp=1 ActivePerl]
 
 
 

== Source Code ==
The easiest way to get this working is to get '''source''', '''artwork''' and '''libraries''' for the same version from the [[source downloads]] page and unpack them all into the same directory/folder, which ideally would be a folder in (or near) the root directory with a short name like ''sl_1_16_0_5''.
'''Note:''' Avoid folder names with spaces in them (this means avoid putting the project into your ''My Documents'' folder).
 
 
 
== Open Source Libraries ==

Some libraries can be distributed with the SL source and there is a library package available with the source. As mentioned above (about the source), you can simply extract the '''library''' archive and copy the files to your code directory, maintaining the same directory structure.

If instead you are interested in compiling these libraries from their source (instead of using the above zipfile of precompiled libraries provided by Linden Lab), see [[Compiling the viewer libraries (MSVS 2003)]]
 
 
== Other Libraries ==

Linden Lab included all the libraries/includes they can ship with their source, but we can not distribute the source to the following , and you will need to follow the instructions to acquire below.

However, it probably is 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 (like ''XCOPY olibs sl_1_16_0_5 /S''). The reason is, that these steps are cumbersome and will have to be repeated for each new release (at least if you keep the source for each release in it's own folder).

If you do not want to do this, of course you can just copy the files directly into the linden source paths.

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

==== Fmod ====
* Download & extract [http://www.fmod.org/index.php/download fmod 3.75 api for win32].
* Copy "fmodapi375win\api\inc\fmod.h" to "linden\libraries\include"
* Copy "fmodapi375win\api\inc\fmod_errors.h" to "linden\libraries\include"
* Copy "fmodapi375win\api\lib\fmodvc.lib" to "linden\libraries\i686-win32\lib_release"
* Copy "fmodapi375win\api\lib\fmodvc.lib" to "linden\libraries\i686-win32\lib_debug"
* Copy "fmodapi375win\api\fmod.dll" to "linden\indra\newview"

==== gl ====
* Download [http://oss.sgi.com/projects/ogl-sample/sdk.html glext.h, glxext.h, and wglext.h]
* Copy them to "linden\libraries\i686-win32\include\GL"

==== ares (viewer 1.18.4 and later) ====
* download c-ares 1.4 from [http://daniel.haxx.se/projects/c-ares/ here] and unpack it somewhere
* open vc.dsw from the c-ares/vc folder
* remove the adig and ahost projects from the vc workspace
* add ares_getnameinfo.c to the areslib project
* for areslib right-click, properties, Code Generation and set Runtime Library to /MT (release) and /MTd (debug)
* compile debug and release
* copy all c-ares\*.h files to linden\libraries\include\ares\*.h
* copy vc\areslib\Debug\*lib to linden\libraries\i686-win32\lib_debug
* copy vc\areslib\Release\*lib to linden\libraries\i686-win32\lib_release

==== Quicktime (Optional) ====
* '''Note:''' Quicktime download can be skipped '''if you can live with a build that does not play in-world movies''' (some minor modifications to the project are necessary then, see "QuickTime removal" on the build instructions for [[Compiling the viewer (MSVS2005)|Visual Studio 2005]]).
* Download & install the [http://developer.apple.com/quicktime/download/ Quicktime SDK for Windows]
* Copy "QuicktimeSDK\Libraries\QTMLClient.lib" to "linden\libraries\i686-win32\lib_release".
* Copy "QuicktimeSDK\Libraries\QTMLClient.lib" to "linden\libraries\i686-win32\lib_debug".
* Copy the contents of "QuicktimeSDK\CIncludes" into "linden\libraries\i686-win32\include\quicktime".
 
 
== Building ==
* Open the '''indra\indra_complete\indra_complete.sln''' solution in Visual Studio (Note: If you plan to work with multiple versions over time, you will find it useful to rename '''indra_complete.sln''' to something which contains the version number, e.g. '''indra_1_17_0_11.sln''' before opening)
* Set newview to be the startup project.
* Build either '''ReleaseNoOpt''' (for debugging) or '''ReleaseForDownload''' (for running/debugging production code).
* Note that the ReleaseForDownload build also contains debug information and can be run in the debugger.
* newview_noopt.exe will be built in \indra\newview\ReleaseNoOpt, or SecondLife.exe will be built in \indra\newview\ReleaseForDownload
* To run it outside VS, create a shortcut to SecondLife.exe, and change the start location to linden\indra\newview\ (all the .dll will be found there.)
* Alternately copy the exe (possibly rename it) to your "c:\program files\second life" folder.
* There were additional steps required in version 1.15 which seem to be fixed now. If you are trying to build 1.15 see an [https://wiki.secondlife.com/w/index.php?title=Compiling_the_viewer_%28MSVS2003%29&oldid=23026 older version of this page].
 
 

== Errors while building? ==
See [[Common compilation problems]] if you run into errors while building.
 
 
 
== Configurations/Debugging Info ==
* You will usually compile/debug the '''ReleaseNoOpt''' or ReleaseForDownload configuration ('''Debug''' should also work but should not really be necessary).
* '''ReleaseNoOpt''' compiles faster and has more debugging information, but this comes at a runtime penalty of about 50% of your FPS in busy areas, compared to ReleaseForDownload build.
* '''ReleaseForDownload''' runs fine in the debugger, but times you may miss debugger access to some local variables or the debugger may even show wrong values for objects and members, because it is confused by the optimizations.
* '''ReleaseNoOpt''' comes with a seperate debugging console window opens and stays open for the duration of your session.
* You can see the last few lines from the debugger console also by pressing Shift+Ctrl+4 in the viewer (all builds).
* The debug log (usually in application data) can also be redirected to a more file if you add "-log secondlife.log" to the command line (Newview, Properties, Debugging, Command line arguments).
* If you want to build a '''Debug''' configuration, see the specific section with compile instructions on [[Finding_leaks]]
 
 
== Problems Running? ==
* Viewer Error: '''Second Life is unable to access a file that it needs.''': Did you neglect to download the Artworks archive from the [[source downloads]] page? It is in the Viewer column, below the OS-specific Viewer archives.
* '''Can't connect''': In the debug builds there is a selection box on the login screen to select the server to connect to. '''Agni''' is the production grid, '''aditi''' is the beta grid. (There seems to be a bug in this part of the code, you may have to make your selection, close the viewer and repoen it, before you can connect to the selected grid).
* '''Inventory errors''': If you're getting errors while trying to load your inventory, try [[Help:Stuck logging in|clearing your cache and deleting other temporary files]].
* If you want to connect to the beta grid, add '''--aditi''' to the command line (Newview, Properties, Debugging, Command line argument).
* '''Missing smime3 DLL''': Those are parts of the integrated web browser. Copy 'smime3.dll', 'nss3.dll', 'softokn3.dll', and 'ssl3.dll' files from your official client's main folder to "linden\indra\newview".
 
 

== Submit Patches ==
This is probably far down the road, but if you make changes to the source and want to submit them, see the page about [[Submitting patches|submitting patches]].

Talk:Viewer Authentication Critique

2007-09-30T14:51:55Z

Nicholaz Beresford: added author of "No balance" paragraph

{{Talk}}

== Process for editing the critique ==

By virtue of jumping first, I think [[User:Matthew Dowd|Matthew Dowd]] should be the working group chair for editing this document. What I think that means is this:
* Anyone can still make no-brainer edits to the article
* Matthew will be arbiter for dispute resolution, should that be necessary.
* If there are points that Matthew is unclear about, he should delete them from the document, and move them to the talk page.
* If there are points that others are unclear about, they should bring them up on the talk page, and then later delete them from the main page if a question/concern goes unanswered on the talk page (with "see talk page" in the comment of the edit).
* If, for whatever reason, it becomes necessary to fork this document, it's best to move all critiques into the user space of the working group chair. So, for example, Matthew's version would move to [[User:Matthew Dowd/Viewer Authentication Critique]], and other critiques could also be done the same way. This page would become a list of critiques.

Sound like a reasonable process? I think this is lightweight enough that a pretty good document can evolve pretty quickly. -- [[User:Rob Linden|Rob Linden]] 12:56, 29 September 2007 (PDT)

== Third party viewers/code ==

What's the substantive difference between these two points?
# Viewer still involves running trusted code on the computer and could initiate other attacks e.g.
# Most of these attacks could be performed by any third-party software designed for use with SL
Both have many subpoints. Could they be consolidated into a single point? -- [[User:Rob Linden|Rob Linden]] 20:10, 29 September 2007 (PDT)

The first point is that keeping the client from seeing the password doesn't remove the danger of a modified client.

The second point is that *any* ancillary software (such as animation editors, sculpt editors, sculpt texture plugins) could be used in an attack, even if they don't actually connect to SL, since they would be used by SL residents.

-- [[User:Argent Stonecutter|Argent Stonecutter]] 21:00, 29 September 2007 (PDT)

Is this better, Rob? -- [[User:Argent Stonecutter|Argent Stonecutter]] 21:11, 29 September 2007 (PDT)

:Yes, that is. Thanks for the clarification! -- [[User:Rob Linden|Rob Linden]] 21:44, 29 September 2007 (PDT)

== No balance ==

This article is pretty awful, its just an attack. For real critique you have to explore the alternatives and discuss the pros and cons for each.
Even if this form of log in has these disadvantages it could still be an improvement over what we currently have.
We need a common point of reference to discuss if this is an improvement and what alternatives exist. (<-- this paragraph seems to be from "Ahab Schmo" (note added by [[User:Nicholaz Beresford|Nicholaz]]))

Viewer Authentication Critique

2007-09-30T10:42:16Z

Nicholaz Beresford: signed new version

This is a formal critique of [[Viewer Authentication]] that was [https://lists.secondlife.com/pipermail/sldev/2007-September/005403.html requested] by [[User:Rob Linden]] on the [[SLDev]] mailing list.

For a branch of the discussion see [https://wiki.secondlife.com/wiki/Talk:Viewer_Authentication Talk page on the original proposal.]

== Summary ==

The new authentication method proposed by LL seems to be an attempt to solve a perceived but non-existent problem.

There are no known password capturing third party viewers in the wild, and a third party viewer requires such a privilege level of access to an account anyway that if you don't trust it with your username and password, you shouldn't be running it anyway. The mechanism proposed, however, is more prone to phishing attacks. Most password compromises are probably due to weaknesses in the current protocol challenge response or due to allowing weak passwords.

Providing a single authentication mechanism for LL (and third party) websites would be an improvement to multiple backend copies of username and password, however this could be implemented without touching the viewer authentication method.

There seems to be no demand to synchronise the authentication of the viewer with authentication on the SL web site (account, forums, etc.), and any benefits gained would be negated by the problems this would cause anyone running alts (e.g. for in world permissions testing etc.) or multiple viewers (e.g. main, test and firstlook). It also raises problems for those running OpenSim based Grids, and may also cause difficulties further down the line as regards the new architecture discussions.

It was also noted that consideration should be given when considering enhancements to the security/authentication models whether these should be optional - allowing users to make their own risk/convenience decisions.

== Security ==

=== LL's Objectives ===
* To mitigate the danger of password capturing Trojans masquerading as third party viewers
* Improve trust in third party viewers by providing a means of assurance to the user that the third party viewer could not be a Trojan capturing usernames and passwords.

=== Pros ===
* Viewer does not have to process (and "see") username and password

=== Cons ===
* The main risk of running a third party viewer (or any other application not provided by Linden Labs) is not stealing passwords, it's direct attacks through the client... and the "official" client is not really any protection against that.
** Viewer can still be used in direct and indirect attacks even if it never sees the password (for example: salami slicing through cutout accounts, acting as a cutout account or an in-world botnet, faking a failed connection while giving an attacker access).
** NON-viewer applications (such as editors, 3d tools) designed for use by SL residents could use a keystroke logger and macro to perform any of these attacks, or could inject code into the viewer to do the same thing. Look at 'cheating' programs in combat MMORPGs for ideas.
* But this is still not a large risk, unless people get the client through a mechanism that makes the creator anonymous. Historically, attempts to disseminate boobytrapped versions of applications have only worked in environments where it's routine for people to download applications from anonymous sources (file areas in the BBS era, for example). It's too easy to trace down the originator of any compromised client when you're getting them from their own website.
 
* Bottom line here is that third party viewers stealing passwords are a very small risk for the user: the bigger risk is from the web browser!
** Potential for phishing websites to entice users to enter username and password and then pass control to SL website and viewer.
*** This kind of attack is not theoretical, phishing websites are a criminal industry.
*** It would be very easy to set up a temporary (i.e. hard to trace the real owner) phishing webpage which looks like the official SL logon, and send e-mails such as "You've received xxx in SL, Click here to logon" apparently from LL - with far less work than trying to create, and entice people to download a trojan viewer
** Relies on browser security, and uses a mechanism often disabled or filtered due to security concerns
** Too reliant on browser/OS implementations (proxies, firewalls, used browsers, etc.)
* So using the browser to perform the authentication moves the authentication to a mechanism that has historically proven more likely to be compromised.
 
* And the mechanism itself is relatively inflexible.
** Links to secondlife:// can only point to one instance (version, e.g. homebrew, release candidate official) of the program
** Links to secondlife:// can not pass parameters to the program
*** In fact allowing that was a security flaw recently found and fixed in the SL client. :(
** It will raise problems for those running alternative (e.g. OpenSim) grids, and also have impact on the dicussions for a future open grid.
 
* Possibility some third party clients will retain the existing UI in order to make it easier for people with alts and multiple clients, and do appropriate GETs and POSTs on the SL to initiate a logon and get the token (thus defeating the original purpose)
** The issues raised in the next sections would mean that people would have an incentive to use this kind of client.

=== Alternatives ===
* One time passwords (for copy paste into a non-secure viewer or to print and take with you to friends, internet cafes, public terminals, etc.)
* lower perm passwords (pwds which put the account into a restricted state, disallowing "dangerous" transactions)
* separate passwords for website account and being inworld
* Account restrictions
* Allow third party plug-ins in the viewer (these would allow the extra functionality which are sometimes the reason for running third party viewers, but would rely on the official viewer for validation)
 
* This may be the wrong problem - password compromises are more likely to be through standard phishing attacks (logon here to update your account info) which is not addressed, or by weaknesses in the current authentication mechnism or just insecure passwords.
** CRAM-MD5 or a similar challenge-response type
** Dictionary check to reject insecure passwords

== Flexibility ==

=== LL's Objectives ===
* Single Sign On - allowing multiple web applications (forums, support, account, jira, wiki etc.) and viewers to use the same username and password through a single point without duplicating usernames and passwords into multiple systems
* Extension of this to allow non-LL applications and web sites to participate in this single sign on system.

=== Pros ===
* Enables username/password authentication to work on third party sites without them having to "see" username and password

=== Cons ===
* This is really an unrelated issue...
** The client doesn't need to depend on the website for this purpose, or this could be a command line option.
** The client could just as easily be the 'authentication source' as the website.
*** Via a "go to website" link in the client that passed an equivalent token.
 
* As noted in section 1, this reduces flexibility for the *users* which may result in third party viewers adopting the current UI and doing the authentication behind the scenes

=== Alternatives ===
* Use this mechanism for websites (including third party) only but not for viewers
 
* Identity Metasystem - [http://en.wikipedia.org/wiki/Identity_Metasystem]
** OpenID - [http://openid.net/]
** CardSpace - [http://msdn2.microsoft.com/en-us/netframework/aa663320.aspx]
** Shibboleth - [http://shibboleth.internet2.edu/]
** CAS - [http://www.ja-sig.org/products/cas/]
*** These could be handled by the client poping up a window using the internal web browser to connect to a HTML logon. It may be difficult or impossible to determine if the client really is displaying the official HTML logon and not capturing key strokes so this would be a way of implementing the above for flexibility or other reasons (e.g. brokered identity verification [http://www.agimo.gov.au/publications/2004/05/egovt_challenges/privacy/identity/brokered]) not for security

== Persistence ==

=== LL's Objectives ===
* To synchronise the various LL's systems (forums, support, jira, account, etc.) so that by logging onto one, you are automatically logged onto the others.

=== Pros ===
* None offered!
** Is this really needed or desirable (''for the client'')? SL is not an extension of the web, it's a different kind of interface... one that has the potential of becoming a "3d web".

=== Cons ===
* As in the previous section, LL's objectives could be met without the viewer logging in via the same mechanism.
* Inconvenient for those with alts or multiple clients
** Cumbersome to change alts and logon with multiple alts
** Those with alts, often have a primary account which is used for forums and logged on permanently to forums even when the alt is online in SL
** As noted in section 1, this reduces flexibility for the *users* which may result in third party viewers adopting the current UI and doing the authentication behind the scenes
* Danger on public or multi-user machines that the user will log out of the client, but not log out of the website properly allowing the next user to access their account.
* Staying online on secondlife.com (which many people seem to do) automatically means anyone with access to the computer/browser (family) can log in with the account inworld
* starting SL from the web browser on a regular basis will most likely result in the web browser lingering in memory in the background when running the viewer, which based on the heavy memory requirement may impair viewer performance.
* this would make things harder for independent grids to use the official client, and have impact on the architecture discussions for a future open grid.

=== Alternatives ===
* Not really felt to be an issue needing any resolution!
== Signatories ==

Please sign this below with "<nowiki>~~~~</nowiki>" if you agree with the version of this document you are reading. The date will indicate which version of the document you read and agree with.

* [[User:Matthew Dowd|Matthew Dowd]] 11:27, 29 September 2007 (PDT)
* [[User:Argent Stonecutter|Argent Stonecutter]] 13:53, 29 September 2007 (PDT)
* [[User:Dale Glass|Dale Glass]] 14:28, 29 September 2007 (PDT)
* [[User:Tillie Ariantho|Tillie Ariantho]] 14:53, 29 September 2007 (PDT)
* [[User:Jesse Barnett|Jesse Barnett]] 20:59, 29 September 2007 (PDT)
* [[User:Winter Ventura|Winter Ventura]] 19:42, 29 September 2007 (PDT)
* [[User:Balp Allen|Balp Allen]] 01:33, 30 September 2007 (PDT)
* [[User:Michelle2 Zenovka|Michelle2 Zenovka]] 02:52, 30 September 2007 (PDT)
* [[User:Nicholaz Beresford|Nicholaz]] 03:42, 30 September 2007 (PDT)

Viewer Authentication Critique

2007-09-29T22:38:41Z

Nicholaz Beresford: signed

Viewer Authentication Critique

2007-09-29T20:22:31Z

Nicholaz Beresford: whitespace

Viewer Authentication Critique

2007-09-29T20:19:44Z

Nicholaz Beresford: various bullets

Talk:Viewer Authentication

2007-09-29T13:14:25Z

Nicholaz Beresford:

I am sorry but the incidences of account hijacking from persistant logins is going to be FAR greater than incidences from phishing.

How you can actually write something like "So long as you are logged into the website on someone's else computer, they will be able to gain access to your account" and then continue on with the idea /at all/ is astonishing.

Log into web site and launch SL? That's fine by itself. "There" worked that way and it was ok, not as good from a pure usability standpoint but ok..., but it it /cannot/ be persistant. We are talking about real money theft here. This is a lowering of security not an increase in it. And I know that other people do it and there is a "remember password" checkbox on the viewer but that doesn't excuse this. If increasing security is actually the goal, persistant logins anywhere are an about face to it.

----
This is like snogging SARS patients to improve your health.

Web based UIs are the #1 tool for phishing. The most commonly used web browser in the world is not just insecure, it has security holes that can not even in theory be fixed. It has been a running gag for 10 years now. And if you're worried about people using open source software for phishing, the popular open source browsers are actually MORE secure than the native ones on BOTH Windows and OS X.

On Linux, ALL the browsers are open-source.

This change will reduce reliability, reduce security, and reduce people's confidence in SL. If anything, you should be centralizing logins in the client and have it handle authenticating the browser, not the other way around. -- [[User:Argent Stonecutter|Argent Stonecutter]] 22:09, 28 September 2007 (PDT)

PS: you also need to fix the proxy support in SL before you even THINK of making it use that splash screen for logging in, because that bad boy never even shows up if you're behind a proxy. -- [[User:Argent Stonecutter|Argent Stonecutter]] 22:18, 28 September 2007 (PDT)
----
This should go long intense beta (release candidate) before switching. Things like proxies, network, and a thousand other variants will break this and make it impossible for people to log in.

For example for some debugging scenarios I'm compiling the viewer without llmozlib. If anything, the web communication in the first iteration should happen through libcurl.

[[User:Nicholaz Beresford|Nicholaz]]
----
The weakest point in the approach however is that a malicious viewer can do anything it needs, once logged in. And when started it can simply install a keystroke logger.

Even a web based application (promising to do whatever would appeal to people) could redirect to the SecondLife page for login, either spoofing the SL page or just grabbing the legit login token and then do something else with it.

The only way I see in order to increase security in relation to transactions and valuable assets is to protect these transactions with disposable passwords or one time transaction numbers (TANs), which is an established procedure in the bank industry. But even then a viewer could simply catch the TAN and execute a different transaction instead.

Another approach would be to issue secondary passwords with limited power, so that a viewer logged in with that, will never be able to execute power transactions.
[[User:Nicholaz Beresford|Nicholaz]]
----

Compiling the viewer (MSVS2003)

2007-09-27T08:31:31Z

Nicholaz Beresford:

{{CompileNav}}

The following instructions are for compiling the Second Life viewer on Windows for Visual Studio .Net 2003. If you are using more recent versions of Visual Studio, see [[Compiling the viewer (MSVS2005)]]. For other platforms including MacOS and Linux, see [[Compiling the viewer]].

If you get lost, or these instructions are incomplete, see [[communication tools]] for a list of ways to get in touch with people that can help.
 
 
== Development Environment ==
The following dev environment is what LL uses for Windows development. There is no reason that the Second Life viewer can not be built using other environments, but it will take some extra work.

(Instructions for building the viewer using Microsoft's Visual Studio .NET 2005 Express can be found [[Compiling the viewer (MSVS2005)|on another page]]. At the time of writing, Express was freely available.)
 
=== Visual Studio .NET 2003 Professional ===
* Download and install [http://www.microsoft.com/downloads/details.aspx?familyid=0BAF2B35-C656-4969-ACE8-E4C0C0716ADB&displaylang=en Microsoft Platform SDK]
* Download and install a DirectX 9.0 SDK released on or after Summer of 2003 [http://download.microsoft.com/download/5/1/f/51ff8357-0af3-418b-9d0b-e9a5cdc39759/dxsdk_dec2006.EXE DirectX 9.0 SDK (December 2006)] [http://www.microsoft.com/downloads/details.aspx?FamilyID=9216652f-51e0-402e-b7b5-feb68d00f298&displaylang=en DirectX 9.0 SDK Update (Summer 2003)]
** If you have previously installed an older version of the DirectX 9.0 SDK, remove it first (from Control Panel -> Add or Remove Programs) before installing this version. Installing the new SDK "on top" of an older version may cause problems.
** Upon installing, it is sufficient to install the '''include''' and '''libraries''' part. Other DX development tools are not necessary.
* Set up the project globals:
** Start Visual C++
** Go to Tools/Options/Projects/VC++ Directories
** Make sure that the '''includes''' and '''libraries''' paths are there (or otherwise add them) in the following order: 1) Platform SDK paths, 2) DirectX SDK paths, 3) Visual C++ paths
** If you are adding DirectX SDK paths, be aware that later versions of the DirectX SDK have subfolders inside the lib directory. With those make sure you select '''lib/x86''', not just '''lib'''.

=== Other Development Tools ===
You will also need some open source development tools.
* [http://www.cygwin.com/ 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. The project files use several hardcoded references that expect Cygwin to be installed at '''C:\cygwin''', if it's not you'll need to edit those references.
* [http://www.activestate.com/Products/ActivePython/?mp=1 ActivePython 2.3x or later] - Latest Version is 2.5.1.1
** You should install this if compiling 1.18 or later viewers, or else hack the prebuild .bat files as in [http://jira.secondlife.com/browse/VWR-1267 VWR-1267].
* ActivePerl was recommended for previous versions on this Wiki, but it currently appears, that it is not strictly necessary unless you are planning to build your own version of all libraries (which most likely you don't want to do). So for a start it may be safe to skip it.
*: [http://www.activestate.com/Products/ActivePerl/?mp=1 ActivePerl]
 
 
 

== Source Code ==
The easiest way to get this working is to get '''source''', '''artwork''' and '''libraries''' for the same version from the [[source downloads]] page and unpack them all into the same directory/folder, which ideally would be a folder in (or near) the root directory with a short name like ''sl_1_16_0_5''.
'''Note:''' Avoid folder names with spaces in them (this means avoid putting the project into your ''My Documents'' folder).
 
 
 
== Open Source Libraries ==

Some libraries can be distributed with the SL source and there is a library package available with the source. As mentioned above (about the source), you can simply extract the '''library''' archive and copy the files to your code directory, maintaining the same directory structure.

If instead you are interested in compiling these libraries from their source (instead of using the above zipfile of precompiled libraries provided by Linden Lab), see [[Compiling the viewer libraries (MSVS 2003)]]
 
 
== Other Libraries ==

Linden Lab included all the libraries/includes they can ship with their source, but we can not distribute the source to the following , and you will need to follow the instructions to acquire below.

However, it probably is 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 (like ''XCOPY olibs sl_1_16_0_5 /S''). The reason is, that these steps are cumbersome and will have to be repeated for each new release (at least if you keep the source for each release in it's own folder).

If you do not want to do this, of course you can just copy the files directly into the linden source paths.

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

==== Fmod ====
* Download & extract [http://www.fmod.org/index.php/download fmod 3.75 api for win32].
* Copy "fmodapi375win\api\inc\fmod.h" to "linden\libraries\include"
* Copy "fmodapi375win\api\inc\fmod_errors.h" to "linden\libraries\include"
* Copy "fmodapi375win\api\lib\fmodvc.lib" to "linden\libraries\i686-win32\lib_release"
* Copy "fmodapi375win\api\lib\fmodvc.lib" to "linden\libraries\i686-win32\lib_debug"
* Copy "fmodapi375win\api\fmod.dll" to "linden\indra\newview"

==== gl ====
* Download [http://oss.sgi.com/projects/ogl-sample/sdk.html glext.h, glxext.h, and wglext.h]
* Copy them to "linden\libraries\i686-win32\include\GL"

==== Quicktime (Optional) ====
* '''Note:''' Quicktime download can be skipped '''if you can live with a build that does not play in-world movies''' (some minor modifications to the project are necessary then, see "QuickTime removal" on the build instructions for [[Compiling the viewer (MSVS2005)|Visual Studio 2005]]).
* Download & install the [http://developer.apple.com/quicktime/download/ Quicktime SDK for Windows]
* Copy "QuicktimeSDK\Libraries\QTMLClient.lib" to "linden\libraries\i686-win32\lib_release".
* Copy "QuicktimeSDK\Libraries\QTMLClient.lib" to "linden\libraries\i686-win32\lib_debug".
* Copy the contents of "QuicktimeSDK\CIncludes" into "linden\libraries\i686-win32\include\quicktime".
 
 
== Building ==
* Open the '''indra\indra_complete\indra_complete.sln''' solution in Visual Studio (Note: If you plan to work with multiple versions over time, you will find it useful to rename '''indra_complete.sln''' to something which contains the version number, e.g. '''indra_1_17_0_11.sln''' before opening)
* Set newview to be the startup project.
* Build either '''ReleaseNoOpt''' (for debugging) or '''ReleaseForDownload''' (for running/debugging production code).
* Note that the ReleaseForDownload build also contains debug information and can be run in the debugger.
* newview_noopt.exe will be built in \indra\newview\ReleaseNoOpt, or SecondLife.exe will be built in \indra\newview\ReleaseForDownload
* To run it outside VS, create a shortcut to SecondLife.exe, and change the start location to linden\indra\newview\ (all the .dll will be found there.)
* Alternately copy the exe (possibly rename it) to your "c:\program files\second life" folder.
* There were additional steps required in version 1.15 which seem to be fixed now. If you are trying to build 1.15 see an [https://wiki.secondlife.com/w/index.php?title=Compiling_the_viewer_%28MSVS2003%29&oldid=23026 older version of this page].
 
 

== Errors while building? ==
See [[Common compilation problems]] if you run into errors while building.
 
 
 
== Configurations/Debugging Info ==
* You will usually compile/debug the '''ReleaseNoOpt''' or ReleaseForDownload configuration ('''Debug''' should also work but should not really be necessary).
* '''ReleaseNoOpt''' compiles faster and has more debugging information, but this comes at a runtime penalty of about 50% of your FPS in busy areas, compared to ReleaseForDownload build.
* '''ReleaseForDownload''' runs fine in the debugger, but times you may miss debugger access to some local variables or the debugger may even show wrong values for objects and members, because it is confused by the optimizations.
* '''ReleaseNoOpt''' comes with a seperate debugging console window opens and stays open for the duration of your session.
* You can see the last few lines from the debugger console also by pressing Shift+Ctrl+4 in the viewer (all builds).
* The debug log (usually in application data) can also be redirected to a more file if you add "-log secondlife.log" to the command line (Newview, Properties, Debugging, Command line arguments).
* If you want to build a '''Debug''' configuration, see the specific section with compile instructions on [[Finding_leaks]]
 
 
== Problems Running? ==
* Viewer Error: '''Second Life is unable to access a file that it needs.''': Did you neglect to download the Artworks archive from the [[source downloads]] page? It is in the Viewer column, below the OS-specific Viewer archives.
* '''Can't connect''': In the debug builds there is a selection box on the login screen to select the server to connect to. '''Agni''' is the production grid, '''aditi''' is the beta grid. (There seems to be a bug in this part of the code, you may have to make your selection, close the viewer and repoen it, before you can connect to the selected grid).
* '''Inventory errors''': If you're getting errors while trying to load your inventory, try [[Help:Stuck logging in|clearing your cache and deleting other temporary files]].
* If you want to connect to the beta grid, add '''--aditi''' to the command line (Newview, Properties, Debugging, Command line argument).
* '''Missing smime3 DLL''': Those are parts of the integrated web browser. Copy 'smime3.dll', 'nss3.dll', 'softokn3.dll', and 'ssl3.dll' files from your official client's main folder to "linden\indra\newview".
 
 

== Submit Patches ==
This is probably far down the road, but if you make changes to the source and want to submit them, see the page about [[Submitting patches|submitting patches]].

Compiling the viewer (Mac OS X)

2007-09-25T11:06:18Z

Nicholaz Beresford: adding links to barney's tips

{{CompileNav}}

The following are instructions for building the Second Life viewer on Mac OS X. For other platforms, see [[Compiling the viewer]]

You will also need to check the '''Build Notes''' column of the table on [[source downloads]] page.

= Development Environment =

Lindens use XCode 2.4.1 for building on Macintosh computers. For simplicity, we suggest installing everything from the mpkg.

You will need to install the proprietary libraries as well as all of the other third party libraries below.
 
 
= Installing Files =

== Viewer Source, Libraries, and Artwork ==

The required source code, pre-compiled third-party libraries, and artwork files are available from the [[source downloads]] page. Download the Mac/Linux (LF) source, the Mac library package, and the Artwork zip file.

Unpack them into a single directory. The directory that you work in should should have no spaces in the name. For example, from the directory where you downloaded the tarballs (x.x.x.x = version number, e.g., 1.14.0.1.):

$ tar xvfz slviewer-src-x.x.x.x.tar.gz
$ tar xvfz slviewer-darwin-libs-x.x.x.x.tar.gz
$ unzip slviewer-artwork-x.x.x.x.zip

If you have Stuffit installed on your system, it may automacially unstuff .gz, so use tar xvf, without the z to extract the tar file. It may also automatically unzip files. Instead of clicking on the file link, right click on the file link and select Download Linked File which will keep .gz and .zip intact.

The exact filenames will differ with the version number. If you open them with the double click file extract, remember that dragging folders on top of each other will overwrite the original contents, not merge them as in Windows.

Check the [[source downloads]] page for any special Build Notes associated with the viewer version, if any.

== Installing Libraries From Scratch (Optional) ==

For convenience, Lindens package up the libraries they are allowed to distribute so you can download and unpack them into your development working directory. The [[#Viewer Source, Libraries, and Artwork|above procedure]] installs pre-compiled third-party library files. Alternatively, if you want to build the libraries yourself, See [[Compiling the viewer libraries (Mac OS X)|another page]].

== Installing Proprietary Libraries ==

The Viewer depends on some proprietary libraries. Lindens do not distribute these libraries, so you will need to fetch and install these even if you download the libraries packages. (This is due to licensing restrictions. Don't ask, Lindens already did, and can't get permission. So you do have to get them yourself.)

=== Fmod ===
* Download & extract [http://www.fmod.org/index.php/download fmod 3.75 programmers api for macintosh].
* (You do *not* want the latest version, instead scroll down to v3.75)
* Copy the extracted files. ''Note the name change for the x86 library.''

$ cp -p fmodapi375mac/api/inc/*.h linden/libraries/include
$ cp -p fmodapi375mac/api/lib/libfmod.a linden/libraries/powerpc-darwin/lib_debug
$ cp -p fmodapi375mac/api/lib/libfmod.a linden/libraries/powerpc-darwin/lib_release
$ cp -p fmodapi375mac/api/lib/libfmodx86.a linden/libraries/i386-darwin/lib_debug/libfmod.a
$ cp -p fmodapi375mac/api/lib/libfmodx86.a linden/libraries/i386-darwin/lib_release/libfmod.a

 
 
= Building the Viewer =
Launch XCode, open the project file 'linden/indra/newview/macview.xcodeproj',

set 'libraries' as the active target, select an active build configuration, build the libraries. After that:
set 'newview' as the active target, select an active build configuration, and build the project.

If you had to change gcc versions for a ppc build, restore gcc back to 4.0.

$ sudo gcc_select 4.0

== Build Configurations ==

; Development : This configuration is more suitable for debugging. The build process will create the SecondLife application targeted for your host architecture.
; Deployment : This configuration is faster than the development version at the cost of some ability to debug. The build process will create the SecondLife application targeted for your host architecture.
; Universal : This configuration is the same as the Deployment target except that all supported architectures - ppc and i386 - are built.

== Post Build Steps ==
To deal with some quirks after building see [http://radio-boomslang.shacknet.nu/~bb/archives/2007/09/16/index.html#e2007-09-16T19_05_06.txt Barney Boomslang post build tips] (not everything there may apply to you, but worth checking)

 
 
= Building the Unit Tests =
From XCode, open the project 'linden/indra/test/MacTester.xcodeproj', set 'MacTester' as the active target, and build.

 
 
= Submitting Patches =
This is probably far down the road, but if you make changes to the source and want to submit them, see the page about [[Submitting patches|submitting patches]].

Converting project files for MSVS2005

2007-09-10T12:09:42Z

Nicholaz Beresford: more polishing

{{CompileNav}}

= Manual conversion of the VS2003 solution/projects =
This page describes the steps necessary to fully convert Linden Labs solution and project files from VS2003 to VS2005.

There are canned sets of these available on the [https://jira.secondlife.com/browse/VWR-1151 JIRA bug tracker issue VWR-1151], so downloading these may save you the work described below.

== Global steps ==

* Start Visual Studio 2005 (or VC++ Express).
* Use "File > Open > Project/Solution" to open the linden\indra\indra_complete\indra_complete.sln
* Visual Studio prompts to update your project files. Allow it to do so. When the results are displayed, you may see warnings, but you should not see any errors.
* Right click '''newview''' in the frame Solution Explorer and click "Set as StartUp Project".
* From the Visual Studio menu bar, choose "File > New > File...". On the "New Fille" dialog box, choose "General", then "Text File". Select the following lines on your browser, copy them, and paste them to the empty file you just created. Save it as a file of the name "SL-UpgradeFromVC71_vc8.vsprops" under the foler "indra_complete" (where the "indra_complete.sln" file resides.)

<?xml version="1.0"?>
<VisualStudioPropertySheet
ProjectType="Visual C++"
Version="8.00"
Name="Upgrade From VC 7.1">
<Tool
Name="VCCLCompilerTool"
PreprocessorDefinitions="_VC80_UPGRADE=0x0710;_CRT_SECURE_NO_DEPRECATE;_CRT_NONSTDC_NO_DEPRECATE;_USE_32BIT_TIME_T;_SECURE_SCL=0"
TreatWChar_tAsBuiltInType="false"
/>
<Tool
Name="VCResourceCompilerTool"
PreprocessorDefinitions="_VC80_UPGRADE=0x0710;_CRT_SECURE_NO_DEPRECATE;_CRT_NONSTDC_NO_DEPRECATE;_USE_32BIT_TIME_T;_SECURE_SCL=0"
/>
</VisualStudioPropertySheet>

 

== All Configuration Steps ==
#Select all projects, i.e., llaudio, llcharacter, ..., win_updater, '''except''' for lscript_compile_fb and test. (You can do it by control-clicking on the projects.)
# Right click on the selection and choose Properties.
# A window named Property Pages opens. There single left-click (select) '''Configuration Properties''' in the tree on the left of the window.
# In the upper left corner of Property Pages choose '''All Configurations''' from the Configuration drop down box.
# Now, in the tree select '''Configuration Properties > General''' and change '''Inherited Project Property Sheets''' and set it to '''$(SolutionDir)\SL-UpgradeFromVC71_vc8.vsprops'''.
# Under the '''Configuration Properties > C/C++ > General''', change '''Treat Warnings As Errors''' to "'''No'''". ([[:Image:MSVS2005_Project_Property_Pages_Config_CPP_General.JPG|'''screen shot''']]).
# Under the '''Configuration Properties > C/C++ > Language''', change (if necessary) '''Treat wchar_t as Build-in Type''' to "'''No (/Zc:wchar_t-)'''" ([[:Image:MSVS2005 Project Property Pages Config CPP Language.JPG|'''screen shot''']]).
# Under the '''Configuration Properties > C/C++ > Advanced''', change (if necessary) '''Use Full Paths''' to "'''Yes (/FC)'''" ([[:Image:MSVS2005 Project Property Pages Config CPP Advanced.JPG|'''screen shot''']]).
# Click OK for the dialog.
 

== Per Configuration Steps ==
* Pick '''ReleaseNoOpt''' in the Solution Configurations drop-down box next to the green arrow under the tool bar, and do the followings on the Solution Explorer frame (on left side of the VS2005 window):
*#Left-click '''newview''' to select it alone.
*#* Right-click '''newview''', choose Properties.
*#*Under '''Configuration Properties > Linker > Input''', click '''Additional Dependencies''' on the right to show a button labeled "'''...'''" on it at the very right on the line, then click the '''...''' button.
*#*Scroll down the list to find '''libboost_regex-vc71-mt-s.lib'''. Rewrite it to libboost_regex-vc'''80'''-mt-s.lib.
*#*Scroll down again to find '''llmozlib.lib''' and rewrite it to llmozlib'''-vc80'''.lib.
*#*Click '''OK''' to close the "Additional Dependencies" dialog, then click OK again to close the "newview Property Pages" dialog box.
* Pick '''ReleaseForDownload''' in the Solution Configurations drop-down box (in the toolbar, next to the green arrow). Repeat the same steps (as for ReleaseNoOpt above) again.
* Depending on what you want to do later (or if you want to do a full and complete conversion), you may also need to perform these steps for the Debug and Release configurations, but for a start it is safe to skip these.
 

== Optional steps ==
The following steps are not strictly necessary, unless you want a full and ultra clean conversion (e.g. for sharing with others). These instructions are telegram style, assuming you will do this only after you have aquainted yourselves with the project
* In the Configuration manager (Build menu):
** unclick the build column for '''test''', '''win_crash_logger''' and '''win_updater''' in all configurations '''except ReleaseForDownload'''.
** unclick the build column for '''test''' in '''ReleaseForDownload'''
* For all configurations: In newview, properties, linker input: If you find libraries starting with 'll' (e.g. '''llaudio.lib''', '''llcharacter.lib''', etc.) or find the library '''lscript_library.lib'''), remove them from the list (these libraries are linked through the dependency)
* For all configurations: In newview, properties, linker input: Set '''Ignore Specific Library''' to '''msvcrt.lib;msvcrtd.lib;libc.lib;libcd.lib;'''
* In the Debug configuration, under lscript_compile_fb, indra.y, properties, custom build step, general, command line, make sure you have ''C:\cygwin\bin\mv.exe ytab.hpp ytab.h'' (use the command line from the release configuration as reference).
* In the Debug configuration, also add '''libcmt.lib;''' to the list of specific libraries to ignore.
* In all configurations: the libraries need to be changed from vc71 to vc80 (boost, llmozlib) for the '''test''' project as well, but since '''test''' does not seem to work under VC2005 so far, it's optional.

== Done :-) ==
Congratulations! You've converted ''solution file'' and ''project files''.

'''NOTE:''' You need to do this by hand everytime a new viewer version is released...

Converting project files for MSVS2005

2007-09-10T11:52:49Z

Nicholaz Beresford: some minor clarifications

{{CompileNav}}

= Manual conversion of the VS2003 solution/projects =
This page describes the steps necessary to fully convert Linden Labs solution and project files from VS2003 to VS2005.

There are canned sets of these available on the [https://jira.secondlife.com/browse/VWR-1151 JIRA bug tracker issue VWR-1151], so downloading these may save you the work described below.

== Global steps ==

* Start Visual Studio 2005 (or VC++ Express).
* Use "File > Open > Project/Solution" to open the linden\indra\indra_complete\indra_complete.sln
* Visual Studio prompts to update your project files. Allow it to do so. When the results are displayed, you may see warnings, but you should not see any errors.
* Right click '''newview''' in the frame Solution Explorer and click "Set as StartUp Project".
* From the Visual Studio menu bar, choose "File > New > File...". On the "New Fille" dialog box, choose "General", then "Text File". Select the following lines on your browser, copy them, and paste them to the empty file you just created. Save it as a file of the name "SL-UpgradeFromVC71_vc8.vsprops" under the foler "indra_complete" (where the "indra_complete.sln" file resides.)

<?xml version="1.0"?>
<VisualStudioPropertySheet
ProjectType="Visual C++"
Version="8.00"
Name="Upgrade From VC 7.1">
<Tool
Name="VCCLCompilerTool"
PreprocessorDefinitions="_VC80_UPGRADE=0x0710;_CRT_SECURE_NO_DEPRECATE;_CRT_NONSTDC_NO_DEPRECATE;_USE_32BIT_TIME_T;_SECURE_SCL=0"
TreatWChar_tAsBuiltInType="false"
/>
<Tool
Name="VCResourceCompilerTool"
PreprocessorDefinitions="_VC80_UPGRADE=0x0710;_CRT_SECURE_NO_DEPRECATE;_CRT_NONSTDC_NO_DEPRECATE;_USE_32BIT_TIME_T;_SECURE_SCL=0"
/>
</VisualStudioPropertySheet>

 

== All Configuration Steps ==
#Select all projects, i.e., llaudio, llcharacter, ..., win_updater, '''except''' for lscript_compile_fb and test. (You can do it by control-clicking on the projects.)
# Right click on the selection and choose Properties.
# A window named Property Pages opens. There single left-click (select) '''Configuration Properties''' in the tree on the left of the window.
# In the upper left corner of Property Pages choose '''All Configurations''' from the Configuration drop down box.
# Now, in the tree select '''Configuration Properties > General''' and change '''Inherited Project Property Sheets''' and set it to '''$(SolutionDir)\SL-UpgradeFromVC71_vc8.vsprops'''.
# Under the '''Configuration Properties > C/C++ > General''', change '''Treat Warnings As Errors''' to "'''No'''". ([[:Image:MSVS2005_Project_Property_Pages_Config_CPP_General.JPG|'''screen shot''']]).
# Under the ''Configuration Properties > C/C++ > Language''', change (if necessary) '''Treat wchar_t as Build-in Type''' to "'''No (/Zc:wchar_t-)'''" ([[:Image:MSVS2005 Project Property Pages Config CPP Language.JPG|'''screen shot''']]).
# Under the '''Configuration Properties > C/C++ > Advanced''', change (if necessary) '''Use Full Paths''' to "'''Yes (/FC)'''" ([[:Image:MSVS2005 Project Property Pages Config CPP Advanced.JPG|'''screen shot''']]).
# Click OK for the dialog.
 

== Per Configuration Steps ==
* Pick '''ReleaseNoOpt''' in the Solution Configurations drop-down box beside the green arrow under the tool bar, and do the followings on the Solution Explorer frame (on left side of the VS2005 window):
*#Click '''newview''' to select it alone.
*#* Right-click '''newview''', choose Properties.
*#*Under Configuration Properties > Linker > Input, click '''Additional Dependencies''' on the right to show a button labeled "'''...'''" on it at the very right on the line, then click the '''...''' button.
*#*Scroll down the list to find '''libboost_regex-vc71-mt-s.lib'''. Rewrite it to libboost_regex-vc'''80'''-mt-s.lib.
*#*Scroll down again to find '''llmozlib.lib''' and rewrite it to llmozlib'''-vc80'''.lib.
*#*Click '''OK''' to close the "Additional Dependencies" dialog, then click OK again to close the "newview Property Pages" dialog box.
* Pick '''ReleaseForDownload''' in the Solution Configurations drop-down box. Do the same thing (as 1 to 7 above) again. Depending on what you want to do later (or if you want to do a full and complete conversion, you will also need to do it for Debug and Release).
 

== Optional steps ==
The following steps are not strictly necessary, unless you want a full and ultra clean conversion (e.g. for sharing with others). These instructions are telegram style, assuming you will do this only after you have aquainted yourselves with the project
* In the Configuration manager:
** unclick '''test''', '''win_crash_logger''' and '''win_updater''' for all configurations except '''ReleaseForDownload'''.
** unclick '''test''' for '''ReleaseForDownload'''
* For all configurations: In newview, properties, linker input: If you find libraries starting with 'll' (e.g. '''llaudio.lib''', '''llcharacter.lib''', etc.) or find the library '''lscript_library.lib'''), remove them from the list (these libraries are linked through the dependancy)
* For all configurations: In newview, properties, linker input: Set '''Ignore Specific Library''' to '''msvcrt.lib;msvcrtd.lib;libc.lib;libcd.lib;'''
* In the Debug configuration, under lscript_compile_fb, indra.y, properties, custom build step, general, command line, make sure you have ''C:\cygwin\bin\mv.exe ytab.hpp ytab.h'' (use the command line from the release configuration as reference).
* In the Debug configuration, also add '''libcmt.lib;''' to the list of specific libraries to ignore.
* In all configurations: the libraries need to be changed from vc71 to vc80 (boost, llmozlib) for the '''test''' project as well, but since '''test''' does not seem to work under VC2005 so far, it's optional.

== Done :-) ==
Congratulations! You've converted ''solution file'' and ''project files''.

'''NOTE:''' You need to do this by hand everytime a new viewer version is released...

Open Source Meeting/2007-10-18

2007-08-30T14:32:28Z

Nicholaz Beresford: Peeking inside the Black Box

< [[Open Source Meeting]]

Open source meeting - Thursday, 2pm PT

* Your agenda items go here - just click "Edit" :)
* If there's nothing else, I'll take a stab at it. Low priority and I may be a bit late (2PM is a bit borderline today), so feel free to raise other issues if I'm not there or more important issues even if I'm there. [[User:Nicholaz Beresford|Nicholaz]]

Agenda:
* Peeking into the black box: Q/A about the Linden workflow, priorities, etc. [[User:Nicholaz Beresford|Nicholaz]] 07:32, 30 August 2007 (PDT)

Alternate viewers

2007-08-30T14:23:03Z

Nicholaz Beresford: alphabetical order of entries

Talk:User Interface Improvements

2007-08-18T13:48:38Z

Nicholaz Beresford: /* Advantages of the current UI */

{{Talk}}

== Problems with current UI (moved from main page) ==

(These are just gathered from comments on the forums, and ones I've heard from helping new users) -- {{unsigned|Benjamin Linden}}

* User interface is rendered as part of the standard frame render cycle. Thus it does not use recognisable OS-standard components and lags whenever the sim does. Could seperate this to use a general platform-independant kit (wxWidgets?) - although a lot of work!

* Users confused by a plethora of options that aren't related to their current situation. A user with no interest in content creation still has to deal with a huge number of related options on the pull-down menus. "Build" button on bottom toolbar is the only thing there related to building.

* Too many valuable items are on the client debug menu. I've seen several Live Help calls in which users are sent to these menus! If they are needed for solving technical problems encountered by regular users, they shouldn't really be part of an "easter egg".

* Mac OX X complaint: Mac OS X implements right-clicking with Control-click. The Mac OS X SL client implements right-clicking with cmd-click.

== Advantages of the current UI ==
* User interface is rendered as part of the standard frame render cycle. This allows for innovative gui components not present in the OS such as the pie menu, which is much easier to navigate than OS-standard context menus. This should be leveraged to design gui components for a virtual world, rather than going backwards with 2d OS controls [[User:Kaworu Jun|Kaworu Jun]] 13:30, 15 August 2007 (PDT)
::That is a disadvantage as well. On the Mac, at least, lag in the viewer makes the UI completely unusable at times. In fact, it seems to make the UI of the rest of the Mac unusable as well. 15:51, 15 August 2007 (PDT)
* Current user interface is easier to deal with for building than a more videogame-like interface would be, since elements like editing and inventory windows can be freely moved, duplicated, and resized. On the other hand, since these *are* windows, many of these UI elements could be rendered in the native GUI toolkit in separate OS-level windows rather than in the UI. which would allow them to be positioned around the SL window in multi-window mode. [[User:Argent Stonecutter|Argent Stonecutter]] 18:38, 15 August 2007 (PDT)
* Current user interface is largely consistent, though this has wavered at times. Designing a new consistent UI is likely to lead to more of the kinds of problems that have caused so much protest over the past year. [[User:Argent Stonecutter|Argent Stonecutter]] 18:38, 15 August 2007 (PDT)
* One of the major advantages of the current UI is immersion. The UI has been tailored to the needs of a virtual experience. There are innovative things like the pie menus, the UI interface is usually designed to be visually lean (slim window titles, slim tabs, etc. ... for example a window title is about half has high as a standard Windows window title). [[User:Nicholaz Beresford|Nicholaz]] 06:48, 18 August 2007 (PDT)
* On an intuitive level, it generates a separation between out of world and in world. Having OS dialogs float on top of the window or even outside the window, especially for operations which are related to in-world, would have the tendency to reduce the experience to a mere animated wallpaper for a fancy chat client. (The only dialog where I could imagine an UI dialog are preferences, because these happen on a meta-level anyway). [[User:Nicholaz Beresford|Nicholaz]] 06:48, 18 August 2007 (PDT)
* Another benefit is that it leads to a consistent experience across platforms. [[User:Nicholaz Beresford|Nicholaz]] 06:48, 18 August 2007 (PDT)
* Yet another benefit is that window clipping leads to performance reduction. Simply run a windowed viewer and watch the FPS by partially covering it with native windows. [[User:Nicholaz Beresford|Nicholaz]] 06:48, 18 August 2007 (PDT)

== Considerations for the proposed UI ==
* Many of the existing floaters, particularly the building ones, should not be radically changed other than possibly making them first class OS level windows. Don't abandon the parts of the user interface that currently work. [[User:Argent Stonecutter|Argent Stonecutter]] 08:13, 16 August 2007 (PDT)
* Users are generally used to Menus so removing the Menu entirely may not be recommended given that it may not be possible to reproduce all the functionality there. However a better reorganisation of the menu, and possibly having the menu contextual and hidable would improve things. May even take some ideas from the MS Office Ribbon bar. {{User|Matthew Dowd}}
:: I was with you up to the point of the ribbon bar. Having a universal menu that contains all options and operations should not be discarded... particularly not in the name of making things easier for new users. [[User:Argent Stonecutter|Argent Stonecutter]] 18:48, 15 August 2007 (PDT)
:* Alternate possibility, keep and expand the pie menu, so that right click (or whatever click or key combination the user selects for menus) brings up a menu (pie, pacman, etc) that includes every option in the menu bar. [[User:Argent Stonecutter|Argent Stonecutter]] 08:09, 16 August 2007 (PDT)
:* Alternate possibility, sweeping the mouse above the top of the screen drops a menu bar down.
* The idea of regions needs careful thought - users could get annoyed if they go to click on something in world which is in a corner of the viewer only for a part of the UI to suddently popup in the way! {{User|Matthew Dowd}}
:: Agreed, you should probably have to click on an actual docked icon to open the element. The Mac dock is visually appealing, but restricted... perhaps make the docked objects recognizably 3d icons, but draggable anywhere around the edges of the screen that you want, so that when you click on them they pop in or up or down. [[User:Argent Stonecutter|Argent Stonecutter]] 18:48, 15 August 2007 (PDT)
* Consideration of how these regions would interact with HUD's attached to that position in the viewer needs careful thought to avoid the UI interfering with existing (and future) HUDs. {{User|Matthew Dowd}}
** Making the HUD anchor points (or new ones... say "Dock 1", "Dock 2", ...) dockable and draggable, with the same show/hide behavior, would help a lot. [[User:Argent Stonecutter|Argent Stonecutter]] 18:48, 15 August 2007 (PDT)
* The ability to dock floaters/regions in os-native windows that can be placed on another monitor would unclutter the view while keeping that information visible (and will not cover the view while they are in use!). [[User:Kaworu Jun|Kaworu Jun]] 13:30, 15 August 2007 (PDT)

== GUI and (eventually) client scripting ==

Whatever design we come up with, ease-of-scripting (or at least the ability to script at all), should be part of the design-parameters.

As I've mentioned before, the WoW client paradigm would be a good one to examine and emulate--at least the overall concept of making virtually everything in the GUI scriptable.
http://www.wowwiki.com/Widget_API
http://www.wowwiki.com/World_of_Warcraft_API

[[User:Saijanai Kuhn|Saijanai]] 15:08, 15 August 2007 (PDT)

Largely agree, and the scripting language should probably be Javascript using the Spidermonkey component in Gecko, since it can be run independently of the HTML browser and is already in there. [[User:Argent Stonecutter|Argent Stonecutter]] 18:50, 15 August 2007 (PDT)
:The wave of the future is apparently mono, even on the client side. This could allow extremely powerful hybrid in-world/external tools to be devised. {{Saijanai Kuhn} [[User:Saijanai Kuhn|Saijanai]] 18:02, 16 August 2007 (PDT)

=== Interaction between in-world and out-of-world scripting ===
To avoid hitting people with too many changes at once, we should look at what changes in the communications between the client and server would make things easier and to allow maximum compatibility with existing content.

* Allowing objects on the client to register listens in the game, so that you can have gui components do things like respond to high channel chat from scripts, should be possible.
::Whether the chat comes in as a simple line or encapsulated in XML or whatever is less critical.
::This could be tested in the existing client by allowing applications outside the client to connect to a socket and hook into chat. Connect to localhost:1337 and send "<listen channel=42/> <send channel=42>flight status</send>" would lead to getting messages like "<chat source=UUID channel=42>flight enable</chat>".
:: [[User:Argent Stonecutter|Argent Stonecutter]] 08:19, 16 August 2007 (PDT)
::::IN the long run, this would allow for external tools to act like in-world tools. If a tool allows you to keep chatting with friends, or ask/answer questions in IM, it becomes at least somewhat part of hte game. 17:58, 16 August 2007 (PDT)

* Allow HUDs to evoke widgets on the client side sot that a HUD could define sliders, dials and other interesting objects where the client's GUI does the mouse-tracking and other GUI updating, and sends the updated info to the HUD for further processing. [[User:Saijanai Kuhn|Saijanai]] 15:24, 17 August 2007 (PDT)

Finding leaks

2007-08-16T17:03:17Z

Nicholaz Beresford:

{{OSWikiContribBox}}

= Overview =

This page describes a method how to identify memory leaks within the SecondLife viewer using Microsoft's debug memory routines.

'''Note:''' If you have questions, please use the discussion page on this wiki topic. ([[User:Nicholaz Beresford|Nicholaz]] 10:29, 29 June 2007 (PDT))

 
 

= Identifying Leaks =
 
== Modifying the source ==
Download the memory leak patch from [http://www.blueflash.cc/users/nicholaz/~libs/leakdebug.patch leakdebug.patch] and apply it to the source tree via
* in a command shell go to the source directory on the level where you see the 'linden' folder when you type ''dir''
* '''c:\cygwin\bin\patch -p 0 -i leakdebug.patch'''
 

== Compiling ==

For general compiling instructions, see [[Compiling the viewer (MSVS2003)|Microsoft Windows - Visual Studio .NET 2003]] or [[Compiling the viewer (MSVS2005)|Microsoft Windows - Visual Studio 2005 & Visual C++ 2005 Express]].

The patch activates the leak debugging routines through the '''linden_common.h''' files and is only activated in the '''Debug''' configuration. It should be completely transparent in other configurations like ReleaseNoOpt or ReleaseForDownload.

When compiling, make sure you compile all projects with the /MTd flag
* Set all projects to /MTd
*# select the '''Debug''' configuration from the toolbar
*# mark all projects in the source tree, '''except''' script_compile_fb, test, win_crash_logger and win_updater
*# select Properties and make sure the '''Debug''' configuration is selected in the upper left corner
*# select C/C++ > Language and set Runtime Library to '''Multithreaded Debug /MTd'''
*# close the dialog

* Add crtdebug.cpp to newview
*# in the source tree under newview right click Source, add existing
*# crtdebug.cpp

* Linker options for newview
*# select '''newview''' alone
*# select Properties and make sure the '''Debug''' configuration is selected in the upper left corner
*# select Linker > Input and set Ignore Specific Library to '''msvcrt.lib;msvcrtd.lib;libc.lib;libcd.lib;libcmt.lib'''
*# close the dialog

* Remove LLMOZLIB (optional for VS2003, required for VS2005)
*# select '''newview''' alone
*# select Properties and make sure the '''Debug''' configuration is selected in the upper left corner
*# select Linker > Input
*# remove '''llmozlib-vc80.lib''' from the list of input libraries
*# close the dialog
*# edit '''llpreprocessor.h''' in the '''llcommon''' project and change
#define LL_LIBXUL_ENABLED 1 (line 59)
to
#ifndef _DEBUG
#define LL_LIBXUL_ENABLED 1
#else
#define LL_LIBXUL_ENABLED 0
#endif

* Compile
*# select compile for the Debug configuration
*# have some coffee and/or cigarettes, the build (especially the link step) is excruciatingly slow
 

== Running ==
* Run the program under the debugger (F5) or standalone (Ctrl+F5)
* Running in the debugger during startup you will notice a couple of exceptions when freeing memory. Just continue (these seem to come from the mozilla DLLs).
* If you encounter crashAndLoop situations (when you hit these, you'll know what it means), consider to delete the contents from the crashAndLoop function and replace it with a single '''__asm int 3;''' command. This way the debugger will stop with an exception but you will be able to continue.
* Finish running the program
* Look at the '''leaks.log''' file in the program folder.

 
== Identifying the source of the leak through leaks.log ==
Finding leaks is a nice task. Like post mortem debugging in many cases it is puzzle and detective work and the leaks.log file is your forensic evidence.
* '''client blocks''' were allocated through '''new''' operations inside the source. Source file and line number will be identified and usually it is not too hard to figure out a program path that bypasses the deletion.
* '''normal memory blocks''' in the leak dump are coming from 3rd party libraries. You'll need creativity to find these (I do it mostly through custom code in '''crt_alloc_hook''' in crtdebug.cpp ... see the example there).
* currently there is a small amount of "unfixable" leaks as normal blocks when the program starts.
** one is from a technique the Lindens are using in llerror.cpp (see [[https://jira.secondlife.com/browse/VWR-849 VWR-849]]), which Zero Linden does not want to fix, although I have a patch which I deem safe
** another is from code in llmozlib which I could not compile yet (these can be avoided by compiling without mozlib, see compile instructions above)
** I have also found a few that seem to trace down into fmod.lib, but fmod doesn't seem like the cleanest code on the planet anyway.
** unless you want to be religious about the issue, you can ignore normal blocks with alloc numbers under 1,000,000

Compiling the viewer (MSVS2005)

2007-08-03T09:26:44Z

Nicholaz Beresford:

{{CompileNav}}

This page explains how you can compile the viewer on Microsoft Windows using Visual Studio 2005 or Visual C++ Express 2005. Note that Lindens are using VS2003 and the whole setup is a bit easier there, so if you have Visual Studio 2003 available, you should read [[Compiling the viewer (MSVS2003)|compiling with VS2003]] and you will get less trouble with it than with VS2005.

The following explanation is adjusted for Viewer releases 1.16.0.5 or later. See an [http://wiki.secondlife.com/w/index.php?title=Compiling_the_viewer_%28MSVS2005%29&oldid=22294 older version of this page] for the Viewer releases 1.15 or before.

= Preparing the Development Environment =

== Installing/Configuring VS2005 ==

You need to setup the compiler and Microsoft Development tools as follows:
* Visual Studio 2005 '''''-or-''''' [http://msdn.microsoft.com/vstudio/express/visualc/download/ Visual C++ 2005 Express](Free) (Also, although not strictly necessary, eventually pick up and install SP1 for VS2005.)
* [http://www.microsoft.com/downloads/details.aspx?familyid=0BAF2B35-C656-4969-ACE8-E4C0C0716ADB&displaylang=en Microsoft Platform SDK]
* A DirectX 9.0 SDK released on or after Summer of 2003 [http://download.microsoft.com/download/5/1/f/51ff8357-0af3-418b-9d0b-e9a5cdc39759/dxsdk_dec2006.EXE DirectX 9.0 SDK (December 2006)] [http://www.microsoft.com/downloads/details.aspx?FamilyID=9216652f-51e0-402e-b7b5-feb68d00f298&displaylang=en DirectX 9.0 SDK Update (Summer 2003)]
: '''Note''': If you have previously installed an older version of the DirectX 9.0 SDK, remove it first (from Control Panel -> Add or Remove Programs) before installing this version. Installing the new SDK "on top" of an older version may cause problems.
* Set up the project globals:
** Start Microsoft Visual Studio 2005
** Go to Tools > Options > Projects > VC++ Directories
** Make sure that the '''includes''' ([[:Image:MSVS2005 Global Project Options Include Files.JPG|'''screen shot''']]) and '''libraries''' ([[:Image:MSVS2005 Global Project Options Library Files.JPG|'''screen shot''']]) paths have the Platform SDK paths first, then the DirectX SDK paths, and then the Visual C++ paths. You may need to check "Show All Settings" at the bottom for VC++ Directories to show.
** If the DirectX SDK paths aren't present, add them to both '''includes''' and '''libraries'''.
*: Note: The newest DirectX SDK ("December 2006") lib folder has two sub-folders, x64 and x86. Make sure your path goes to one of them (select '''lib/x86''', not just '''lib'''), or you will get a Link error.
 

== Getting other Development Tools ==
You will also need some open source development tools.
* [http://www.cygwin.com/ 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. The project files use several hardcoded references that expect Cygwin to be installed at '''C:\cygwin''', if it's not you'll need to edit those references.
* [http://www.activestate.com/Products/ActivePython/?mp=1 ActivePython 2.3x or later] - Latest Version is 2.5.1.1
** It is required but can be avoided if you are compiling 1.18 or later viewers. Either download and install or hack the prebuild.bat files as described in [http://jira.secondlife.com/browse/VWR-1267 VWR-1267].
* ActivePerl was recommended for previous versions on this Wiki, but it currently appears, that it is not strictly necessary unless you are planning to build your own version of all libraries (which most likely you don't want to do). So for a start it may be safe to skip it.
*: [http://www.activestate.com/Products/ActivePerl/?mp=1 ActivePerl]

 
 
 
= Downloading Source Code =

You can download the Viewer source codes on the [[source downloads]] page. You can also use a [[version control repository]].

At a minimum, grab the source package and the artwork package, but for a start, also grab the library archive. Many of the libraries can either be compiled from source or downloaded from other sites (see below), but this will take hours and thus it is easiest to also get the package with libraries compiled by the Lindens.

'''WARNING:'''
* If the directory path you keep the SL source in has a space in it, the batch file that copies message_template.msg will fail. So, if you unzip or checkout the source tree into, e.g., "C:\Projects\Dir with space in name\Etc\linden", it won't work!
* You should also avoid using non-ASCII (national) characters in the paths, although some localized versions of the tool puts some as a default...
* Unzip or checkout your source tree into a directory that has as short full pathname as possible, since long paths cause some unexpected trouble during the build.

In other words, the easiest way to get this working is to get ''source'', ''artwork'' and ''libraries'' from the [[source downloads]] page and unpack them all into the same directory/folder, which ideally would be a folder in (or near) the root directory with a short name like ''sl_1_16_0_5''.
 
 
 
 

= Installing Libraries =

SL Viewer depends on some third party libraries. Some of them are open source, some others are not.

== Open Source Libraries ==

You can download the pre-build open source libraries from LL. They are available on [[source downloads]] page. Unzip them into your SL viewer source code directory, maintaining the same directory structure.

'''Note:''' The VS2003 libraries provided in the [[source downloads]] do not fully work with VS2005 compiled binaries. They will compile with the viewer under VS2005, but the VS2003 libraries are not fully STL compliant. The differences of [http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vclang/html/vclrfnonstandardbehavior.asp non-standard behavior in MSVS] are the known cause. This may lead to subtle issues, especially if want to make a release other than for yourself, but on the other hand so far many have successfully used the precompiled libraries which are provided by Linden Lab.

Alternatively, it may be possible to get the source files for the libraries and build by yourself. See [[Compiling the viewer libraries (MSVS 2003)|the instruction for VS2003 users]] if you try it. Please note, however, it is not known that VS2005 can successfully compile the libraries. '''You have been warned.''' (If you can make it, please write the info on this wiki...)
 
 

== Proprietary Libraries ==

Lindens does not inlcude the following proprietary libraries. You will need to follow the instructions to acquire below and copy them to the source path.

However, it probably is 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 (like ''XCOPY OLIB SL_1_16_0_5 /S''). The reason is, that these steps are cumbersome and will have to be repeated for each new release (at least if you keep the source for each release in it's own folder). If you do not want to do this, of course you can just copy the files directly into the linden source paths.

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
 
=== Fmod ===
* Download & extract [http://www.fmod.org/ifmoddownload.html fmod 3.75 api for win32] (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\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"
 
=== OpenGL ===
* Download [http://oss.sgi.com/projects/ogl-sample/sdk.html glext.h, glxext.h, and wglext.h]
* Copy them to "linden\libraries\i686-win32\include\GL"
* You don't need any additional *.lib or *.dll for OpenGL.
 
=== Quicktime ''(optional)'' ===
'''Note:''' This download requires a registration at the Apple Quicktime website and take a bit of time. You can avoid using QuickTime if you want, bee [[#QuickTime removal|below]] for details. Remember that your viewer '''can't play in-world movies''' if you do so.
* Download & install the [http://connect.apple.com/cgi-bin/WebObjects/MemberSite.woa/203/wa/getSoftware?fileID=20525&code=y&source=x&wosid=4h16WcyMtVfd2P1EffGafkoxFcr 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".
 
 
 
= Configuring for VS2005 =

Lindens use VS2003 to develop the viewer.

You either need to convert ''solution file'' and ''project files'' from VS2003 format to VS2005 format or obtain files compatible with VS2005. You may also need to modify source files to work around the incompatibility between VS2003 and VS2005.

'''Note''': linden\indra\indra_complete_vs8.sln is a solution file already included in the source archive and intended for the Visual Studio 2005, but it '''does not work''' (at least between 1.14.0 and 1.17.0.9 distribution). This may change in a future release, if Lindens include an updated versions of the '''_vc8''' files.

 
 
== Using pre-built solution/project files ==

Currently there is a ZIP file with solution/project files available on the [https://jira.secondlife.com/browse/VWR-1151 JIRA bug tracker issue VWR-1151].

If you are building 1.16 or 1.17, most likely the easiest way towards compiling SL on MS2005 will be to:
* download the ZIP archive there
* unpack it and copy it onto your linden source tree (allow to overwrite files that have '''_vc8''' in the name).
* start Visual Studio 2005 (or VC++ Express).
* use "File > Open > Project/Solution" to open the linden\indra\indra_complete\indra_complete'''_vc8'''.sln (Note: If you plan to work with multiple versions over time, you will find it useful to rename '''indra_complete_vc8.sln''' to something which contains the version number, e.g. '''indra_1_17_0_11_vc8.sln''' before opening)
* right click '''newview''' in the frame Solution Explorer and click "Set as StartUp Project".
* proceed with applying the '''Workarounds''' below (skip '''Manual conversion''').

'''Note:''' If, while compiling, you later encounter errors or problems regarding the projects, you may have to do the manual conversion instead.

 
 

== Manual conversion of the solution/projects ==

If you can not find a set of project files (see above), there are instructions available how to manually do it: [[Converting_project_files_for_MSVS2005]] (this step will take about 5-15 minutes, depending on how proficient you are using VS2005).

 
 
 

== Workarounds ==

There are more compatibility problems between VS2003 and VS2005. You need the following code edits.
 
=== test project/crash_logger/updater ===

For whatever reason, the '''test''' project doesn't work under VS2005. Workaround is to disable it as follows: Right click on the '''test''' and choose '''Unload Project'''.

If you do not plan to create a full download build, you can exclude the '''win_crash_logger''' and '''win_updater''' from newview's project dependencies and unload them also. But be careful with unloading these projects without removing them from the dependencies, because I have seen VS2005 act highly erratic while linking then project when I tried this.
 
=== QuickTime removal ===

If you don't want to get Apple QuickTime SDK, you can disable it as follows:
*linden\indra\llcommon\llpreprocessor.h - near line 58 (the line below '''#elif LL_WINDOWS''')
--50: #define LL_QUICKTIME_ENABLED 1
++50: #define LL_QUICKTIME_ENABLED '''''0'''''

* Pick '''ReleaseNoOpt''' in the Solution Configurations drop-down box beside the green arrow under the tool bar, and do the followings on the Solution Explorer frame:
*Click '''newview''' to select it alone.
**Choose Properties.
**Under Configuration Properties > Linker > Input, click '''Additional Dependencies''' on the right to show a button labeled "'''...'''" on it at the very right on the line, then click the '''...''' button.
**Scroll down the list to find '''qtmlclient.lib'''. Delete this single line.
**Click '''OK''' to close the "Additional Dependencies" dialog, then click OK again to close the "newview Property Pages" dialog box.
* Pick '''ReleaseForDownload''' in the Solution Configurations drop-down box. Click '''newview''' to select it alone and do the same thing again.
 
 
 
= Ready, Set, Build! =

== Building ==
* Build either '''ReleaseNoOpt''' (for debugging) or '''ReleaseForDownload''' (for production code).
* To do this, pick either in the Solution Configurations drop-down box beside the green arrow under the tool bar.
* Make sure '''newview''' is set as the active project (otherwise set from newview's right-click menu).
* Select Build-Menu > Build Solution or press F7.
* newview_noopt.exe will be built in linden\indra\newview\ReleaseNoOpt or SecondLife.exe will be linden\indra\newview\ReleaseForDownload.
 
== Common compile errors ==
* See [[Common compilation problems]] if you run into other errors while building.
 
== Running ==
* You can run the viewer by '''Debug > Start Debugging''' or '''Debug > Start "Without Debugging''' in Visual Studio.
* To run it outside VS, create a shortcut to SecondLife.exe, and change the start location to linden\indra\newview\ (all the .dll will be found there.)
* Alternately copy the exe (possibly rename it) to your "c:\program files\second life" folder.
 
== Debugging Info/Configurations ==
* Usually you will either use '''ReleaseNoOpt''' or the '''ReleaseForDownload''' configuration.
* '''ReleaseNoOpt''' (not optimized) compiles faster and has more debugging information, but this comes at a runtime penalty of about 50% of your FPS in busy areas, compared to ReleaseForDownload build.
* '''ReleaseForDownload''' also has debugging information and runs fine in the debugger (although at times you may miss access to some local variables).
* '''ReleaseNoOpt''' comes with a seperate debugging console window opens and stays open for the duration of your session, but you can access the same information also by pressing Shift+Ctrl+4 in the viewer (all builds).
* The debug console log can also be redirected to a file if you add "2>secondlife.log" to the command line (Newview, Properties, Debugging, Command line arguments).
* If you want to build a '''Debug''' configuration, see the specific section with compile instructions on [[Finding_leaks]]
 

== Problems Running? ==
* '''Inventory errors''': If you're getting errors while trying to load your inventory, try [[Help:Stuck logging in|clearing your cache and deleting other temporary files]].
* '''Missing smime3 DLL''': Those are parts of the integrated web browser. Copy 'smime3.dll', 'nss3.dll', 'softokn3.dll', and 'ssl3.dll' files from your official client's main folder to "linden\indra\newview".
* '''Can't connect''': In the debug builds there is a selection box on the login screen to select the server to connect to. '''Agni''' is the production grid, '''aditi''' is the beta grid. (There seems to be a bug in this part of the code, you may have to make your selection, close the viewer and repoen it, before you can connect to the selected grid).
 
 
= Submit Patches =
This is probably faaar down the road, but if you make changes to the source and want to submit them, see the page about [[Submitting patches|submitting patches]].

Compiling the viewer (MSVS2005)

2007-08-03T09:19:57Z

Nicholaz Beresford:

{{CompileNav}}

This page explains how you can compile the viewer on Microsoft Windows using Visual Studio 2005 or Visual C++ Express 2005. Note that Lindens are using VS2003 and the whole setup is a bit easier there, so if you have Visual Studio 2003 available, you should read [[Compiling the viewer (MSVS2003)|compiling with VS2003]] and you will get less trouble with it than with VS2005.

The following explanation is adjusted for Viewer releases 1.16.0.5 or later. See an [http://wiki.secondlife.com/w/index.php?title=Compiling_the_viewer_%28MSVS2005%29&oldid=22294 older version of this page] for the Viewer releases 1.15 or before.

= Preparing the Development Environment =

== Installing/Configuring VS2005 ==

You need to setup the compiler and Microsoft Development tools as follows:
* Visual Studio 2005 '''''-or-''''' [http://msdn.microsoft.com/vstudio/express/visualc/download/ Visual C++ 2005 Express](Free) (Also, although not strictly necessary, eventually pick up and install SP1 for VS2005.)
* [http://www.microsoft.com/downloads/details.aspx?familyid=0BAF2B35-C656-4969-ACE8-E4C0C0716ADB&displaylang=en Microsoft Platform SDK]
* A DirectX 9.0 SDK released on or after Summer of 2003 [http://download.microsoft.com/download/5/1/f/51ff8357-0af3-418b-9d0b-e9a5cdc39759/dxsdk_dec2006.EXE DirectX 9.0 SDK (December 2006)] [http://www.microsoft.com/downloads/details.aspx?FamilyID=9216652f-51e0-402e-b7b5-feb68d00f298&displaylang=en DirectX 9.0 SDK Update (Summer 2003)]
: '''Note''': If you have previously installed an older version of the DirectX 9.0 SDK, remove it first (from Control Panel -> Add or Remove Programs) before installing this version. Installing the new SDK "on top" of an older version may cause problems.
* Set up the project globals:
** Start Microsoft Visual Studio 2005
** Go to Tools > Options > Projects > VC++ Directories
** Make sure that the '''includes''' ([[:Image:MSVS2005 Global Project Options Include Files.JPG|'''screen shot''']]) and '''libraries''' ([[:Image:MSVS2005 Global Project Options Library Files.JPG|'''screen shot''']]) paths have the Platform SDK paths first, then the DirectX SDK paths, and then the Visual C++ paths. You may need to check "Show All Settings" at the bottom for VC++ Directories to show.
** If the DirectX SDK paths aren't present, add them to both '''includes''' and '''libraries'''.
*: Note: The newest DirectX SDK ("December 2006") lib folder has two sub-folders, x64 and x86. Make sure your path goes to one of them (select '''lib/x86''', not just '''lib'''), or you will get a Link error.
 

== Getting other Development Tools ==
You will also need some open source development tools.
* [http://www.cygwin.com/ 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. The project files use several hardcoded references that expect Cygwin to be installed at '''C:\cygwin''', if it's not you'll need to edit those references.
* [http://www.activestate.com/Products/ActivePython/?mp=1 ActivePython 2.3x or later] - Latest Version is 2.5.1.1
** It is required but can be avoided if you are compiling 1.18 or later viewers. Either download and install or hack the prebuild.bat files as described in [http://jira.secondlife.com/browse/VWR-1267 VWR-1267].
* ActivePerl was recommended for previous versions on this Wiki, but it currently appears, that it is not strictly necessary unless you are planning to build your own version of all libraries (which most likely you don't want to do). So for a start it may be safe to skip it.
*: [http://www.activestate.com/Products/ActivePerl/?mp=1 ActivePerl]

 
 
 
= Downloading Source Code =

You can download the Viewer source codes on the [[source downloads]] page. You can also use a [[version control repository]].

At a minimum, grab the source package and the artwork package, but for a start, also grab the library archive. Many of the libraries can either be compiled from source or downloaded from other sites (see below), but this will take hours and thus it is easiest to also get the package with libraries compiled by the Lindens.

'''WARNING:'''
* If the directory path you keep the SL source in has a space in it, the batch file that copies message_template.msg will fail. So, if you unzip or checkout the source tree into, e.g., "C:\Projects\Dir with space in name\Etc\linden", it won't work!
* You should also avoid using non-ASCII (national) characters in the paths, although some localized versions of the tool puts some as a default...
* Unzip or checkout your source tree into a directory that has as short full pathname as possible, since long paths cause some unexpected trouble during the build.

In other words, the easiest way to get this working is to get ''source'', ''artwork'' and ''libraries'' from the [[source downloads]] page and unpack them all into the same directory/folder, which ideally would be a folder in (or near) the root directory with a short name like ''sl_1_16_0_5''.
 
 
 
 

= Installing Libraries =

SL Viewer depends on some third party libraries. Some of them are open source, some others are not.

== Open Source Libraries ==

You can download the pre-build open source libraries from LL. They are available on [[source downloads]] page. Unzip them into your SL viewer source code directory, maintaining the same directory structure.

'''NOTE: The VS2003 libraries provided in the [[source downloads]] do not fully work with VS2005 compiled binaries. They will compile with the viewer under VS2005, but the VS2003 libraries are not fully STL compliant. The differences of [http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vclang/html/vclrfnonstandardbehavior.asp non-standard behavior in MSVS] are the known cause.'''

Alternatively, it may be possible to get the source files for the libraries and build by yourself. See [[Compiling the viewer libraries (MSVS 2003)|the instruction for VS2003 users]] if you try it. Please note, however, it is not known that VS2005 can successfully compile the libraries. '''You have been warned.''' (If you can make it, please write the info on this wiki...)
 
 

== Proprietary Libraries ==

Lindens does not inlcude the following proprietary libraries. You will need to follow the instructions to acquire below and copy them to the source path.

However, it probably is 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 (like ''XCOPY OLIB SL_1_16_0_5 /S''). The reason is, that these steps are cumbersome and will have to be repeated for each new release (at least if you keep the source for each release in it's own folder). If you do not want to do this, of course you can just copy the files directly into the linden source paths.

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
 
=== Fmod ===
* Download & extract [http://www.fmod.org/ifmoddownload.html fmod 3.75 api for win32] (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\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"
 
=== OpenGL ===
* Download [http://oss.sgi.com/projects/ogl-sample/sdk.html glext.h, glxext.h, and wglext.h]
* Copy them to "linden\libraries\i686-win32\include\GL"
* You don't need any additional *.lib or *.dll for OpenGL.
 
=== Quicktime ''(optional)'' ===
'''Note:''' This download requires a registration at the Apple Quicktime website and take a bit of time. You can avoid using QuickTime if you want, bee [[#QuickTime removal|below]] for details. Remember that your viewer '''can't play in-world movies''' if you do so.
* Download & install the [http://connect.apple.com/cgi-bin/WebObjects/MemberSite.woa/203/wa/getSoftware?fileID=20525&code=y&source=x&wosid=4h16WcyMtVfd2P1EffGafkoxFcr 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".
 
 
 
= Configuring for VS2005 =

Lindens use VS2003 to develop the viewer.

You either need to convert ''solution file'' and ''project files'' from VS2003 format to VS2005 format or obtain files compatible with VS2005. You may also need to modify source files to work around the incompatibility between VS2003 and VS2005.

'''Note''': linden\indra\indra_complete_vs8.sln is a solution file already included in the source archive and intended for the Visual Studio 2005, but it '''does not work''' (at least between 1.14.0 and 1.17.0.9 distribution). This may change in a future release, if Lindens include an updated versions of the '''_vc8''' files.

 
 
== Using pre-built solution/project files ==

Currently there is a ZIP file with solution/project files available on the [https://jira.secondlife.com/browse/VWR-1151 JIRA bug tracker issue VWR-1151].

If you are building 1.16 or 1.17, most likely the easiest way towards compiling SL on MS2005 will be to:
* download the ZIP archive there
* unpack it and copy it onto your linden source tree (allow to overwrite files that have '''_vc8''' in the name).
* start Visual Studio 2005 (or VC++ Express).
* use "File > Open > Project/Solution" to open the linden\indra\indra_complete\indra_complete'''_vc8'''.sln (Note: If you plan to work with multiple versions over time, you will find it useful to rename '''indra_complete_vc8.sln''' to something which contains the version number, e.g. '''indra_1_17_0_11_vc8.sln''' before opening)
* right click '''newview''' in the frame Solution Explorer and click "Set as StartUp Project".
* proceed with applying the '''Workarounds''' below (skip '''Manual conversion''').

'''Note:''' If, while compiling, you later encounter errors or problems regarding the projects, you may have to do the manual conversion instead.

 
 

== Manual conversion of the solution/projects ==

If you can not find a set of project files (see above), there are instructions available how to manually do it: [[Converting_project_files_for_MSVS2005]] (this step will take about 5-15 minutes, depending on how proficient you are using VS2005).

 
 
 

== Workarounds ==

There are more compatibility problems between VS2003 and VS2005. You need the following code edits.
 
=== test project/crash_logger/updater ===

For whatever reason, the '''test''' project doesn't work under VS2005. Workaround is to disable it as follows: Right click on the '''test''' and choose '''Unload Project'''.

If you do not plan to create a full download build, you can exclude the '''win_crash_logger''' and '''win_updater''' from newview's project dependencies and unload them also. But be careful with unloading these projects without removing them from the dependencies, because I have seen VS2005 act highly erratic while linking then project when I tried this.
 
=== QuickTime removal ===

If you don't want to get Apple QuickTime SDK, you can disable it as follows:
*linden\indra\llcommon\llpreprocessor.h - near line 58 (the line below '''#elif LL_WINDOWS''')
--50: #define LL_QUICKTIME_ENABLED 1
++50: #define LL_QUICKTIME_ENABLED '''''0'''''

* Pick '''ReleaseNoOpt''' in the Solution Configurations drop-down box beside the green arrow under the tool bar, and do the followings on the Solution Explorer frame:
*Click '''newview''' to select it alone.
**Choose Properties.
**Under Configuration Properties > Linker > Input, click '''Additional Dependencies''' on the right to show a button labeled "'''...'''" on it at the very right on the line, then click the '''...''' button.
**Scroll down the list to find '''qtmlclient.lib'''. Delete this single line.
**Click '''OK''' to close the "Additional Dependencies" dialog, then click OK again to close the "newview Property Pages" dialog box.
* Pick '''ReleaseForDownload''' in the Solution Configurations drop-down box. Click '''newview''' to select it alone and do the same thing again.
 
 
 
= Ready, Set, Build! =

== Building ==
* Build either '''ReleaseNoOpt''' (for debugging) or '''ReleaseForDownload''' (for production code).
* To do this, pick either in the Solution Configurations drop-down box beside the green arrow under the tool bar.
* Make sure '''newview''' is set as the active project (otherwise set from newview's right-click menu).
* Select Build-Menu > Build Solution or press F7.
* newview_noopt.exe will be built in linden\indra\newview\ReleaseNoOpt or SecondLife.exe will be linden\indra\newview\ReleaseForDownload.
 
== Common compile errors ==
* See [[Common compilation problems]] if you run into other errors while building.
 
== Running ==
* You can run the viewer by '''Debug > Start Debugging''' or '''Debug > Start "Without Debugging''' in Visual Studio.
* To run it outside VS, create a shortcut to SecondLife.exe, and change the start location to linden\indra\newview\ (all the .dll will be found there.)
* Alternately copy the exe (possibly rename it) to your "c:\program files\second life" folder.
 
== Debugging Info/Configurations ==
* Usually you will either use '''ReleaseNoOpt''' or the '''ReleaseForDownload''' configuration.
* '''ReleaseNoOpt''' (not optimized) compiles faster and has more debugging information, but this comes at a runtime penalty of about 50% of your FPS in busy areas, compared to ReleaseForDownload build.
* '''ReleaseForDownload''' also has debugging information and runs fine in the debugger (although at times you may miss access to some local variables).
* '''ReleaseNoOpt''' comes with a seperate debugging console window opens and stays open for the duration of your session, but you can access the same information also by pressing Shift+Ctrl+4 in the viewer (all builds).
* The debug console log can also be redirected to a file if you add "2>secondlife.log" to the command line (Newview, Properties, Debugging, Command line arguments).
* If you want to build a '''Debug''' configuration, see the specific section with compile instructions on [[Finding_leaks]]
 

== Problems Running? ==
* '''Inventory errors''': If you're getting errors while trying to load your inventory, try [[Help:Stuck logging in|clearing your cache and deleting other temporary files]].
* '''Missing smime3 DLL''': Those are parts of the integrated web browser. Copy 'smime3.dll', 'nss3.dll', 'softokn3.dll', and 'ssl3.dll' files from your official client's main folder to "linden\indra\newview".
* '''Can't connect''': In the debug builds there is a selection box on the login screen to select the server to connect to. '''Agni''' is the production grid, '''aditi''' is the beta grid. (There seems to be a bug in this part of the code, you may have to make your selection, close the viewer and repoen it, before you can connect to the selected grid).
 
 
= Submit Patches =
This is probably faaar down the road, but if you make changes to the source and want to submit them, see the page about [[Submitting patches|submitting patches]].

Talk:Bug triage/2007-08-08

2007-07-24T22:36:41Z

Nicholaz Beresford: New page: == Invitation == Following the lead of Rob Linden and Benjamin Linden, I'll be starting my own weekly bug triages focusing on Viewer Crashes. I created a new filter in the Issue Tracker ...

== Invitation ==

Following the lead of Rob Linden and Benjamin Linden, I'll be starting my own weekly bug triages focusing on Viewer Crashes. I created a new filter in the Issue Tracker titled (appropriately!) "Viewer Crashes". We'll be looking through issues that have not already been imported into Linden Lab's internal issue tracker, sorted by priority.

The Viewer Crashes bug triage will be on Wednesdays at 3:00 pm at my house in Linden Village. We'll use the same general process the other triages have been following. Minutes and transcripts from the triage will be posted to the Wiki after each triage. I’ll be your host, but expect to see other Lindens make appearances and help out.

The first Viewer Crashes bug triage will be held Wednesday, July 25th. I could really use some help with the agenda for this first triage. Any volunteers?

Thanks!

--Bridie Linden

Bug triage/2007-08-08

2007-07-24T22:28:37Z

Nicholaz Beresford:

{{Bug triage}}

Next meeting: 2007-07-25, 3pm PDT at {{User|Bridie Linden}}'s house. See [[Bug triage]] for details.

 

== Top Viewer Crashes ==

* There is a list of top viewer crashes being sent to LL: [[Crash Reports]]

'''The Dan Linden Crashes are excerpts from the above top viewer crashes'''
* {{jira|VWR-586}} - Votes: 0 - crash in LLRenderPass::pushBatch - {{User|dan linden}}
* {{jira|VWR-588}} - Votes: 0 - crash in LLInventoryItem::setCreationDate - {{User|dan linden}}
* {{jira|VWR-589}} - Votes: 0 - crash in LLFace::setSize - {{User|dan linden}}
* {{jira|VWR-594}} - Votes: 1 - crash in LLError::crashAndLoop - {{User|dan linden}}
* {{jira|VWR-592}} - Votes: 0 - crash in LLTemplateMessageBuilder::addString - {{User|dan linden}}
* {{jira|VWR-596}} - Votes: 0 - crash in LLTextureFetchWorker::clearPackets - {{User|dan linden}}
* {{jira|VWR-595}} - Votes: 0 - crash in LLViewBorder::drawOnePixelLines - {{User|dan linden}}
* {{jira|VWR-590}} - Votes: 0 - crash in LLWindowWin32::close - {{User|dan linden}}
* {{jira|VWR-591}} - Votes: 0 - crash in LLVLComposition::generateHeights - {{User|dan linden}}
* {{jira|VWR-620}} - Votes: 0 - crash in LLImageJ2C::updateData - {{User|dan linden}}
* {{jira|VWR-619}} - Votes: 0 - crash in LLFace::setTEOffset - {{User|dan linden}}
* {{jira|VWR-617}} - Votes: 0 - crash in LLPipeline::updateMove() - {{User|dan linden}}
* {{jira|VWR-1081}} - Votes: 0 - crash in LLViewerImageList::updateImagesFetchTextures(float) - {{User|dan linden}}
* {{jira|VWR-1082}} - Votes: 0 - crash in LLMsgData::~LLMsgData - {{User|dan linden}}
* {{jira|VWR-1084}} - Votes: 0 - crash in LLFloaterTools::setStatusText - {{User|dan linden}}
* {{jira|VWR-1083}} - Votes: 0 - crash in LLRenderPass::pushBatch - {{User|dan linden}}

== Viewer Crashes ==

(Current list (48) of [https://jira.secondlife.com/secure/IssueNavigator.jspa?mode=hide&requestId=10492 Viewer Crashes] that have '''not''' been imported, sorted by priority)

* {{jira|VWR-1682}} - Votes: 1 - System reboot shortly after login on 1.18.0.6 - {{User|Grazel Cosmo}}
* {{jira|VWR-1765}} - Votes: 1 - Compleate system hang after inworld a few minutes - {{User|Gershom Taov}}
* {{jira|VWR-1863}} - Votes: 0 - vtdisp Blue screen - {{User|Zaphlarb Allen}}
* {{jira|VWR-673}} - Votes: 5 - Viewer freeze on timed-out asset download request. - {{User|Elbereth Witte}}
* {{jira|VWR-1853}} - Votes: 0 - Missing fonts = segfault x64 Linux - {{User|Awsoonn Rawley}}
* {{jira|VWR-1864}} - Votes: 0 - dwt_decode_tile SegFault - {{User|Awsoonn Rawley}}
* {{jira|VWR-1855}} - Votes: 1 - Crash immedatly on Login - {{User|Awsoonn Rawley}}
* {{jira|VWR-376}} - Votes: 3 - Voice Viewer randomly crashing - {{User|xionwolf udal}}
* {{jira|VWR-1459}} - Votes: 1 - Unexpected crash in Mac OS X: Using a menu? - {{User|Alos Fellini}}
* {{jira|VWR-1718}} - Votes: 1 - First Look: Selecting multiple items in object contents then choosing Properties causes crash. - {{User|Doubledown Tandino}}
* {{jira|VWR-228}} - Votes: 2 - Attempting to log into a down sim results in a randomized location - {{User|Strife Onizuka}}
* {{jira|VWR-524}} - Votes: 2 - X300 / x600 Graphics Card Crash - {{User|davidbatty hathaway}}
* {{jira|VWR-629}} - Votes: 3 - Buffer Overrun message from the MS Visual C++ Runtime Library - viewer terminated. - {{User|Aaron Greenberg}}
* {{jira|VWR-695}} - Votes: 0 - Old fashioned memory corruption - {{User|Lee Ponzu}}
* {{jira|VWR-854}} - Votes: 0 - Viewer crashes in non-Administrator user in MS Vista - {{User|Benja Kepler}}
* {{jira|VWR-861}} - Votes: 1 - memory leak - {{User|tx Oh}}
* {{jira|VWR-1090}} - Votes: 0 - Mac Intel-native version of universal binary 1.16.0.6 crashes at start-up - Rosetta version works stable - {{User|Harry Palliard}}
* {{jira|VWR-1257}} - Votes: 0 - Viewer shuts down with no reason - {{User|Dre Dagostino}}
* {{jira|VWR-1272}} - Votes: 0 - Random Lockups on First Look Voice - {{User|Ice Semple}}
* {{jira|VWR-1564}} - Votes: 0 - Viewer crashes when started with the "-local" argument. - {{User|Timmahy Widget}}
* {{jira|VWR-1690}} - Votes: 0 - SL Locks up, and TCP/IP temporarily fails for whole system - {{User|PlanetThoughts Raymaker}}
* {{jira|VWR-738}} - Votes: 1 - SL crashes when loading with a GTK_IM scim module - {{User|Kilcher Jewell}}
* {{jira|VWR-502}} - Votes: 3 - client crashes on quit - {{User|Lex Neva}}
* {{jira|VWR-1744}} - Votes: 0 - Keyboard/Mouse Freeze in XP pro when minimizing SL full screen to get desktop access - {{User|Barrpeople Winx}}
* {{jira|VWR-396}} - Votes: 0 - Crash message stating xpcom_core.dll is not found - {{User|Kittenanne Mousehold}}
* {{jira|VWR-1656}} - Votes: 0 - Second Life Viewer freezes and causes an graphical driver restart on Vista Ultimate 32-bit on a Dell D620 with Nvidia NVS Quatro 110M gfx card and crashes after driver restart. - {{User|JW Russell}}
* {{jira|VWR-1343}} - Votes: 0 - SL Crashes with nVIDIA Stereo driver - {{User|Kyra Arkin}}
* {{jira|VWR-1587}} - Votes: 0 - Window "The application SLVoice quit unexpectedly." appears but the app hasn't crashed. Window appears every few minutes afterwards. - {{User|Prng Flagstaff}}
* {{jira|VWR-1848}} - Votes: 1 - Crashreport window does not show status and never closes - {{User|Lisa Lowe}}
* {{jira|VWR-1829}} - Votes: 0 - Client crash when entering password with caps lock on [mac] - {{User|Kerian Bunin}}

== Fast Track Import ==

(Move bugs here that have solid repros, or valid patches that you have reviewed)

== Hot by Vote ==

== Patches ==

== Misc Pool ==

== Pre-meeting activity ==

Some issues will be resolved in the course of building this agenda. Rather than deleting them from the proposed agenda, move the issue and associated discussion into the appropriate section below.

=== Imported ===

=== Resolved ===
* {{jira|VWR-1290}} - Votes: 6 - Client Crashes on every log out / logging out - {{User|Robin Laffer}}
** Closed. Dupe of {{jira|VWR-502}} [[User:Dzonatas Sol|Dzonatas Sol]] 13:03, 24 July 2007 (PDT)
* {{jira|VWR-817}} - Votes: 2 - Viewer crashes on quit - {{User|Benja Kepler}}
** Closed. Dupe of {{jira|VWR-502}} [[User:Dzonatas Sol|Dzonatas Sol]] 13:11, 24 July 2007 (PDT)

Bug triage/2007-10-23

2007-07-20T14:11:21Z

Nicholaz Beresford:

{{Bug triage}}

Next meeting: 2007-07-24, 10am PDT at {{User|Benjamin Linden}}'s office. See [[Bug triage]] for details.

== Note to UI Triagers ==
If you find new issues which might be suitable for solution through open source programmers (many UI isses tend to fall into that category) pleaes add them to/link them from {{jira|VWR-1577}} ([[User:Nicholaz Beresford|Nicholaz]] 06:59, 20 July 2007 (PDT))

 
== Bugfix Patches ==
* {{jira|VWR-546}} - Votes: 1 - Using inspect interfers with mouse usage. - {{User|Ryozu Kojima}} (patch Nicholaz Beresford)
* {{jira|VWR-1721}} - Votes: 1 - GUI quirk in groups - {{User|Nicholaz Beresford}}

 
== Feature Request Patches ==
* {{jira|MISC-82}} - Votes: 27 - New Feature -> UI -> IM -> Teleport (other person) Button - {{User|bob wellman}}
* {{jira|VWR-1825}} -> {{jira|VWR-1826}} Inventory double click: Landmarks -> Teleport {{User|Nicholaz Beresford}}
*: please revisit: this was disucssed last week for general objects->wear and landmarks was touched/discussed as a side issue (Nicholaz)
* {{jira|VWR-1825}} -> {{jira|VWR-1827}} Inventory double click: Linden provided attachments -> wear {{User|Nicholaz Beresford}}
*: please revisit: this was disucssed last week for general objects->wear but there is a special type of objects in new user's inventory (Nicholaz)

 
== Other Bug Reports ==
* {{jira|VWR-1664}} - Votes: 5 - Selecting "Cancel" during TP process leaves avatar motionless - {{User|Edna Sperber}}
* {{jira|VWR-289}} - Votes: 4 - URLs for video media streaming need to be URL-encoded or stream doesn't work - {{User|Gwyneth Llewelyn}}
* {{jira|VWR-1619}} - Votes: 3 - Instant message window not resizable (reverts to default on sending/recieving message) - {{User|Skinkie Winkler}}
* {{jira|VWR-749}} - Votes: 3 - Bandwidth indicator: Kbps, should not have capital k - {{User|Daedalus Young}}
* {{jira|VWR-1408}} - Votes: 3 - Online status viewable via Groups even if "Make my online status visible only to my Friends" is set - {{User|Cloud Bracken}}
* {{jira|VWR-584}} - Votes: 2 - Show Avatar Names Temporarily - nonfunctional - {{User|jay norfolk}}
* {{jira|VWR-645}} - Votes: 2 - Sit, then click on self: camera pans but does not tilt - {{User|jeffer clave}}
* {{jira|VWR-817}} - Votes: 2 - Viewer crashes on quit - {{User|Benja Kepler}}
* {{jira|VWR-1667}} - Votes: 2 - Profile "My Notes" tab - contents replaced by "Loading..." if you close it before it displays the actual contents - {{User|idoru ng}}
* {{jira|VWR-1286}} - Votes: 2 - alt-zooming on hollow face mishandled - {{User|Lex Neva}}
* {{jira|VWR-1097}} - Votes: 2 - Chat and Im history no longer saved - {{User|astarte artaud}}
* {{jira|VWR-977}} - Votes: 2 - Alt-zoom on anything results in uncontrollable spinning camera - {{User|gonta maltz}}
* {{jira|VWR-298}} - Votes: 1 - Practically impossible to enter Japanese text when viewer is running full-screen on MacOS - {{User|Alissa Sabre}}
* {{jira|VWR-1124}} - Votes: 1 - Show Cross Sections not working on Linux with NVidia - {{User|Zi Ree}}
* {{jira|VWR-1332}} - Votes: 1 - Resident Chooser Fails When Inventory Contains NO Contact Cards - {{User|Chance Unknown}}
* {{jira|VWR-1424}} - Votes: 1 - Local ruler shows inaccurate grid units (defaults to 1) - {{User|McCabe Maxsted}}
* {{jira|VWR-1457}} - Votes: 1 - Friend Online/Offline pop up steals focus from Inventory scrolling. - {{User|cat gisel}}
* {{jira|VWR-1541}} - Votes: 1 - Shortcut key Ctrl-` cannot be entered on Japanese version of Windows with 104 keyboard - {{User|Sat Nemeth}}
* {{jira|VWR-719}} - Votes: 1 - Money dialogs missing after group notifications - {{User|Daedalus Young}}
* {{jira|VWR-1003}} - Votes: 1 - Enable Vertex Shaders removes textures from prims but adds windlight effects - {{User|Billie Scaggs}}
* {{jira|VWR-444}} - Votes: 1 - "My Active Title" drop-down does not refresh when role changes - {{User|Gigs Taggart}}
* {{jira|VWR-1713}} - Votes: 1 - Object owner name truncated in Properties window - {{User|Benja Kepler}}
* {{jira|VWR-1281}} - Votes: 1 - text selecting/hilighting rendering problem - {{User|Lex Neva}}
* {{jira|VWR-1724}} - Votes: 1 - HUD zoom snaps back after selecting another HUD object - {{User|Celierra Darling}}
* {{jira|VWR-1730}} - Votes: 1 - After accepting texture or notecard, Keep/Discard options display again - {{User|Celierra Darling}}

 
== Pre-meeting activity ==

Some issues will be resolved in the course of building this agenda. Rather than deleting them from the proposed agenda, move the issue and associated discussion into the appropriate section below.

 
=== Imported ===

 
=== Resolved ===

Bug triage/2007-10-23

2007-07-20T14:09:38Z

Nicholaz Beresford:

{{Bug triage}}

Next meeting: 2007-07-24, 10am PDT at {{User|Benjamin Linden}}'s office. See [[Bug triage]] for details.

== Note to UI Triagers ==
If you find new issues which might be suitable for solution through open source programmers (many UI isses tend to fall into that category) pleaes add them to/link them from {{jira|VWR-1577}} ([[User:Nicholaz Beresford|Nicholaz]] 06:59, 20 July 2007 (PDT))

== Bugfix Patches ==
* {{jira|VWR-546}} - Votes: 1 - Using inspect interfers with mouse usage. - {{User|Ryozu Kojima}} (patch Nicholaz Beresford)

 
== Feature Request Patches ==
* {{jira|MISC-82}} - Votes: 27 - New Feature -> UI -> IM -> Teleport (other person) Button - {{User|bob wellman}}
* {{jira|VWR-1825}} -> {{jira|VWR-1826}} Inventory double click: Landmarks -> Teleport {{User|Nicholaz Beresford}}
*: please revisit: this was disucssed last week for general objects->wear and landmarks was touched/discussed as a side issue (Nicholaz)
* {{jira|VWR-1825}} -> {{jira|VWR-1827}} Inventory double click: Linden provided attachments -> wear {{User|Nicholaz Beresford}}
*: please revisit: this was disucssed last week for general objects->wear but there is a special type of objects in new user's inventory (Nicholaz)

 
== Other Bug Reports ==
* {{jira|VWR-1664}} - Votes: 5 - Selecting "Cancel" during TP process leaves avatar motionless - {{User|Edna Sperber}}
* {{jira|VWR-289}} - Votes: 4 - URLs for video media streaming need to be URL-encoded or stream doesn't work - {{User|Gwyneth Llewelyn}}
* {{jira|VWR-1619}} - Votes: 3 - Instant message window not resizable (reverts to default on sending/recieving message) - {{User|Skinkie Winkler}}
* {{jira|VWR-749}} - Votes: 3 - Bandwidth indicator: Kbps, should not have capital k - {{User|Daedalus Young}}
* {{jira|VWR-1408}} - Votes: 3 - Online status viewable via Groups even if "Make my online status visible only to my Friends" is set - {{User|Cloud Bracken}}
* {{jira|VWR-584}} - Votes: 2 - Show Avatar Names Temporarily - nonfunctional - {{User|jay norfolk}}
* {{jira|VWR-645}} - Votes: 2 - Sit, then click on self: camera pans but does not tilt - {{User|jeffer clave}}
* {{jira|VWR-817}} - Votes: 2 - Viewer crashes on quit - {{User|Benja Kepler}}
* {{jira|VWR-1667}} - Votes: 2 - Profile "My Notes" tab - contents replaced by "Loading..." if you close it before it displays the actual contents - {{User|idoru ng}}
* {{jira|VWR-1286}} - Votes: 2 - alt-zooming on hollow face mishandled - {{User|Lex Neva}}
* {{jira|VWR-1097}} - Votes: 2 - Chat and Im history no longer saved - {{User|astarte artaud}}
* {{jira|VWR-977}} - Votes: 2 - Alt-zoom on anything results in uncontrollable spinning camera - {{User|gonta maltz}}
* {{jira|VWR-298}} - Votes: 1 - Practically impossible to enter Japanese text when viewer is running full-screen on MacOS - {{User|Alissa Sabre}}
* {{jira|VWR-1124}} - Votes: 1 - Show Cross Sections not working on Linux with NVidia - {{User|Zi Ree}}
* {{jira|VWR-1332}} - Votes: 1 - Resident Chooser Fails When Inventory Contains NO Contact Cards - {{User|Chance Unknown}}
* {{jira|VWR-1424}} - Votes: 1 - Local ruler shows inaccurate grid units (defaults to 1) - {{User|McCabe Maxsted}}
* {{jira|VWR-1457}} - Votes: 1 - Friend Online/Offline pop up steals focus from Inventory scrolling. - {{User|cat gisel}}
* {{jira|VWR-1541}} - Votes: 1 - Shortcut key Ctrl-` cannot be entered on Japanese version of Windows with 104 keyboard - {{User|Sat Nemeth}}
* {{jira|VWR-719}} - Votes: 1 - Money dialogs missing after group notifications - {{User|Daedalus Young}}
* {{jira|VWR-1003}} - Votes: 1 - Enable Vertex Shaders removes textures from prims but adds windlight effects - {{User|Billie Scaggs}}
* {{jira|VWR-444}} - Votes: 1 - "My Active Title" drop-down does not refresh when role changes - {{User|Gigs Taggart}}
* {{jira|VWR-1713}} - Votes: 1 - Object owner name truncated in Properties window - {{User|Benja Kepler}}
* {{jira|VWR-1281}} - Votes: 1 - text selecting/hilighting rendering problem - {{User|Lex Neva}}
* {{jira|VWR-1724}} - Votes: 1 - HUD zoom snaps back after selecting another HUD object - {{User|Celierra Darling}}
* {{jira|VWR-1721}} - Votes: 1 - GUI quirk in groups - {{User|Nicholaz Beresford}}
* {{jira|VWR-1730}} - Votes: 1 - After accepting texture or notecard, Keep/Discard options display again - {{User|Celierra Darling}}

 
== Pre-meeting activity ==

Some issues will be resolved in the course of building this agenda. Rather than deleting them from the proposed agenda, move the issue and associated discussion into the appropriate section below.

 
=== Imported ===

 
=== Resolved ===

Bug triage/2007-10-23

2007-07-20T13:59:56Z

Nicholaz Beresford:

{{Bug triage}}

Next meeting: 2007-07-24, 10am PDT at {{User|Benjamin Linden}}'s office. See [[Bug triage]] for details.

== Note to UI Triagers ==
If you find new issues which might be suitable for solution through open source programmers (many UI isses tend to fall into that category) pleaes add them to/link them from {{jira|VWR-1577}} ([[User:Nicholaz Beresford|Nicholaz]] 06:59, 20 July 2007 (PDT))

== Bugfix Patches ==
* {{jira|VWR-546}} - Votes: 1 - Using inspect interfers with mouse usage. - {{User|Ryozu Kojima}}

== Feature Request Patches ==
* {{jira|MISC-82}} - Votes: 27 - New Feature -> UI -> IM -> Teleport (other person) Button - {{User|bob wellman}}

== Other Bug Reports ==
* {{jira|VWR-1664}} - Votes: 5 - Selecting "Cancel" during TP process leaves avatar motionless - {{User|Edna Sperber}}
* {{jira|VWR-289}} - Votes: 4 - URLs for video media streaming need to be URL-encoded or stream doesn't work - {{User|Gwyneth Llewelyn}}
* {{jira|VWR-1619}} - Votes: 3 - Instant message window not resizable (reverts to default on sending/recieving message) - {{User|Skinkie Winkler}}
* {{jira|VWR-749}} - Votes: 3 - Bandwidth indicator: Kbps, should not have capital k - {{User|Daedalus Young}}
* {{jira|VWR-1408}} - Votes: 3 - Online status viewable via Groups even if "Make my online status visible only to my Friends" is set - {{User|Cloud Bracken}}
* {{jira|VWR-584}} - Votes: 2 - Show Avatar Names Temporarily - nonfunctional - {{User|jay norfolk}}
* {{jira|VWR-645}} - Votes: 2 - Sit, then click on self: camera pans but does not tilt - {{User|jeffer clave}}
* {{jira|VWR-817}} - Votes: 2 - Viewer crashes on quit - {{User|Benja Kepler}}
* {{jira|VWR-1667}} - Votes: 2 - Profile "My Notes" tab - contents replaced by "Loading..." if you close it before it displays the actual contents - {{User|idoru ng}}
* {{jira|VWR-1286}} - Votes: 2 - alt-zooming on hollow face mishandled - {{User|Lex Neva}}
* {{jira|VWR-1097}} - Votes: 2 - Chat and Im history no longer saved - {{User|astarte artaud}}
* {{jira|VWR-977}} - Votes: 2 - Alt-zoom on anything results in uncontrollable spinning camera - {{User|gonta maltz}}
* {{jira|VWR-298}} - Votes: 1 - Practically impossible to enter Japanese text when viewer is running full-screen on MacOS - {{User|Alissa Sabre}}
* {{jira|VWR-1124}} - Votes: 1 - Show Cross Sections not working on Linux with NVidia - {{User|Zi Ree}}
* {{jira|VWR-1332}} - Votes: 1 - Resident Chooser Fails When Inventory Contains NO Contact Cards - {{User|Chance Unknown}}
* {{jira|VWR-1424}} - Votes: 1 - Local ruler shows inaccurate grid units (defaults to 1) - {{User|McCabe Maxsted}}
* {{jira|VWR-1457}} - Votes: 1 - Friend Online/Offline pop up steals focus from Inventory scrolling. - {{User|cat gisel}}
* {{jira|VWR-1541}} - Votes: 1 - Shortcut key Ctrl-` cannot be entered on Japanese version of Windows with 104 keyboard - {{User|Sat Nemeth}}
* {{jira|VWR-719}} - Votes: 1 - Money dialogs missing after group notifications - {{User|Daedalus Young}}
* {{jira|VWR-1003}} - Votes: 1 - Enable Vertex Shaders removes textures from prims but adds windlight effects - {{User|Billie Scaggs}}
* {{jira|VWR-444}} - Votes: 1 - "My Active Title" drop-down does not refresh when role changes - {{User|Gigs Taggart}}
* {{jira|VWR-1713}} - Votes: 1 - Object owner name truncated in Properties window - {{User|Benja Kepler}}
* {{jira|VWR-1281}} - Votes: 1 - text selecting/hilighting rendering problem - {{User|Lex Neva}}
* {{jira|VWR-1724}} - Votes: 1 - HUD zoom snaps back after selecting another HUD object - {{User|Celierra Darling}}
* {{jira|VWR-1721}} - Votes: 1 - GUI quirk in groups - {{User|Nicholaz Beresford}}
* {{jira|VWR-1730}} - Votes: 1 - After accepting texture or notecard, Keep/Discard options display again - {{User|Celierra Darling}}

== Pre-meeting activity ==

Some issues will be resolved in the course of building this agenda. Rather than deleting them from the proposed agenda, move the issue and associated discussion into the appropriate section below.

=== Imported ===

=== Resolved ===

Common compilation problems

2007-07-20T10:03:09Z

Nicholaz Beresford: /* Unresolved external symbol "int __cdecl lscript_compile" (VS2005) */

{{CompileNav}}

= General Problems =

* Make sure you download not only the source, but the artwork zipfile, and the appropriate zipfile/tarball of libraries for your platform

= Windows =

== Unresolved external symbol _CLSID_DxDiagProvider/_IID_IDxDiagProvider ==
* ''newview error LNK2001: unresolved external symbol _CLSID_DxDiagProvider''
* ''newview error LNK2001: unresolved external symbol _IID_IDxDiagProvider''

These errors reportedly occur with MSVC 2003 and certain versions of the DirectX SDK. To workaround, edit lldxhardware.cpp and replace the following (line 35):

#include <dxdiag.h>
with...
#define INITGUID
#include <dxdiag.h>
#undef INITGUID

== Cannot open input file 'dxguid.lib' ==
* ''fatal error LNK1181: cannot open input file 'dxguid.lib' in ...''

If you are using the most recent DirectX SDK ("December 2006"), your VC++ Libraries Directory may be wrong because the SDK's lib folder now has 2 sub-folders for x64 and x86. Try changing the path from ''C:\Program Files\Microsoft DirectX SDK (December 2006)\Lib'' to ''C:\Program Files\Microsoft DirectX SDK (December 2006)\'' '''Lib\x86'''
 
 
== Cannot open include file: 'ytab.h': No such file or directory ==
* ''indra.l (20) : fatal error C1083: Cannot open include file: 'ytab.h': No such file or directory.''
Workaround: Manually copy "linden\indra\lscript\lscript_compile\ytab.hpp" to "linden\indra\lscript\lscript_compile\ytab.h" and build again.

Note: The underlying issue is that in indra.y there is a postbuild step which should do this automatically, but which is missing in some configurations (e.g. in Debug builds).
 
 
== Cannot open include file: 'png.h': No such file or directory ==
* ''imagepng.cpp : fatal error C1083: Cannot open include file: 'libpng12/png.h': No such file or directory.''
There are a couple of files missing since the 1.17. distribution. You can either get the missing files from the internet (from the libpng and zlib projects) or download a set with just the missing files from [http://www.blueflash.cc/users/nicholaz/~libs here] (see the readme.txt inside the png archive there).
 
 

== Errors relating to "template_verifier.py" ==
With version 1.18 a template verifier script written in Python is used to ensure the message template is correct. In some distributions the file was missing. You will also get an error if you have skipped the Python install. In both cases it is safe to hack the prebuild.bat file in the newview folder as described on the JIRA [http://jira.secondlife.com/browse/VWR-1267 VWR-1267]
 
 

== Missing resources ==
* ''.\res\newViewRes.rc(64) : error RC2135 : file not found: ll_icon.ico''
Some releases have missing files, which were reported to be last seen in the '''1.14.0.1''' release.
* Go to the [[source downloads]] page and grab the [[http://secondlife.com/developers/opensource/downloads/2007/04/slviewer-src-1.14.0.1.zip '''1.14.0.1''' viewer]] sources.
* Explore the archive to "linden/indra/newview/res" folder and extract content to your "linden/indra/newview/res" folder into current revision.
Missing folder in recent release, "'''1.17.0.12'''" which causes the SecondLife to hang while loading into the world.
* Go to the previous source and copy the missing folder, "Character" and place it into the "newview" folder
 
== Error code from "Copying message template" ==
* ''newview error PRJ0019: A tool returned an error code from "Copying message template"''
This is caused by the script trying to do a copy command, but the source path isn't in quotes. Open up newview.vcproj in notepad, and near the bottom there are 4 line that say:
CommandLine="copy $(InputPath) .\app_settings\message_template.msg
replace them with
CommandLine="copy &quot;$(InputPath)&quot; .\app_settings\message_template.msg
The source and destination paths on line 158 may also require wrapping in quotes. In which case:
CommandLine="copy $(TargetDir)\$(TargetFileName) $(ProjectDir)
should become:
CommandLine="copy &quot;$(TargetDir)\$(TargetFileName)&quot; &quot;$(ProjectDir)&quot;
 
== Can not find library ll*.lib ==
If you get a compile error for missing libraries with names of the projects (lscript_compile.lib, llaudio.lib, llcharacter.lib, etc.) go to newview > Properties > Linker > Input and remove these from the list of input libraries (they will be linked through the dependencies and should not be in the list).
 
 
== Cannot open include file: 'windows.h' ==
If you run into this problem:
..\..\..\boost/regex/v4/fileiter.hpp(44) : fatal error C1083: Cannot open include file: 'windows.h': No such file or directory
Fix it with this: (thanks Fairlight!)
set INCLUDE=C:\Program Files\Microsoft Platform SDK for Windows Server 2003 R2\Include;%INCLUDE%
set LIB=C:\Program Files\Microsoft Platform SDK for Windows Server 2003 R2\Lib;%LIB%

 
== Unresolved external symbol "int __cdecl lscript_compile" (VS2005) ==
* ''llcompilequeue.obj : error LNK2019: unresolved external symbol "int __cdecl lscript_compile(char const *,char const *,char const *,int)" (?lscript_compile@@YAHPBD00H@Z) referenced in function "protected: void __thiscall LLFloaterCompileQueue::compile(char const *,class LLUUID const &)" (?compile@LLFloaterCompileQueue@@IAEXPBDABVLLUUID@@@Z)''
* ''llpreviewscript.obj : error LNK2001: unresolved external symbol "int __cdecl lscript_compile(char const *,char const *,char const *,int)" (?lscript_compile@@YAHPBD00H@Z)''

This is not entirely clear, but there seems to be a problem with VS2005 if projects are unloaded while being in the dependency tree. I have seen this error while I had win_crash_logger and win_updater unloaded from the project tree and the problem went away when I loaded them back and excluded them from the newview dependency first.

Also make sure that in newview, properties, linker, input, input libraries, no libraries named ll*.lib and lscript_compile.lib are listed there (remove them if you find them).
 
 

== Unresolved external symbol __invalid_parameter_noinfo (VS2005) ==
* ''llmozlib-vc80.lib(llembeddedbrowserwindow.obj) : error LNK2019: unresolved external symbol __invalid_parameter_noinfo referenced''

You are most likely trying a debug build under VS2005. For debug builds, see the compile instruction section on [[finding_leaks]]
 
 
== Other (older) notes ==
* Mozilla is not compatible with visual studio 2005, so we have not migrated the codebase, so we do not know if it works.

* Added my errors at [[User:Adam_Zaius/MSVS2005 Errors]] [[User:Adam Zaius|Adam Zaius]] 09:40, 8 January 2007 (PST)

* To minimize the number of warnings for now: in C/C++-Preprocessor add ';_CRT_SECURE_NO_DEPRECATE' to the Preprocessor Definitions, that will supress deprecation warnings --[[User:Artm Udal|Artm Udal]] 12:42, 8 January 2007 (PST)

 

= Mac OS X =

Getting:

*/linden/indra/newview/../llwindow/llglheaders.h:377:31: error: GL/glh_extensions.h: No such file or directory
** This means you didn't [[Compiling the viewer (Mac OS X)#Viewer Source, Libraries, and Artwork|merge the libraries]] right.

 

= Linux =

==== Packaging errors ====

The final packaging step may fail with errors about the manifest if you are not using the slviewer-linux-libs bundle; in this case, if you still wish to end up with an end-user viewer package incorporating your own libraries, you can edit the manifest file found at indra/newview/viewer_manifest.py

==== Various Compilation problems ====

* "Unable to initialize communications"
** If the viewer just displays the error message " Unable to initialize communications" and exits, it can't find message_template.msg. You did remember to copy it over, right?

* Blino's SL build/linking patches for '''gcc4''': http://svn.mandriva.com/cgi-bin/viewvc.cgi/packages/cooker/secondlife/current/
* objcopy: 'newview/linux_tools/exposed-symbols.txt': No such file
** Tofu says... 'This is an omission from our manifest which I'll fix. Meanwhile it's a safe fix to create an empty file with that name.'

* Something like: /usr/bin/ld: cannot find -lz
** Nadia says: Install the zlib development headers. (Ubuntu package zlib1g-dev, Red Hat zlib-devel.)

* Something like: indra.y.cpp:17: error: previous declaration of `int yyparse()'
** Tofu says... 'This appears to be a problem with some versions of flex/bison. A resident reports success when comment out the #ifdef __cplusplus lines in lscript/lscript_compile/indra.y'
** Nadia says: install the zlib development headers first and try recompiling. Commenting out those lines results in a error indra.l:666: undefined
* Linking failures ("script not found") due to spaces in the LINKFLAGS variable?
** I saw a [http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4665538 report], and modified the SConstruct file to drop the trailing arguments (and spaces) in LINKFLAGS.

* Building [https://lists.secondlife.com/pipermail/sldev/2007-January/000091.html 20070112a] using ''BUILD=releasefordownload'' I get many ''[: 89: ==: unexpected operator'' errors; ''cp: target `SecondLife_i686_1_13_1_7/app_settings/*’ is not a directory'' error, and same thing for character, fonts, help, skins, res-sdl; ''[: 111: ==: unexpected operator, [: 120: SecondLife_i686_1_13_1_7.tar.bz2: unexpected operator''. I can succesfully run the client from the source tree.
** i think this has been fixed --[[User:Signore Iredell|Signore Iredell]] 06:09, 9 June 2007 (PDT)

* scons: *** While building `['.../linden/indra/i686-linux-client-release/lscript/lscript_compile/indra.l.cpp']': Don't know how to build a file with suffix `.l'.
** You probably don't have all the dependencies installed (I had the same problem). Check that you have flex and bison. --[[User:Random73 Janus|Random73 Janus]] 07:43, 16 May 2007 (PDT)

* Something like: linden/indra/i686-linux-client-release/llrender/llimagegl.cpp:122: error: `glActiveTextureARB' was not declared in this scope
** Tofu says... 'You'll need to install OpenGL headers if you don't already have them: gl.h, glext.h, glu.h (The ones from 'mesa' should work)
** two residents report good luck on Gentoo after doing 'eselect opengl set xorg-x11' (but note!! You must know what you're doing; this may change your default system OpenGL drivers, and you will probably want to change them back again after the compile, e.g. 'eselect opengl set nvidia')'

*Building Shared Library ELFIO [[Compiling_the_viewer_%28Linux%29]] on AMD64 ubuntu 6.10
g++-3.4 -shared *.o -o libelfio.so
/usr/bin/ld: ELFIDynamic.o: relocation R_X86_64_32 against `a local symbol' can
not be used when making a shared object; recompile with -fPIC
ELFIDynamic.o: could not read symbols: Bad value'''

* Building Client on Ubuntu 7.04 AMD64
/usr/bin/ld: skipping incompatible /home/dereck/Desktop/SLdev/linden/libraries/i686-linux/lib_release_client/libopenjpeg.a when searching for -lopenjpeg
/usr/bin/ld: cannot find -lopenjpeg
collect2: ld returned 1 exit status
** I went to the OpenJPEG website, downloaded the source, compiled for my system, installed it. The VWR compile was happy after that. Although it's not done yet and I'm still fixing another error, that I assume is unrelated.

Talk:Bug triage/2007-10-23

2007-07-17T04:00:25Z

Nicholaz Beresford: Pasting invitation from sldev to discussion, need that to link to from my blog

== UI-Triage Invitation ==

Dear SL Devs,

I would just like to give you a heads up that the UI Triage Agenda for tomorrow (July 17, 2007) is up on the wiki (http://wiki.secondlife.com/wiki/Bug_triage/UI_Agenda#Other_Bug_Reports). Benjamin, Torley, and I will conduct the triage at 10am SLTime tomorrow. The slurl to Benjamin's office is listed on the wiki. Feel free to edit the Agenda as you see fit. For this particular triage, I organized by number of votes. You may certainly add issues that you think are important, issues I have failed to address this week.

It is our hope that you will seize control of the UI Triage Agenda in the spirit of Resident empowerment. That way, you dictate what goes on the agenda, not Linden Lab. For instructions on setting the agenda, please see http://wiki.secondlife.com/wiki/Bug_triage. Still have questions? Ping me.

Best,
Iridium Linden

Alternate viewers

2007-07-14T15:54:55Z

Nicholaz Beresford:

Alternate viewers

2007-07-14T15:54:06Z

Nicholaz Beresford:

Common compilation problems

2007-07-10T14:49:37Z

Nicholaz Beresford: template_verifyer.py (windows)

= General Problems =

= Windows =

== Unresolved external symbol _CLSID_DxDiagProvider/_IID_IDxDiagProvider ==
* ''newview error LNK2001: unresolved external symbol _CLSID_DxDiagProvider''
* ''newview error LNK2001: unresolved external symbol _IID_IDxDiagProvider''

These errors reportedly occur with MSVC 2003 and certain versions of the DirectX SDK. To workaround, edit lldxhardware.cpp and replace the following (line 35):

#include <dxdiag.h>
with...
#define INITGUID
#include <dxdiag.h>
#undef INITGUID

== Cannot open input file 'dxguid.lib' ==
* ''fatal error LNK1181: cannot open input file 'dxguid.lib' in ...''

If you are using the most recent DirectX SDK ("December 2006"), your VC++ Libraries Directory may be wrong because the SDK's lib folder now has 2 sub-folders for x64 and x86. Try changing the path from ''C:\Program Files\Microsoft DirectX SDK (December 2006)\Lib'' to ''C:\Program Files\Microsoft DirectX SDK (December 2006)\'' '''Lib\x86'''
 
 
== Cannot open include file: 'ytab.h': No such file or directory ==
* ''indra.l (20) : fatal error C1083: Cannot open include file: 'ytab.h': No such file or directory.''
Workaround: Manually copy "linden\indra\lscript\lscript_compile\ytab.hpp" to "linden\indra\lscript\lscript_compile\ytab.h" and build again.

Note: The underlying issue is that in indra.y there is a postbuild step which should do this automatically, but which is missing in some configurations (e.g. in Debug builds).
 
 
== Cannot open include file: 'png.h': No such file or directory ==
* ''imagepng.cpp : fatal error C1083: Cannot open include file: 'libpng12/png.h': No such file or directory.''
There are a cople of files missing since the 1.17. distribution. You can either get the missing files from the internet (from the libpng and zlib projects) or download a set with just the missing files from [http://www.blueflash.cc/users/nicholaz/~libs here] (see the readme.txt inside the png archive there).
 
 
== Errors relating to "template_verifier.py" ==
With version 1.18 a template verifier script written in Python is used to ensure the message template is correct. In some distributions the file was missing. You will also get an error if you have skipped the Python install. In both cases it is safe to hack the prebuild.bat file in the newview folder as described on the JIRA [http://jira.secondlife.com/browse/VWR-1267 VWR-1267]
 
 

== Missing resources ==
* ''.\res\newViewRes.rc(64) : error RC2135 : file not found: ll_icon.ico''
Some releases have missing files, which were reported to be last seen in the '''1.14.0.1''' release.
* Go to the [[source downloads]] page and grab the [[http://secondlife.com/developers/opensource/downloads/2007/04/slviewer-src-1.14.0.1.zip '''1.14.0.1''' viewer]] sources.
* Explore the archive to "linden/indra/newview/res" folder and extract content to your "linden/indra/newview/res" folder into current revision.
Missing folder in recent release, "'''1.17.0.12'''" which causes the SecondLife to hang while loading into the world.
* Go to the previous source and copy the missing folder, "Character" and place it into the "newview" folder
 
== Error code from "Copying message template" ==
* ''newview error PRJ0019: A tool returned an error code from "Copying message template"''
This is caused by the script trying to do a copy command, but the source path isn't in quotes. Open up newview.vcproj in notepad, and near the bottom there are 4 line that say:
CommandLine="copy $(InputPath) .\app_settings\message_template.msg
replace them with
CommandLine="copy &quot;$(InputPath)&quot; .\app_settings\message_template.msg
The source and destination paths on line 158 may also require wrapping in quotes. In which case:
CommandLine="copy $(TargetDir)\$(TargetFileName) $(ProjectDir)
should become:
CommandLine="copy &quot;$(TargetDir)\$(TargetFileName)&quot; &quot;$(ProjectDir)&quot;
 
== Can not find library ll*.lib ==
If you get a compile error for missing libraries with names of the projects (lscript_compile.lib, llaudio.lib, llcharacter.lib, etc.) go to newview > Properties > Linker > Input and remove these from the list of input libraries (they will be linked through the dependencies and should not be in the list).
 
 
== Cannot open include file: 'windows.h' ==
If you run into this problem:
..\..\..\boost/regex/v4/fileiter.hpp(44) : fatal error C1083: Cannot open include file: 'windows.h': No such file or directory
Fix it with this: (thanks Fairlight!)
set INCLUDE=C:\Program Files\Microsoft Platform SDK for Windows Server 2003 R2\Include;%INCLUDE%
set LIB=C:\Program Files\Microsoft Platform SDK for Windows Server 2003 R2\Lib;%LIB%

 
== Unresolved external symbol "int __cdecl lscript_compile" (VS2005) ==
* ''llcompilequeue.obj : error LNK2019: unresolved external symbol "int __cdecl lscript_compile(char const *,char const *,char const *,int)" (?lscript_compile@@YAHPBD00H@Z) referenced in function "protected: void __thiscall LLFloaterCompileQueue::compile(char const *,class LLUUID const &)" (?compile@LLFloaterCompileQueue@@IAEXPBDABVLLUUID@@@Z)''
* ''llpreviewscript.obj : error LNK2001: unresolved external symbol "int __cdecl lscript_compile(char const *,char const *,char const *,int)" (?lscript_compile@@YAHPBD00H@Z)''

This is not entirely clear, but there seems to be a problem with VS2005 if projects are unloaded while being in the dependency tree. I have seen this error while I had win_crash_logger and win_updater unloaded from the project tree and the problem went away when I loaded them back and excluded them from the newview dependency first.
 
 
== Unresolved external symbol __invalid_parameter_noinfo (VS2005) ==
* ''llmozlib-vc80.lib(llembeddedbrowserwindow.obj) : error LNK2019: unresolved external symbol __invalid_parameter_noinfo referenced''

You are most likely trying a debug build under VS2005. For debug builds, see the compile instruction section on [[finding_leaks]]
 
 
== Other (older) notes ==
* Mozilla is not compatible with visual studio 2005, so we have not migrated the codebase, so we do not know if it works.

* Added my errors at [[User:Adam_Zaius/MSVS2005 Errors]] [[User:Adam Zaius|Adam Zaius]] 09:40, 8 January 2007 (PST)

* To minimize the number of warnings for now: in C/C++-Preprocessor add ';_CRT_SECURE_NO_DEPRECATE' to the Preprocessor Definitions, that will supress deprecation warnings --[[User:Artm Udal|Artm Udal]] 12:42, 8 January 2007 (PST)
 
 
 

= Mac OS X =

Getting:

*/linden/indra/newview/../llwindow/llglheaders.h:377:31: error: GL/glh_extensions.h: No such file or directory
** This means you didn't merge the libraries right.
 
 
 
= Linux =

==== Packaging errors ====

The final packaging step may fail with errors about the manifest if you are not using the slviewer-linux-libs bundle; in this case, if you still wish to end up with an end-user viewer package incorporating your own libraries, you can edit the manifest file found at indra/newview/viewer_manifest.py

==== Various Compilation problems ====

* "Unable to initialize communications"
** If the viewer just displays the error message " Unable to initialize communications" and exits, it can't find message_template.msg. You did remember to copy it over, right?

* Blino's SL build/linking patches for '''gcc4''': http://svn.mandriva.com/cgi-bin/viewvc.cgi/packages/cooker/secondlife/current/
* objcopy: 'newview/linux_tools/exposed-symbols.txt': No such file
** Tofu says... 'This is an omission from our manifest which I'll fix. Meanwhile it's a safe fix to create an empty file with that name.'

* Something like: /usr/bin/ld: cannot find -lz
** Nadia says: Install the zlib development headers. (Ubuntu package zlib1g-dev, Red Hat zlib-devel.)

* Something like: indra.y.cpp:17: error: previous declaration of `int yyparse()'
** Tofu says... 'This appears to be a problem with some versions of flex/bison. A resident reports success when comment out the #ifdef __cplusplus lines in lscript/lscript_compile/indra.y'
** Nadia says: install the zlib development headers first and try recompiling. Commenting out those lines results in a error indra.l:666: undefined
* Linking failures ("script not found") due to spaces in the LINKFLAGS variable?
** I saw a [http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4665538 report], and modified the SConstruct file to drop the trailing arguments (and spaces) in LINKFLAGS.

* Building [https://lists.secondlife.com/pipermail/sldev/2007-January/000091.html 20070112a] using ''BUILD=releasefordownload'' I get many ''[: 89: ==: unexpected operator'' errors; ''cp: target `SecondLife_i686_1_13_1_7/app_settings/*’ is not a directory'' error, and same thing for character, fonts, help, skins, res-sdl; ''[: 111: ==: unexpected operator, [: 120: SecondLife_i686_1_13_1_7.tar.bz2: unexpected operator''. I can succesfully run the client from the source tree.
** i think this has been fixed --[[User:Signore Iredell|Signore Iredell]] 06:09, 9 June 2007 (PDT)

* scons: *** While building `['.../linden/indra/i686-linux-client-release/lscript/lscript_compile/indra.l.cpp']': Don't know how to build a file with suffix `.l'.
** You probably don't have all the dependencies installed (I had the same problem). Check that you have flex and bison. --[[User:Random73 Janus|Random73 Janus]] 07:43, 16 May 2007 (PDT)

* Something like: linden/indra/i686-linux-client-release/llrender/llimagegl.cpp:122: error: `glActiveTextureARB' was not declared in this scope
** Tofu says... 'You'll need to install OpenGL headers if you don't already have them: gl.h, glext.h, glu.h (The ones from 'mesa' should work)
** two residents report good luck on Gentoo after doing 'eselect opengl set xorg-x11' (but note!! You must know what you're doing; this may change your default system OpenGL drivers, and you will probably want to change them back again after the compile, e.g. 'eselect opengl set nvidia')'

*Building Shared Library ELFIO [[Compiling_the_viewer_%28Linux%29]] on AMD64 ubuntu 6.10
g++-3.4 -shared *.o -o libelfio.so
/usr/bin/ld: ELFIDynamic.o: relocation R_X86_64_32 against `a local symbol' can
not be used when making a shared object; recompile with -fPIC
ELFIDynamic.o: could not read symbols: Bad value'''

* Building Client on Ubuntu 7.04 AMD64
/usr/bin/ld: skipping incompatible /home/dereck/Desktop/SLdev/linden/libraries/i686-linux/lib_release_client/libopenjpeg.a when searching for -lopenjpeg
/usr/bin/ld: cannot find -lopenjpeg
collect2: ld returned 1 exit status
** I went to the OpenJPEG website, downloaded the source, compiled for my system, installed it. The VWR compile was happy after that. Although it's not done yet and I'm still fixing another error, that I assume is unrelated.

Compiling the viewer (MSVS2005)

2007-07-10T14:37:39Z

Nicholaz Beresford: other build tools (python)

{{CompileNav}}

This page explains how you can compile the viewer on Microsoft Windows using Visual Studio 2005 or Visual C++ Express 2005. Note that Lindens are using VS2003 and the whole setup is a bit easier there, so if you have Visual Studio 2003 available, you should read [[Compiling the viewer (MSVS2003)|compiling with VS2003]] and you will get less trouble with it than with VS2005.

The following explanation is adjusted for Viewer releases 1.16.0.5 or later. See an [http://wiki.secondlife.com/w/index.php?title=Compiling_the_viewer_%28MSVS2005%29&oldid=22294 older version of this page] for the Viewer releases 1.15 or before.

= Preparing the Development Environment =

== Installing/Configuring VS2005 ==

You need to setup the compiler and Microsoft Development tools as follows:
* Visual Studio 2005 '''''-or-''''' [http://msdn.microsoft.com/vstudio/express/visualc/download/ Visual C++ 2005 Express](Free) (Also, although not strictly necessary, eventually pick up and install SP1 for VS2005.)
* [http://www.microsoft.com/downloads/details.aspx?familyid=0BAF2B35-C656-4969-ACE8-E4C0C0716ADB&displaylang=en Microsoft Platform SDK]
* A DirectX 9.0 SDK released on or after Summer of 2003 [http://download.microsoft.com/download/5/1/f/51ff8357-0af3-418b-9d0b-e9a5cdc39759/dxsdk_dec2006.EXE DirectX 9.0 SDK (December 2006)] [http://www.microsoft.com/downloads/details.aspx?FamilyID=9216652f-51e0-402e-b7b5-feb68d00f298&displaylang=en DirectX 9.0 SDK Update (Summer 2003)]
: '''Note''': If you have previously installed an older version of the DirectX 9.0 SDK, remove it first (from Control Panel -> Add or Remove Programs) before installing this version. Installing the new SDK "on top" of an older version may cause problems.
* Set up the project globals:
** Start Microsoft Visual Studio 2005
** Go to Tools > Options > Projects > VC++ Directories
** Make sure that the '''includes''' ([[:Image:MSVS2005 Global Project Options Include Files.JPG|'''screen shot''']]) and '''libraries''' ([[:Image:MSVS2005 Global Project Options Library Files.JPG|'''screen shot''']]) paths have the Platform SDK paths first, then the DirectX SDK paths, and then the Visual C++ paths. You may need to check "Show All Settings" at the bottom for VC++ Directories to show.
** If the DirectX SDK paths aren't present, add them to both '''includes''' and '''libraries'''.
*: Note: The newest DirectX SDK ("December 2006") lib folder has two sub-folders, x64 and x86. Make sure your path goes to one of them (select '''lib/x86''', not just '''lib'''), or you will get a Link error.
 

== Getting other Development Tools ==
You will also need some open source development tools.
* [http://www.cygwin.com/ 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. The project files use several hardcoded references that expect Cygwin to be installed at '''C:\cygwin''', if it's not you'll need to edit those references.
* [http://www.activestate.com/Products/ActivePython/?mp=1 ActivePython 2.3x or later] - Latest Version is 2.5.1.1
** You should install this if compiling 1.18 or later viewers, or if you want to avoid it, hack the prebuild.bat files as in [http://jira.secondlife.com/browse/VWR-1267 VWR-1267].
* ActivePerl was recommended for previous versions on this Wiki, but it currently appears, that it is not strictly necessary unless you are planning to build your own version of all libraries (which most likely you don't want to do). So for a start it may be safe to skip it.
*: [http://www.activestate.com/Products/ActivePerl/?mp=1 ActivePerl]

 
 
 
= Downloading Source Code =

You can download the Viewer source codes on the [[source downloads]] page. You can also use a [[version control repository]].

At a minimum, grab the source package and the artwork package, but for a start, also grab the library archive. Many of the libraries can either be compiled from source or downloaded from other sites (see below), but this will take hours and thus it is easiest to also get the package with libraries compiled by the Lindens.

'''WARNING:'''
* If the directory path you keep the SL source in has a space in it, the batch file that copies message_template.msg will fail. So, if you unzip or checkout the source tree into, e.g., "C:\Projects\Dir with space in name\Etc\linden", it won't work!
* You should also avoid using non-ASCII (national) characters in the paths, although some localized versions of the tool puts some as a default...
* Unzip or checkout your source tree into a directory that has as short full pathname as possible, since long paths cause some unexpected trouble during the build.

In other words, the easiest way to get this working is to get ''source'', ''artwork'' and ''libraries'' from the [[source downloads]] page and unpack them all into the same directory/folder, which ideally would be a folder in (or near) the root directory with a short name like ''sl_1_16_0_5''.
 
 
 
 

= Installing Libraries =

SL Viewer depends on some third party libraries. Some of them are open source, some others are not.

== Open Source Libraries ==

You can download the pre-build open source libraries from LL. They are available on [[source downloads]] page. Unzip them into your SL viewer source code directory, maintaining the same directory structure.

Alternatively, it may be possible to get the source files for the libraries and build by yourself. See [[Compiling the viewer libraries (MSVS 2003)|the instruction for VS2003 users]] if you try it. Please note, however, it is not known that VS2005 can successfully compile the libraries. '''You have been warned.''' (If you can make it, please write the info on this wiki...)
 
 
== Proprietary Libraries ==

Lindens does not inlcude the following proprietary libraries. You will need to follow the instructions to acquire below and copy them to the source path.

However, it probably is 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 (like ''XCOPY OLIB SL_1_16_0_5 /S''). The reason is, that these steps are cumbersome and will have to be repeated for each new release (at least if you keep the source for each release in it's own folder). If you do not want to do this, of course you can just copy the files directly into the linden source paths.

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
 
=== Fmod ===
* Download & extract [http://www.fmod.org/ifmoddownload.html fmod 3.75 api for win32] (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\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"
 
=== OpenGL ===
* Download [http://oss.sgi.com/projects/ogl-sample/sdk.html glext.h, glxext.h, and wglext.h]
* Copy them to "linden\libraries\i686-win32\include\GL"
* You don't need any additional *.lib or *.dll for OpenGL.
 
=== Quicktime ''(optional)'' ===
'''Note:''' that you can avoid using QuickTime if you want. See [[#QuickTime removal|below]] for details. Remember that your viewer '''can't play in-world movies''' if you do so.
* Download & install the [http://connect.apple.com/cgi-bin/WebObjects/MemberSite.woa/203/wa/getSoftware?fileID=20525&code=y&source=x&wosid=4h16WcyMtVfd2P1EffGafkoxFcr 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".
 
 
 
= Configuring for VS2005 =

Lindens use VS2003 to develop the viewer.

You either need to convert ''solution file'' and ''project files'' from VS2003 format to VS2005 format or obtain files compatible with VS2005. You may also need to modify source files to work around the incompatibility between VS2003 and VS2005.

'''Note''': linden\indra\indra_complete_vs8.sln is a solution file already included in the source archive and intended for the Visual Studio 2005, but it '''does not work''' (at least between 1.14.0 and 1.17.0.9 distribution). This may change in a future release, if Lindens include an updated versions of the '''_vc8''' files.

 
 
== Using pre-built solution/project files ==

Currently there is a ZIP file with solution/project files available on the [https://jira.secondlife.com/browse/VWR-1151 JIRA bug tracker issue VWR-1151].

If you are building 1.16 or 1.17, most likely the easiest way towards compiling SL on MS2005 will be to:
* download the ZIP archive there
* unpack it and copy it onto your linden source tree (allow to overwrite files that have '''_vc8''' in the name).
* start Visual Studio 2005 (or VC++ Express).
* use "File > Open > Project/Solution" to open the linden\indra\indra_complete\indra_complete'''_vc8'''.sln (Note: If you plan to work with multiple versions over time, you will find it useful to rename '''indra_complete_vc8.sln''' to something which contains the version number, e.g. '''indra_1_17_0_11_vc8.sln''' before opening)
* right click '''newview''' in the frame Solution Explorer and click "Set as StartUp Project".
* proceed with applying the '''Workarounds''' below (skip '''Manual conversion''').

'''Note:''' If, while compiling, you later encounter errors or problems regarding the projects, you may have to do the manual conversion instead.

 
 

== Manual conversion of the solution/projects ==

If you can not find a set of project files (see above), there are instructions available how to manually do it: [[Converting_project_files_for_MSVS2005]]

 
 
 

== Workarounds ==

There are more compatibility problems between VS2003 and VS2005. You need the following code edits.
 
=== test project/crash_logger/updater ===

For whatever reason, the '''test''' project doesn't work under VS2005. Workaround is to disable it as follows: Right click on the '''test''' and choose '''Unload Project'''.

If you do not plan to create a full download build, you can exclude the '''win_crash_logger''' and '''win_updater''' from newview's project dependencies and unload them also. But be careful with unloading these projects without removing them from the dependencies, because I have seen VS2005 act highly erratic while linking then project when I tried this.
 
=== QuickTime removal ===

If you don't want to get Apple QuickTime SDK, you can disable it as follows:
*linden\indra\llcommon\llpreprocessor.h - near line 58 (the line below '''#elif LL_WINDOWS''')
--50: #define LL_QUICKTIME_ENABLED 1
++50: #define LL_QUICKTIME_ENABLED '''''0'''''

* Pick '''ReleaseNoOpt''' in the Solution Configurations drop-down box beside the green arrow under the tool bar, and do the followings on the Solution Explorer frame:
*Click '''newview''' to select it alone.
**Choose Properties.
**Under Configuration Properties > Linker > Input, click '''Additional Dependencies''' on the right to show a button labeled "'''...'''" on it at the very right on the line, then click the '''...''' button.
**Scroll down the list to find '''qtmlclient.lib'''. Delete this single line.
**Click '''OK''' to close the "Additional Dependencies" dialog, then click OK again to close the "newview Property Pages" dialog box.
* Pick '''ReleaseForDownload''' in the Solution Configurations drop-down box. Click '''newview''' to select it alone and do the same thing again.
 
 
 
= Ready, Set, Build! =

== Building ==
* Build either '''ReleaseNoOpt''' (for debugging) or '''ReleaseForDownload''' (for production code).
* To do this, pick either in the Solution Configurations drop-down box beside the green arrow under the tool bar.
* Make sure '''newview''' is set as the active project (otherwise set from newview's right-click menu).
* Select Build-Menu > Build Solution or press F7.
* newview_noopt.exe will be built in linden\indra\newview\ReleaseNoOpt or SecondLife.exe will be linden\indra\newview\ReleaseForDownload.
 
== Common compile errors ==
* See [[Common compilation problems]] if you run into other errors while building.
 
== Running ==
* You can run the viewer by '''Debug > Start Debugging''' or '''Debug > Start "Without Debugging''' in Visual Studio.
* To run it outside VS, create a shortcut to SecondLife.exe, and change the start location to linden\indra\newview\ (all the .dll will be found there.)
* Alternately copy the exe (possibly rename it) to your "c:\program files\second life" folder.
 
== Debugging Info/Configurations ==
* Usually you will either use '''ReleaseNoOpt''' or the '''ReleaseForDownload''' configuration.
* '''ReleaseNoOpt''' compiles faster and has more debugging information, but this comes at a runtime penalty of about 50% of your FPS in busy areas, compared to ReleaseForDownload build.
* '''ReleaseForDownload''' also has debugging information and runs fine in the debugger (although at times you may miss access to some local variables).
* '''ReleaseNoOpt''' comes with a seperate debugging console window opens and stays open for the duration of your session, but you can access the same information also by pressing Shift+Ctrl+4 in the viewer (all builds).
* The debug console log can also be redirected to a file if you add "2>secondlife.log" to the command line (Newview, Properties, Debugging, Command line arguments).
* If you want to build a '''Debug''' configuration, see the specific section with compile instructions on [[Finding_leaks]]
 

== Problems Running? ==
* '''Inventory errors''': If you're getting errors while trying to load your inventory, try [[Help:Stuck logging in|clearing your cache and deleting other temporary files]].
* '''Missing smime3 DLL''': Those are parts of the integrated web browser. Copy 'smime3.dll', 'nss3.dll', 'softokn3.dll', and 'ssl3.dll' files from your official client's main folder to "linden\indra\newview".
* '''Can't connect''': In the debug builds there is a selection box on the login screen to select the server to connect to. '''Agni''' is the production grid, '''aditi''' is the beta grid. (There seems to be a bug in this part of the code, you may have to make your selection, close the viewer and repoen it, before you can connect to the selected grid).
 
 
= Submit Patches =
This is probably faaar down the road, but if you make changes to the source and want to submit them, see the page about [[Submitting patches|submitting patches]].

Compiling the viewer (MSVS2003)

2007-07-10T14:35:51Z

Nicholaz Beresford:

{{CompileNav}}

The following instructions are for compiling the Second Life viewer on Windows for Visual Studio .Net 2003. If you are using more recent versions of Visual Studio, see [[Compiling the viewer (MSVS2005)]]. For other platforms including MacOS and Linux, see [[Compiling the viewer]].

If you get lost, or these instructions are incomplete, see [[communication tools]] for a list of ways to get in touch with people that can help.
 
 
== Development Environment ==
The following dev environment is what LL uses for Windows development. There is no reason that the Second Life viewer can not be built using other environments, but it will take some extra work.

(Instructions for building the viewer using Microsoft's Visual Studio .NET 2005 Express can be found [[Compiling the viewer (MSVS2005)|on another page]]. At the time of writing, Express was freely available.)
 
=== Visual Studio .NET 2003 Professional ===
* Download and install [http://www.microsoft.com/downloads/details.aspx?familyid=0BAF2B35-C656-4969-ACE8-E4C0C0716ADB&displaylang=en Microsoft Platform SDK]
* Download and install a DirectX 9.0 SDK released on or after Summer of 2003 [http://download.microsoft.com/download/5/1/f/51ff8357-0af3-418b-9d0b-e9a5cdc39759/dxsdk_dec2006.EXE DirectX 9.0 SDK (December 2006)] [http://www.microsoft.com/downloads/details.aspx?FamilyID=9216652f-51e0-402e-b7b5-feb68d00f298&displaylang=en DirectX 9.0 SDK Update (Summer 2003)]
** If you have previously installed an older version of the DirectX 9.0 SDK, remove it first (from Control Panel -> Add or Remove Programs) before installing this version. Installing the new SDK "on top" of an older version may cause problems.
** Upon installing, it is sufficient to install the '''include''' and '''libraries''' part. Other DX development tools are not necessary.
* Set up the project globals:
** Start Visual C++
** Go to Tools/Options/Projects/VC++ Directories
** Make sure that the '''includes''' and '''libraries''' paths are there (or otherwise add them) in the following order: 1) Platform SDK paths, 2) DirectX SDK paths, 3) Visual C++ paths
** If you are adding DirectX SDK paths, be aware that later versions of the DirectX SDK have subfolders inside the lib directory. With those make sure you select '''lib/x86''', not just '''lib'''.

=== Other Development Tools ===
You will also need some open source development tools.
* [http://www.cygwin.com/ 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. The project files use several hardcoded references that expect Cygwin to be installed at '''C:\cygwin''', if it's not you'll need to edit those references.
* [http://www.activestate.com/Products/ActivePython/?mp=1 ActivePython 2.3x or later] - Latest Version is 2.5.1.1
** You should install this if compiling 1.18 or later viewers, or else hack the prebuild .bat files as in [http://jira.secondlife.com/browse/VWR-1267 VWR-1267].
* ActivePerl was recommended for previous versions on this Wiki, but it currently appears, that it is not strictly necessary unless you are planning to build your own version of all libraries (which most likely you don't want to do). So for a start it may be safe to skip it.
*: [http://www.activestate.com/Products/ActivePerl/?mp=1 ActivePerl]
 
 
 

== Source Code ==
The easiest way to get this working is to get '''source''', '''artwork''' and '''libraries''' for the same version from the [[source downloads]] page and unpack them all into the same directory/folder, which ideally would be a folder in (or near) the root directory with a short name like ''sl_1_16_0_5''.
'''Note:''' Avoid folder names with spaces in them (this means avoid putting the project into your ''My Documents'' folder).
 
 
 
== Open Source Libraries ==

Some libraries can be distributed with the SL source and there is a library package available with the source. As mentioned above (about the source), you can simply extract the '''library''' archive and copy the files to your code directory, maintaining the same directory structure.

If instead you are interested in compiling these libraries from their source (instead of using the above zipfile of precompiled libraries provided by Linden Lab), see [[Compiling the viewer libraries (MSVS 2003)]]
 
 
== Other Libraries ==

Linden Lab included all the libraries/includes they can ship with their source, but we can not distribute the source to the following , and you will need to follow the instructions to acquire below.

However, it probably is 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 (like ''XCOPY olibs sl_1_16_0_5 /S''). The reason is, that these steps are cumbersome and will have to be repeated for each new release (at least if you keep the source for each release in it's own folder).

If you do not want to do this, of course you can just copy the files directly into the linden source paths.

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

==== Fmod ====
* Download & extract [http://www.fmod.org/ifmoddownload.html fmod 3.75 api for win32].
* Copy "fmodapi375win\api\inc\fmod.h" to "linden\libraries\include"
* Copy "fmodapi375win\api\inc\fmod_errors.h" to "linden\libraries\include"
* Copy "fmodapi375win\api\lib\fmodvc.lib" to "linden\libraries\i686-win32\lib_release"
* Copy "fmodapi375win\api\lib\fmodvc.lib" to "linden\libraries\i686-win32\lib_debug"
* Copy "fmodapi375win\api\fmod.dll" to "linden\indra\newview"

==== gl ====
* Download [http://oss.sgi.com/projects/ogl-sample/sdk.html glext.h, glxext.h, and wglext.h]
* Copy them to "linden\libraries\i686-win32\include\GL"

==== Quicktime (Optional) ====
* '''Note:''' Quicktime download can be skipped '''if you can live with a build that does not play in-world movies''' (some minor modifications to the project are necessary then, see "QuickTime removal" on the build instructions for [[Compiling the viewer (MSVS2005)|Visual Studio 2005]]).
* Download & install the [http://developer.apple.com/quicktime/download/ Quicktime SDK for Windows]
* Copy "QuicktimeSDK\Libraries\QTMLClient.lib" to "linden\libraries\i686-win32\lib_release".
* Copy "QuicktimeSDK\Libraries\QTMLClient.lib" to "linden\libraries\i686-win32\lib_debug".
* Copy the contents of "QuicktimeSDK\CIncludes" into "linden\libraries\i686-win32\include\quicktime".
 
 
== Building ==
* Open the '''indra\indra_complete\indra_complete.sln''' solution in Visual Studio (Note: If you plan to work with multiple versions over time, you will find it useful to rename '''indra_complete.sln''' to something which contains the version number, e.g. '''indra_1_17_0_11.sln''' before opening)
* Set newview to be the startup project.
* Build either '''ReleaseNoOpt''' (for debugging) or '''ReleaseForDownload''' (for running/debugging production code).
* Note that the ReleaseForDownload build also contains debug information and can be run in the debugger.
* newview_noopt.exe will be built in \indra\newview\ReleaseNoOpt, or SecondLife.exe will be built in \indra\newview\ReleaseForDownload
* To run it outside VS, create a shortcut to SecondLife.exe, and change the start location to linden\indra\newview\ (all the .dll will be found there.)
* Alternately copy the exe (possibly rename it) to your "c:\program files\second life" folder.
* There were additional steps required in version 1.15 which seem to be fixed now. If you are trying to build 1.15 see an [https://wiki.secondlife.com/w/index.php?title=Compiling_the_viewer_%28MSVS2003%29&oldid=23026 older version of this page].
 
 

== Errors while building? ==
See [[Common compilation problems]] if you run into errors while building.
 
 
 
== Configurations/Debugging Info ==
* You will usually compile/debug the '''ReleaseNoOpt''' or ReleaseForDownload configuration (Debug should also work but should not really be necessary).
* '''ReleaseNoOpt''' compiles faster and has more debugging information, but this comes at a runtime penalty of about 50% of your FPS in busy areas, compared to ReleaseForDownload build.
* '''ReleaseForDownload''' runs fine in the debugger, but times you may miss debugger access to some local variables.
* '''ReleaseNoOpt''' comes with a seperate debugging console window opens and stays open for the duration of your session
* You can see the last few lines from the debugger console also by pressing Shift+Ctrl+4 in the viewer (all builds).
* The debug log can also be redirected to a file if you add "2>secondlife.log" to the command line (Newview, Properties, Debugging, Command line arguments).
* If you want to build a '''Debug''' configuration, see the specific section with compile instructions on [[Finding_leaks]]
 
 
== Problems Running? ==
* '''Can't connect''': In the debug builds there is a selection box on the login screen to select the server to connect to. '''Agni''' is the production grid, '''aditi''' is the beta grid. (There seems to be a bug in this part of the code, you may have to make your selection, close the viewer and repoen it, before you can connect to the selected grid).
* '''Inventory errors''': If you're getting errors while trying to load your inventory, try [[Help:Stuck logging in|clearing your cache and deleting other temporary files]].
* '''Missing smime3 DLL''': Those are parts of the integrated web browser. Copy 'smime3.dll', 'nss3.dll', 'softokn3.dll', and 'ssl3.dll' files from your official client's main folder to "linden\indra\newview".
 
 
== Submit Patches ==
This is probably far down the road, but if you make changes to the source and want to submit them, see the page about [[Submitting patches|submitting patches]].

Crash Reports

2007-07-09T23:13:34Z

Nicholaz Beresford:

{{OSWikiContribBox}}

The easiest way to get involved as a developer is to start fixing bugs. These are the crash reports for which patches are most likely to be accepted.

== Call stacks for Top 10 Viewer crashes ==

=== boost::intrusive_ptr_release ===
Bug tracking: 
There are 1348 unassociated crashes like this: 
'''Note:''' Most likely already fixed (at least internally): {{jira|VWR-1436}} [[User:Nicholaz Beresford|Nicholaz]] 16:13, 9 July 2007 (PDT)
<pre>
SecondLife!boost::intrusive_ptr_release+0x8
SecondLife!LLEventPoll::Impl::stop+0xd2
SecondLife!LLEventPoll::`scalar deleting destructor'+0x11
SecondLife!LLViewerRegion::~LLViewerRegion+0xb6
SecondLife!std::for_each<std::list<LLViewerRegion *,std::allocator<LLViewerRegion *> >::iterator,DeletePointer>+0x1e
SecondLife!LLWorld::~LLWorld+0x4a
SecondLife!disconnect_viewer+0x1d1
SecondLife!cleanup_app+0x3e
SecondLife!WinMain
</pre>

=== LLXMLRPCTransaction::Impl::init ===
Bug tracking: https://jira.secondlife.com/browse/VWR-587 
There are 496 unassociated crashes like this: 
<pre>
SecondLife!Curl_hash_init+0x4c
SecondLife!Curl_hash_alloc+0x22
SecondLife!Curl_mk_dnscache+0xc
SecondLife!curl_multi_init+0x1f
SecondLife!LLXMLRPCTransaction::Impl::init+0x378
SecondLife!LLXMLRPCTransaction::Impl::Impl+0xb1
SecondLife!LLXMLRPCTransaction::LLXMLRPCTransaction+0x4c
SecondLife!LLUserAuth::authenticate+0x583
SecondLife!idle_startup+0x33fa
SecondLife!idle+0x12d
SecondLife!main_loop+0x1ca
</pre>

=== LLRenderPass::pushBatch ===
Bug tracking: https://jira.secondlife.com/browse/VWR-586 
There are 473 unassociated crashes like this: 
<pre>
SecondLife!LLRenderPass::pushBatch+0xa5
SecondLife!LLRenderPass::renderTexture+0x2d
SecondLife!LLDrawPoolSimple::render+0x99
SecondLife!LLPipeline::renderGeom+0x49f
SecondLife!display+0x944
SecondLife!main_loop+0x22b
</pre>

=== LLWindowWin32::close ===
Bug tracking: https://jira.secondlife.com/browse/VWR-590 
There are 368 unassociated crashes like this: 
<pre>
user32!InternalCallWinProc+0x28
user32!UserCallWinProcCheckWow+0x150
user32!DispatchClientMessage+0xa3
user32!__fnDWORD+0x24
ntdll!KiUserCallbackDispatcher+0x13
user32!NtUserShowWindow+0xc
SecondLife!LLWindowWin32::close+0x426
SecondLife!LLWindowManager::destroyWindow+0x96
SecondLife!LLViewerWindow::~LLViewerWindow+0x39a
SecondLife!LLViewerWindow::`scalar deleting destructor'+0x8
SecondLife!cleanup_app+0x84a
SecondLife!WinMain
</pre>

=== LLUserAuth::authenticate ===
Bug tracking: 
There are 357 unassociated crashes like this: 
<pre>
SecondLife!LLUserAuth::authenticate+0x550
SecondLife!idle_startup+0x33fa
SecondLife!idle+0x12d
SecondLife!main_loop+0x1ca
</pre>

=== LLImageBase::allocateData ===
Bug tracking: 
There are 319 unassociated crashes like this: 
<pre>
SecondLife!LLError::crashAndLoop
SecondLife!LLError::Log::flush+0x4f1
SecondLife!first_mem_error_handler+0xa0
SecondLife!_shi_invokeErrorHandler1+0xe7
SecondLife!_shi_allocExternal+0x78
SecondLife!MemAllocPtr+0x121
SecondLife!shi_New+0x48
SecondLife!operator new+0xe
SecondLife!LLImageBase::allocateData+0x1b8
SecondLife!LLImageRaw::allocateData+0xd
SecondLife!LLImageRaw::LLImageRaw+0x5d
SecondLife!LLImageWorker::doWork+0xc4
SecondLife!LLWorkerThread::WorkRequest::processRequest+0x1c
SecondLife!LLQueuedThread::processNextRequest+0x17c
SecondLife!LLQueuedThread::run+0x36
SecondLife!LLThread::staticRun+0x2a
SecondLife!_flswbuf+0x14d
SecondLife!_threadstartex+0x6f
kernel32!BaseThreadStart+0x37
</pre>

=== LLVolume::sculpt ===
Bug tracking: 
There are 244 unassociated crashes like this: 
<pre>
SecondLife!LLVolume::sculpt+0x225
SecondLife!LLVOVolume::sculpt+0xe8
SecondLife!LLVOVolume::setVolume+0x1b2
SecondLife!LLVOVolume::updateGeometry+0x19c
SecondLife!LLDrawable::updateGeometry+0x13
SecondLife!LLPipeline::updateGeom+0x278
SecondLife!display+0x86e
SecondLife!main_loop+0x22b
</pre>

=== LLRenderPass::pushBatch ===
Bug tracking: https://jira.secondlife.com/browse/VWR-586 
There are 198 unassociated crashes like this: 
<pre>
nvoglnt
SecondLife!LLRenderPass::pushBatch+0xa5
SecondLife!LLRenderPass::renderTexture+0x2d
SecondLife!LLDrawPoolSimple::render+0x99
SecondLife!LLPipeline::renderGeom+0x49f
SecondLife!display+0x944
SecondLife!main_loop+0x22b
</pre>

=== LLRenderPass::pushBatch ===
Bug tracking: https://jira.secondlife.com/browse/VWR-586 
There are 177 unassociated crashes like this: 
**Probably a twin of the above, different GL driver** 
<pre>
atioglxx
SecondLife!LLRenderPass::pushBatch+0xa5
SecondLife!LLRenderPass::renderTexture+0x2d
SecondLife!LLDrawPoolSimple::render+0x99
SecondLife!LLPipeline::renderGeom+0x49f
SecondLife!display+0x944
SecondLife!main_loop+0x22b
</pre>

=== LLProfile::~LLProfile ===
Bug tracking: 
There are 170 unassociated crashes like this: 
<pre>
SecondLife!MemFreePtr+0x17
SecondLife!free+0xe
SecondLife!LLProfile::~LLProfile+0x5e
SecondLife!LLVolume::~LLVolume+0x7c
SecondLife!LLVolume::`scalar deleting destructor'+0x8
SecondLife!LLPointer<LLVolume>::unref+0x34
SecondLife!LLVOVolume::updateGeometry+0x27c
SecondLife!LLDrawable::updateGeometry+0x13
SecondLife!LLPipeline::updateGeom+0x278
SecondLife!display+0x86e
SecondLife!main_loop+0x22b
</pre>

== Call stacks for Top 5 Mac-specific crashes ==

=== LLImageGL::~LLImageGL ===
Bug tracking: 
<pre>
SecondLife!std::_Rb_tree<LLImageGL*, LLImageGL*, std::_Identity<LLImageGL*>, std::less<LLImageGL*>, std::allocator<LLImageGL*> >::lower_bound(LLImageGL* const&)+20
SecondLife!LLImageGL::~LLImageGL [in-charge deleting]()+556
SecondLife!__tcf_433+80
SecondLife!cxa_atexit_wrapper+172
libSystem.B.dylib!__cxa_finalize+232
libSystem.B.dylib!exit+36
SecondLife!viewer_crash_callback()+1700
libSystem.B.dylib!_sigtramp+104
libSystem.B.dylib!kill+12
libSystem.B.dylib!abort+92
libstdc++.6.dylib!_gnu_cxx::__verbose_terminate_handler()+412
libstdc++.6.dylib!__gxx_personality_v0+1244
libstdc++.6.dylib!std::terminate()+72
libstdc++.6.dylib!__cxa_rethrow+0
libstdc++.6.dylib!std::__throw_domain_error(char const*)+0
libstdc++.6.dylib!char* std::basic_string<char, std::char_traits<char>, std::allocator<char> >::_S_construct<char const*>(char const*, char const*, std::allocator<char> const&, std::forward_iterator_tag)+96
libstdc++.6.dylib!std::basic_string<char, std::char_traits<char>, std::allocator<char> >::basic_string[in-charge](char const*, std::allocator<char> const&)+68
SecondLife!LLUserAuth::authenticate(char const*, char const*, char const*, char const*, char const*, char const*, int, int, int, LLUUID const&, int, std::vector<char const*, std::allocator<char const*> > const&, std::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, std::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)+1644
SecondLife!idle_startup()+25484
SecondLife!idle()+372
SecondLife!main_loop()+920
</pre>

=== LLEventPoll::~LLEventPoll ===
'''Note:''' Most likely already fixed (at least internally): {{jira|VWR-1436}} [[User:Nicholaz Beresford|Nicholaz]] 16:13, 9 July 2007 (PDT)
Bug tracking: 
<pre>
(Execution Froze)
SecondLife!boost::intrusive_ptr_release(LLHTTPClient::Responder*)+10
SecondLife!LLEventPoll::~LLEventPoll [in-charge deleting]()+27
SecondLife!LLViewerRegion::~LLViewerRegion [in-charge]()+196
SecondLife!LLWorld::~LLWorld [in-charge]()+67
SecondLife!disconnect_viewer(void*)+345
SecondLife!cleanup_app()+36
SecondLife!main+11599
</pre>

=== LLPipeline::updateMove ===
Bug tracking: https://jira.secondlife.com/browse/VWR-617 
<pre>
libstdc++.6.dylib!std::_Rb_tree_increment(std::_Rb_tree_node_base const*)+16
SecondLife!LLPipeline::updateMove()+324
SecondLife!idle()+6436
SecondLife!main_loop()+920
</pre>
Also: 
<pre>
SecondLife!LLPipeline::updateMove()+300
SecondLife!idle()+6436
SecondLife!main_loop()+920
</pre>

=== LLDrawPoolWater::render ===
Bug tracking: 
<pre>
ATIRadeon8500GLDriver!gldCompleteVertexBuffer+0
ATIRadeon8500GLDriver!gldUpdateDispatch+0
GLEngine!0x6188000+0
SecondLife!_ZN15LLDrawPoolWater6renderEi+0
SecondLife!_ZN10LLPipeline10renderGeomER8LLCamera+0
SecondLife!_Z7displayifi+0
SecondLife!_Z9main_loopv+0
SecondLife!main+0
</pre>

=== LLMessageSystem::checkMessages ===
Bug tracking: 
<pre>
SecondLife!std::_Rb_tree<unsigned, std::pair<unsigned const, unsigned long long>, std::_Select1st<std::pair<unsigned const, unsigned long long> >, std::less<unsigned>, std::allocator<std::pair<unsigned const, unsigned long long> > >::lower_bound(unsigned const&)+20
SecondLife!LLMessageSystem::checkMessages(long long)+3736
SecondLife!LLMessageSystem::checkAllMessages(long long, LLPumpIO*)+28
SecondLife!idle_network()+488
SecondLife!idle()+2712
SecondLife!main_loop()+920
</pre>