Second Life Wiki - User contributions [en]

User talk:Ima Mechanique

2012-11-21T02:30:53Z

Ima Mechanique: /* Page Creation */

== Page Creation ==

Thank you for create all those pages. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 20:38, 19 November 2012 (PST)

:Do [[OPT_OTHER]] and [[OPT_LEGACY_LINKSET]] really share the same value? -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 20:40, 19 November 2012 (PST)

::No problem, I was working on the syntax-highlighting file for LSL Editor and thought I'd better create the wiki pages as I went along ;-). [[OPT_OTHER]] should have had -1 for value, fixed it now.

OPT OTHER

2012-11-21T02:14:14Z

Ima Mechanique:

{{LSL Constant
|name=OPT_OTHER
|type=integer
|value=-1
|hvalue=
|desc
|examples
|caveats=
|functions={{LSL DefineRow||[[llGetObjectDetails]]|}}
|events
|cat1
|cat2
|cat3
|cat4
}}

HTTP PRAGMA NO CACHE

2012-11-19T15:53:22Z

Ima Mechanique: Created page with "{{LSL Constant|name=HTTP_PRAGMA_NO_CACHE |type=integer|value=6 |hvalue |desc |examples |caveats |functions={{LSL DefineRow||llHTTPRequest|}} |events |cat1 |cat2 |cat3 |cat4 }…"

{{LSL Constant|name=HTTP_PRAGMA_NO_CACHE
|type=integer|value=6
|hvalue
|desc
|examples
|caveats
|functions={{LSL DefineRow||[[llHTTPRequest]]|}}
|events
|cat1
|cat2
|cat3
|cat4
}}

SIM STAT PCT CHARS STEPPED

2012-11-19T15:47:42Z

Ima Mechanique: Created page with "{{LSL Constant|name=SIM_STAT_PCT_CHARS_STEPPED |type=integer|value=0 |hvalue |desc |examples |caveats |functions={{LSL DefineRow||llGetSimStats|}} |events |cat1 |cat2 |cat3 |…"

{{LSL Constant|name=SIM_STAT_PCT_CHARS_STEPPED
|type=integer|value=0
|hvalue
|desc
|examples
|caveats
|functions={{LSL DefineRow||[[llGetSimStats]]|}}
|events
|cat1
|cat2
|cat3
|cat4
}}

OPT EXCLUSION VOLUME

2012-11-19T15:38:34Z

Ima Mechanique: Created page with "{{LSL Constant|name=OPT_EXCLUSION_VOLUME |type=integer|value=6 |hvalue |desc |examples |caveats |functions={{LSL DefineRow||llGetObjectDetails|}} |events |cat1 |cat2 |cat3 |c…"

{{LSL Constant|name=OPT_EXCLUSION_VOLUME
|type=integer|value=6
|hvalue
|desc
|examples
|caveats
|functions={{LSL DefineRow||[[llGetObjectDetails]]|}}
|events
|cat1
|cat2
|cat3
|cat4
}}

OPT MATERIAL VOLUME

2012-11-19T15:31:30Z

Ima Mechanique: Created page with "{{LSL Constant|name=OPT_MATERIAL_VOLUME |type=integer|value=5 |hvalue |desc |examples |caveats |functions={{LSL DefineRow||llGetObjectDetails|}} |events |cat1=|cat2=|cat3=|ca…"

{{LSL Constant|name=OPT_MATERIAL_VOLUME
|type=integer|value=5
|hvalue
|desc
|examples
|caveats
|functions={{LSL DefineRow||[[llGetObjectDetails]]|}}
|events
|cat1=|cat2=|cat3=|cat4=}}

OPT STATIC OBSTACLE

2012-11-19T15:28:53Z

Ima Mechanique: Created page with "{{LSL Constant |name=OPT_STATIC_OBSTACLE |type=integer |value=4 |hvalue= |desc |examples |caveats= |functions={{LSL DefineRow||llGetObjectDetails|}} |events |cat1 |cat2 |cat3…"

{{LSL Constant
|name=OPT_STATIC_OBSTACLE
|type=integer
|value=4
|hvalue=
|desc
|examples
|caveats=
|functions={{LSL DefineRow||[[llGetObjectDetails]]|}}
|events
|cat1
|cat2
|cat3
|cat4
}}

OPT WALKABLE

2012-11-19T15:27:36Z

Ima Mechanique:

{{LSL Constant
|name=OPT_WALKABLE
|type=integer
|value=3
|hvalue=
|desc
|examples
|caveats=
|functions={{LSL DefineRow||[[llGetObjectDetails]]|}}
|events
|cat1
|cat2
|cat3
|cat4
}}

OPT AVATAR

2012-11-19T15:27:15Z

Ima Mechanique:

{{LSL Constant
|name=OPT_AVATAR
|type=integer
|value=1
|hvalue=
|desc
|examples
|caveats=
|functions={{LSL DefineRow||[[llGetObjectDetails]]|}}
|events
|cat1
|cat2
|cat3
|cat4
}}

OPT LEGACY LINKSET

2012-11-19T15:26:45Z

Ima Mechanique:

{{LSL Constant
|name=OPT_LEGACY_LINKSET
|type=integer
|value=0
|hvalue=
|desc
|examples
|caveats=
|functions={{LSL DefineRow||[[llGetObjectDetails]]|}}
|events
|cat1
|cat2
|cat3
|cat4
}}

PERMISSION TELEPORT

2012-11-19T15:25:09Z

Ima Mechanique:

{{LSL Constant
|name=PERMISSION_TELEPORT
|type=integer
|value=4096
|hvalue=0x1000
|desc
|examples
|functions={{LSL DefineRow||[[llTeleportAgent]]|}}
|events={{LSL DefineRow||[[run_time_permissions]]|Permission receiving event}}
|caveats=
|cat1=Permissions/Script
|cat2=Teleport
|cat3
|cat4
}}

OPT WALKABLE

2012-11-19T15:21:13Z

Ima Mechanique: Created page with "{{LSL Constant |name={{PAGENAME}} |type=integer |value=3 |hvalue= |desc |examples |caveats= |functions={{LSL DefineRow||llGetObjectDetails|}} |events |cat1 |cat2 |cat3 |cat4 …"

{{LSL Constant
|name={{PAGENAME}}
|type=integer
|value=3
|hvalue=
|desc
|examples
|caveats=
|functions={{LSL DefineRow||[[llGetObjectDetails]]|}}
|events
|cat1
|cat2
|cat3
|cat4
}}

OPT LEGACY LINKSET

2012-11-19T15:17:52Z

Ima Mechanique:

{{LSL Constant
|name={{PAGENAME}}
|type=integer
|value=0
|hvalue=
|desc
|examples
|caveats=
|functions={{LSL DefineRow||[[llGetObjectDetails]]|}}
|events
|cat1
|cat2
|cat3
|cat4
}}

OPT AVATAR

2012-11-19T15:17:26Z

Ima Mechanique:

{{LSL Constant
|name={{PAGENAME}}
|type=integer
|value=1
|hvalue=
|desc
|examples
|caveats=
|functions={{LSL DefineRow||[[llGetObjectDetails]]|}}
|events
|cat1
|cat2
|cat3
|cat4
}}

OPT CHARACTER

2012-11-19T15:17:05Z

Ima Mechanique: Created page with "{{LSL Constant |name={{PAGENAME}} |type=integer |value=2 |hvalue= |desc |examples |caveats= |functions={{LSL DefineRow||llGetObjectDetails|}} |events= |cat1 |cat2 |cat3 |cat4…"

{{LSL Constant
|name={{PAGENAME}}
|type=integer
|value=2
|hvalue=
|desc
|examples
|caveats=
|functions={{LSL DefineRow||[[llGetObjectDetails]]|}}
|events=
|cat1
|cat2
|cat3
|cat4
}}

OPT AVATAR

2012-11-19T15:14:17Z

Ima Mechanique: Created page with "{{LSL Constant |name={{PAGENAME}} |type=integer |value=1 |hvalue= |desc |examples |caveats= |functions={{LSL DefineRow||llGetObjectDetails|}} |events={{LSL DefineRow||[[dummy…"

{{LSL Constant
|name={{PAGENAME}}
|type=integer
|value=1
|hvalue=
|desc
|examples
|caveats=
|functions={{LSL DefineRow||[[llGetObjectDetails]]|}}
|events={{LSL DefineRow||[[dummy_event_name]]|dummy event description}}
|cat1
|cat2
|cat3
|cat4
}}

PERMISSION TELEPORT

2012-11-19T15:05:26Z

Ima Mechanique:

{{LSL Constant
|name={{PAGENAME}}
|type=integer
|value=4096
|hvalue=0x1000
|desc
|examples
|functions={{LSL DefineRow||[[llTeleportAgent]]|}}
|events={{LSL DefineRow||[[run_time_permissions]]|Permission receiving event}}
|caveats=
|cat1=Permissions/Script
|cat2=Teleport
|cat3
|cat4
}}

OPT LEGACY LINKSET

2012-11-19T15:04:57Z

Ima Mechanique: Created page with "{{LSL Constant |name={{PAGENAME}} |type=integer |value=0 |hvalue= |desc |examples |caveats= |functions={{LSL DefineRow||llGetObjectDetails|}} |events={{LSL DefineRow||[[dummy…"

{{LSL Constant
|name={{PAGENAME}}
|type=integer
|value=0
|hvalue=
|desc
|examples
|caveats=
|functions={{LSL DefineRow||[[llGetObjectDetails]]|}}
|events={{LSL DefineRow||[[dummy_event_name]]|dummy event description}}
|cat1
|cat2
|cat3
|cat4
}}

OPT OTHER

2012-11-19T14:43:11Z

Ima Mechanique:

{{LSL Constant
|name=OPT_OTHER
|type=integer
|value=0
|hvalue=
|desc
|examples
|caveats=
|functions={{LSL DefineRow||[[llGetObjectDetails]]|}}
|events
|cat1
|cat2
|cat3
|cat4
}}

OPT OTHER

2012-11-19T14:42:32Z

Ima Mechanique: Created page with "{{LSL Constant |name=OPT_LEGACY_LINKSET |type=integer |value=0 |hvalue= |desc |examples |caveats= |functions={{LSL DefineRow||llGetObjectDetails|}} |events |cat1 |cat2 |cat3 …"

{{LSL Constant
|name=OPT_LEGACY_LINKSET
|type=integer
|value=0
|hvalue=
|desc
|examples
|caveats=
|functions={{LSL DefineRow||[[llGetObjectDetails]]|}}
|events
|cat1
|cat2
|cat3
|cat4
}}

OBJECT PATHFINDING TYPE

2012-11-19T14:23:04Z

Ima Mechanique: Created page with "{{LSL Constant |name=OBJECT_PATHFINDING_TYPE |type=integer |value=20 |hvalue= |desc |examples |caveats= |functions={{LSL DefineRow||llGetObjectDetails|}} |events |cat1 |cat2 …"

{{LSL Constant
|name=OBJECT_PATHFINDING_TYPE
|type=integer
|value=20
|hvalue=
|desc
|examples
|caveats=
|functions={{LSL DefineRow||[[llGetObjectDetails]]|}}
|events
|cat1
|cat2
|cat3
|cat4
}}

OBJECT ATTACHED POINT

2012-11-19T13:47:32Z

Ima Mechanique: Created page with "{{LSL Constant |name=OBJECT_ATTACHED_POINT |type=integer |value=19 |hvalue= |desc |examples |caveats= |functions={{LSL DefineRow||llGetObjectDetails|}} |events |cat1 |cat2 |c…"

{{LSL Constant
|name=OBJECT_ATTACHED_POINT
|type=integer
|value=19
|hvalue=
|desc
|examples
|caveats=
|functions={{LSL DefineRow||[[llGetObjectDetails]]|}}
|events
|cat1
|cat2
|cat3
|cat4
}}

CHARACTER ACCOUNT FOR SKIPPED FRAMES

2012-11-19T13:42:51Z

Ima Mechanique: Created page with "{{LSL Constant |name=CHARACTER_ACCOUNT_FOR_SKIPPED_FRAMES |type=integer |value=14 |hvalue= |desc |examples |caveats= |functions={{LSL DefineRow||llCreateCharacter|}} |events …"

{{LSL Constant
|name=CHARACTER_ACCOUNT_FOR_SKIPPED_FRAMES
|type=integer
|value=14
|hvalue=
|desc
|examples
|caveats=
|functions={{LSL DefineRow||[[llCreateCharacter]]|}}
|events
|cat1
|cat2
|cat3
|cat4
}}

OBJECT ROOT

2012-11-19T12:46:15Z

Ima Mechanique: Created page with "{{LSL Constant |name=OBJECT_ROOT |type=integer |value=18 |hvalue= |desc |examples |caveats= |functions={{LSL DefineRow|| llGetObjectDetails|}} |events= |cat1 |cat2 |cat3 |cat…"

{{LSL Constant
|name=OBJECT_ROOT
|type=integer
|value=18
|hvalue=
|desc
|examples
|caveats=
|functions={{LSL DefineRow||[[ llGetObjectDetails]]|}}
|events=
|cat1
|cat2
|cat3
|cat4
}}

Beacons/en

2012-11-19T12:16:53Z

Ima Mechanique: Redirected page to Viewerhelp:Beacons

#REDIRECT [[Viewerhelp:Beacons]]

Using beacons

2012-11-19T12:16:32Z

Ima Mechanique: Redirected page to Viewerhelp:Beacons

#REDIRECT [[Viewerhelp:Beacons]]

How to use beacons

2012-11-19T12:16:12Z

Ima Mechanique: Redirected page to Viewerhelp:Beacons

#REDIRECT [[Viewerhelp:Beacons]]

Advanced Water Settings/en

2012-11-19T12:15:25Z

Ima Mechanique: Redirected page to Viewerhelp:Water Presets

#REDIRECT [[Viewerhelp:Water Presets]]

Open Development User Group

2012-05-31T20:11:31Z

Ima Mechanique:

{{Oz/User Group Page
|purpose=
Open Source Policies, Resources for Open Contributions, and progressing contributions through the Snowstorm process.
|date-time=
Every Monday 07:00-08:00 SLT and Thursday 13:00-14:00 SLT
|location={{SLurl|region=Hippotropolis|x=209|y=90|z=24|title=Oz's Raft}}
|team=Chaired by [[User:Oz Linden|Oz Linden]] of the [[Snowstorm Team]].
|agenda=

#[https://jira.secondlife.com/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+%22Open+Development%22+AND+assignee+is+EMPTY+AND+status+%3D+%22Awaiting+Review%22++ORDER+BY+createdDate%2C+priority+DESC OPEN Issue Triage] ([[User:Oz Linden|Oz Linden]])
# The Havok Sub-license [[User:Nalates Urriah|Nalates Urriah]] 08:37, 12 April 2012 (PDT) - Edit: removed by: [[User:Nalates Urriah|Nalates Urriah]]
#{{JiraIssue|VWR-27404|Allow User-Defined Sidebars}} [[User:Haravikk Mistral|Haravikk Mistral]]
# Would it be possible to get a mailing list similar to viewer-development-commits for viewer-release? ([[User:Kadah Coba|Kadah Coba]])
# {{JiraIssue|OPEN-139|For Windows OS enable Incremental Linking in VS2010}} ([[User:Jonathan Yap|Jonathan Yap]] 08:38, 31 May 2012 (PDT))
#update on autocorrect and spellcheck integration progress [[User:TankMaster Finesmith|TankMaster Finesmith]] 13:10, 31 May 2012 (PDT)
# {{JiraIssue|STORM-1855|Script editor pastes blocks using line by line}} What's the hold up with this? ;-)
# {{JiraIssue|STORM-1831|Automatic download of syntax-table}} Any news on translation issue?


}}

Template:LSL Constants/ExecCharacterCmd

2012-05-11T03:58:06Z

Ima Mechanique:

<noinclude>{{Pathfinding alpha}}</noinclude>
{| {{Prettytable}}
|- {{Hl2}}
!Command
!Value
!Description
|-
|CHARACTER_CMD_SMOOTH_STOP
|0x2
|Stops any current pathfinding operation.
|-
|CHARACTER_CMD_STOP
|0x0
|Stops any current pathfinding operation.
|-
|CHARACTER_CMD_JUMP
|0x1
|Makes the character jump. Requires an additional parameter, the height to jump, between 0.1m and 2.0m. This must be provided as the first element of the llExecCharacterCmd option list.
|}

Template:LSL Constants/llCreateCharacter

2012-05-11T03:01:59Z

Ima Mechanique:

<noinclude>{{Pathfinding alpha}}</noinclude>
{| {{Prettytable}}
|-{{Hl2}}
!Option
!Value
!Default
!Description
|-
|CHARACTER_DESIRED_SPEED
|1
|6
|Speed of pursuit in meters per second.
|-
|CHARACTER_RADIUS
|2
|
|Set collision capsule radius.
|-
|CHARACTER_LENGTH
|3
|
|Set collision capsule length - cannot be less than twice the radius plus 0.1m.
|-
|CHARACTER_ORIENTATION
|4
|VERTICAL
|Valid options are: VERTICAL, HORIZONTAL.
|-
|TRAVERSAL_TYPE
|7
|TRAVERSAL_TYPE_SLOW
|Valid options are: TRAVERSAL_TYPE_FAST, TRAVERSAL_TYPE_SLOW, and TRAVERSAL_TYPE_NONE. Controls the speed at which characters move on <100% walkable surfaces. To use _FAST or _SLOW, you must specify a CHARACTER_TYPE.
|-
|CHARACTER_TYPE
|6
|CHARACTER_TYPE_NONE
|Specifies which walkability coefficient will be used by this character. Options are CHARACTER_TYPE_A, CHARACTER_TYPE_B, CHARACTER_TYPE_C, CHARACTER_TYPE_D, and CHARACTER_TYPE_NONE
|-
|CHARACTER_AVOIDANCE_MODE
|5
|AVOID_CHARACTERS <nowiki>|</nowiki> AVOID_DYNAMIC_OBSTACLES
|Allows you to specify that a character should not try to avoid other characters, should not try to avoid dynamic obstacles (relatively fast moving objects and avatars), or both. This is framed in the positive sense ([CHARACTER_AVOIDANCE_MODE, AVOID_CHARACTERS] would create a character that avoided other characters but not agents or moving vehicles).
|-
|CHARACTER_MAX_ACCEL
|8
|20
|The character's maximum acceleration rate.
|-
|CHARACTER_MAX_DECEL
|9
|30
|The character's maximum deceleration rate.
|-
|CHARACTER_DESIRED_TURN_SPEED
|12
|6
|The character's maximum speed while turning--note that this is only loosely enforced (i.e., a character may turn at higher speeds under certain conditions)
|-
|CHARACTER_MAX_TURN_RADIUS
|10
|1.25
|The character's turn radius when traveling at CHARACTER_DESIRED_TURN_SPEED
|-
|CHARACTER_MAX_SPEED
|13
|20
|The character's maximum speed. Affects speed when avoiding dynamic obstacles and when traversing low-walkability objects in TRAVERSAL_TYPE_FAST mode.
|}

Viewer 2 Microsoft Windows Builds

2012-05-08T23:32:45Z

Ima Mechanique: /* Configuring the Viewer Build */

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

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

{{KBnote|Following this recipe will probably take 6 to 12 hours of wall-clock time, and 2 to 6 hours of your time, if you're starting from a fresh Windows XP/Vista/7 system.}}

== Establish your programming environment ==

This is needed for compiling any viewer based on the LL open source code and only needs to be done once.

=== Install and update Visual Studio and SDKs ===

*Install [http://www.microsoft.com/visualstudio/en-us/products/2010-editions/visual-cpp-express Visual C++ 2010 Express] (Web install) or [http://go.microsoft.com/?linkid=9709969 Visual C++ 2010 Express] (ISO)
*Install [http://www.microsoft.com/downloads/en/details.aspx?FamilyID=a7b7a05e-6de6-4d3a-a423-37bf0912db84&displaylang=en Microsoft Visual C++ 2010 Redistributable Package]
*Install [http://www.microsoft.com/downloads/en/details.aspx?FamilyID=6B6C21D2-2006-4AFA-9702-529FA782D63B Windows SDK for Windows 7 and .NET Framework 4] (Web install) [Note: uncheck the Redistributable Package option to prevent installation failure] or [http://www.microsoft.com/downloads/en/details.aspx?FamilyID=35aeda01-421d-4ba5-b44b-543dc8c33a20 Windows SDK for Windows 7 and .NET Framework 4] (ISO)
*Install [http://www.microsoft.com/downloads/en/details.aspx?displaylang=en&FamilyID=3021d52b-514e-41d3-ad02-438a3ba730ba DirectX SDK (June 2010)]
*Run [http://www.update.microsoft.com/microsoftupdate/v6 Microsoft Update], and keep running it until no updates are needed. This may take 6~8 iterations on older versions of windows.
** For Windows Vista and Windows 7, you need to select "Get updates from other Microsoft products" to get the updates for Visual Studio.
** For Windows XP, use the provided link above. The Windows Update menu item on your computer is not the correct updater to use.
** During the update cycles make sure you have picked up [http://www.microsoft.com/downloads/en/confirmation.aspx?FamilyID=75568aa6-8107-475d-948a-ef22627e57a5 Microsoft Visual Studio 2010 Service Pack 1] (Web install) or [http://go.microsoft.com/fwlink/?LinkId=210710 Microsoft Visual Studio 2010 Service Pack 1] (ISO)

=== Install required development tools ===

{{KBnote|The order of the following installations should not matter.}}
{{KBnote|If the installer for a particular package does not update your PATH environment variable you will have to do this manually.}}

* '''CMake''' ([http://www.cmake.org/HTML/Download.html download CMake])
** This should be version 2.8.4 (or above in the 2.8.x series).
**Add the <code>\bin</code> directory to your path.
* '''Python''' (either [http://www.python.org/download/ Standard Python] or [http://www.activestate.com/activepython/downloads ActivePython])
** Version 2.7.1 works with the build scripts.
* '''Mercurial''' (either [http://tortoisehg.bitbucket.org/ TortoiseHg] or [http://mercurial.selenic.com/ Mercurial Hg])
**Create a new file <code>%USERPROFILE%\Mercurial.ini</code> and in it put your Second Life name and optionally your email address:
[ui]
username = John Doe <john@example.com>
* '''Cygwin''' ([http://www.cygwin.com/ download Cygwin])
** When you run the cygwin setup utility make sure you have selected to install '''unzip''' (under "Archives"), '''bison''', '''flex''', '''patchutils''' (all located under "devel"), and '''curl''' (under "Web"), which are not part of the default install. Do not install Cygwin Python or Mercurial. You won't need to use the Cygwin shell for anything.
**Add the <code>cygwin\bin</code> directory to the '''very end''' of your path and make sure it stays that way.

=== Install optional development tools ===

* [http://code.google.com/p/unsis/downloads/list Unicode NSIS (Nullsoft Scriptable Install System)]
** This is the package installer used to build <code>Second_Life_<version-code>_LindenDeveloper_Setup.exe</code>. You only need this package if you are going to distribute the viewer you compile or if you want to install it locally.
*: In the [[#Configuring_the_Viewer|Configure VS2010 step]] below you will need to add a line in the '''Executable Directories''' section:
*:* 64 bit systems use <code>%ProgramFiles(x86)%\NSIS\Unicode</code>
*:* 32 bit systems use <code>%ProgramFiles%\NSIS\Unicode</code>
* [http://notepadplusplus.org/ Notepad++]
** You need to use an editor that conforms to the [[Coding Standard]]. In particular, you must not check in files with DOS line endings except in very limited circumstances; see [[How to avoid DOS line endings in Windows tools]].
* [[Mercurial_Tools]] (strongly recommended)
** When you are following these instructions you will be updating the <code>%USERPROFILE%\Mercurial.ini</code> file you created when you installed Mercurial.

=== Install Autobuild ===
* Follow the directions at [[Autobuild#Getting_Autobuild|Getting Autobuild]] to install Autobuild
* Add an environment variable, so that autobuild doesn't default to using (or trying) older compiler versions:
** Right-click "My Computer" and select '''Properties''' or press the windows logo key and the pause key at the same time.
** For XP, when the Properties dialog opens, click the '''Advanced''' tab followed by the '''Environmental Variables''' button. This will open a new window with a list of System and User variables. For Vista and later, when the System Properties window opens, click the '''Advanced system settings''' on the left column, then click '''Environment Variables...'''
** In the User section, click '''New'''. Set '''Variable Name''' to AUTOBUILD_VSVER and set '''Variable Value''' to 100.
** Click the OK/Close buttons to close all the windows.

=== Configure VC2010 ===
While you may choose to use autobuild for all your compiling you still need to establish certain settings internal to VC2010.

*Start the IDE

*Navigate to '''Tools''' > '''Options''' > '''Projects and Solutions''' > '''Build and Run''' and set '''maximum number of parallel projects builds''' to <code>1</code>.

* (VC Express only) Enable '''Tools''' > '''Settings''' > '''Expert Settings''' to get the '''Build''' (and other) menus. If you already have a '''Build''' menu you do not need to perform this step.

{{KBnote|The following steps require an open visual studio project. It does not matter which project you use, as you will only change some global settings used by all projects when they are opened. The open project itself won't be changed.}}

You need to set a number of paths.
* Open any existing project you may have or make a New Project.

At the bottom on the Solution Explorer you will see three tabs.
*Click the one on the right labeled '''Property Manager'''. (The name may be somewhat truncated.)

[[File:VS2010_Property_Manager.PNG|100px]]
[[:File:VS2010_Property_Manager.PNG|Example image]]

*On the left side click to expand any project and then click again to expand the '''Release''' folder.

[[File:VS2010_Project_Config.PNG|100px]]
[[:File:VS2010_Project_Config.PNG|Example image]]

*Right click on '''Microsoft.Cpp.Win32.user'''.

*Pick '''Properties''' > '''VC++ Directories'''.

This is where the build environment is pulled together into a functional VC2010 build system and also where much hand wringing, hair pulling, and fist pounding frustration takes place.

*Set '''Executable Directories''' to:

$(ExecutablePath)
$(DXSDK_DIR)
$(WindowsSdkDir)\Bin
C:\cygwin\bin
$(SystemRoot)

[[File:32BitExecutableDirectories.png|100px]]
[[:File:32BitExecutableDirectories.png|32 bit Executable Directories example image]]

*Set '''Include Directories''' to:

$(WindowsSdkDir)\Include
$(WindowsSdkDir)\Include\gl
$(DXSDK_DIR)\Include

[[File:32BitIncludeDirectories.png|100px]]
[[:File:32BitIncludeDirectories.png|32 bit Include Directories example image]]

*Set '''Library Directories''' to:

$(WindowsSdkDir)\Lib
$(DXSDK_DIR)

[[File:32BitLibraryDirectories.png|100px]]
[[:File:32BitLibraryDirectories.png|32 bit Library Directories example image]]

== Set up your source code tree ==

Plan your directory structure ahead of time. If you are going to be producing changes or patches you will be cloning a copy of an unaltered source code tree for every change or patch you make, so you might want to have all this work stored in it's own directory.

To get a copy of the source code tree:
* Open up a DOS Command window
* CD to where you want to install viewer-release. Do not have any spaces in this path.
* Do:
hg clone <nowiki>http://hg.secondlife.com/viewer-release</nowiki>

Let's say some time has gone by since you have performed the previous steps and now you want to develop a change or work on a jira. You will update your clean local repository with all the changes committed to viewer-release since you last synchronized your files:
* CD into <code>viewer-release</code>
* Do:
hg pull -u

* Move up one level from <code>viewer-release</code>
* Do:
hg clone viewer-release VWR-nnnnn
Note: <code>nnnnn</code> is the jira number. You can also clone to a name of your choosing if you are making changes not associated with the LL jira system.

== Prepare third party libraries ==
Most third party libraries needed to build the viewer will be automatically downloaded for you and installed into the build directory within your source tree during the [[#Configuring_the_Viewer|configuration step]] below. Some few need to be manually set up, though, when using an open source developer configuration (<code>Release'''OS'''</code>, <code>RelWithDebInfo'''OS'''</code> or <code>Debug'''OS'''</code>)

=== Fmod method 1 (using autobuild) ===

CD to where you want to install the 3p-fmod repository and do:
hg clone <nowiki>https://bitbucket.org/lindenlab/3p-fmod</nowiki>

CD into the <code>3p-fmod</code> directory you created and build it:
autobuild build --all

Package the results:
autobuild package

Update autobuild with the filename and hash just displayed. CD to the directory where you cloned viewer-release and do:

copy autobuild.xml my_autobuild.xml
set AUTOBUILD_CONFIG_FILE=my_autobuild.xml
autobuild installables edit fmod platform=windows hash=<hash> url=file:///<fmod-filespec>

Example:

copy autobuild.xml my_autobuild.xml
autobuild installables edit fmod platform=windows hash=0f196f00e7dff49f22252efb68525658 url=file:///C:/3p-fmod/fmod-3.75-windows-20110531.tar.bz2

{{KBnote|Having to copy <code>autobuild.xml</code> and modify the copy from within a cloned repository is a lot of work for every repository you make, but this is the only way to guarantee you pick up upstream changes to <code>autobuild.xml</code> and do not send up a modified <code>autobuild.xml</code> when you do an hg push.}}

=== Fmod method 2 (using switches) ===
[To be written up]

== Configuring the Viewer Build ==

Fmod is the audio library the viewer uses. If you are compiling with Fmod you will need to do:
set AUTOBUILD_CONFIG_FILE=my_autobuild.xml

The environment variable <code>AUTOBUILD_INSTALLABLE_CACHE</code> controls the placement of library files downloaded as part of the configure process. If you do not want these library files going into your Windows <code>%TEMP%</code> directory define the environment variable to point to some other location you have established:
set AUTOBUILD_INSTALLABLE_CACHE=E:\SSfiles\Libraries

At the command line in the source tree's root directory (presumably a directory you have cloned from viewer-release, as it is not a good idea to work in viewer-release, unless you are only compiling for youself) e.g. <code>C:\linden\VWR-12345\</code>) run:
autobuild configure -c [CONFIGURATION]
where <code>[CONFIGURATION]</code> is one of those listed at [[Building the Viewer with Autobuild#Build a desired configuration]] (<code>ReleaseOS</code>, <code>RelWithDebInfoOS</code>, <code>DebugOS</code>)

=== Configuration Switches ===
There are a number of switches you can use to modify the configuration process. The name of each switch is followed by its type and then by the value you want to set.

* '''FMOD''' (bool) controls if the Fmod package is incorporated into the viewer. You must have performed the Fmod installation steps in [[Viewer_2_Microsoft_Windows_Builds#Fmod_method_1_.28using_autobuild.29]] for this to work.
* '''LL_TESTS''' (bool) controls if the tests are compiled and run. There are quite a lot of them so excluding them is recommended unless you have some reason to need one or more of them.
* '''PACKAGE''' (bool) controls if the package step is run. You must have installed NSIS described in [[Viewer_2_Microsoft_Windows_Builds#Install_optional_development_tools]] for this to work.

{{KBnote|'''OFF''' and '''NO''' are the same as '''FALSE'''; anything else is considered to be '''TRUE'''.}}

Example:
autobuild configure -c ReleaseOS -- -DLL_TESTS:BOOL=FALSE -DPACKAGE:BOOL=FALSE -DFMOD:BOOL=TRUE

== Compiling the Viewer ==
=== Compiling the viewer with autobuild ===
You can compile the viewer with either autobuild (the encouraged/supported method) or with the VS IDE.

When compiling with autobuild you will have the best chance of success if you work from within a preconfigured Command Prompt window. Depending on how your computer has been set up there are two possible ways to open this window and you need to find which works in your particular case:
*Method 1
**From '''All Programs''' Navigate into the '''Microsoft Windows SDK V7.1''' program menu
**Click on '''Windows SDK 7.1 Command Prompt'''
*Method 2
**From '''All Programs''' Navigate into the '''Microsoft Visual Studio 2010''' program menu
**Click on '''Microsoft Visual Studio Command Prompt (2010)'''

{{KBcaution|If you are building with Fmod and have followed the previous Fmod setup instructions AND you are now using a new command window you will need to redo the <code>set AUTOBUILD_CONFIG_FILE{{=}}my_autobuild.xml</code>.}}

*Run:
autobuild build -c [CONFIGURATION] --no-configure

There are some useful switches to know about, so your commands may look like this:
autobuild configure -c ReleaseOS -- -DLL_TESTS:BOOL=FALSE -DPACKAGE:BOOL=FALSE -DFMOD:BOOL=TRUE
autobuild build -c ReleaseOS --no-configure

{{KBnote|It is possible to use autobuild to do both the configure step (only needed once) and the build step with one command. I find it is clearer and saves a bit of time if these steps are done separately.}}

{{KBnote|Do not be alarmed if you see groups of messages with '''warning LNK4099: PDB''' in them.}}

=== Compiling the viewer with the IDE ===

The autobuild configure step created the <code>\build-vc100</code> directory at the root of the source tree. In here is the <code>SecondLife.sln</code> solution file.

Start the IDE and open this solution.

You might want to change the build type in the drop-down located in the toolbar from '''Debug''' to '''Release''' or '''RelWithDebInfo'''.

[[File:VS2010BuildType.png|100px]]
[[:File:VS2010BuildType.png|Changing build type example image]]

You need to adjust the Platform Toolset setting.
* Select all the projects in the Solution Explorer list on the left of the screen.
** Click on the first project and scroll to the bottom of this list and {{K|shift}}-click on the last project.
* Right click on the selected list
* Navigate to '''Properties''' > '''Configuration Properties''' > '''General''' > '''Platform Toolset'''
* Change this value to <code>Windows7.1SDK</code>

* Push {{K|F7}} to start the compiler.

== Running your newly built viewer ==
=== Running from a desktop shortcut ===
* Make a desktop shortcut for <code>Drive:\your-path\build-vc100\newview\Release\secondlife-bin.exe</code>

* Right-click the shortcut
* Select '''Properties'''
* Set '''Start in:''' to <code>Drive:\your-path\indra\newview</code>

=== Running from within the IDE ===
* In the Solution Explorer pane right click on '''secondlife-bin'''
** Click '''Set as StartUp Project'''
** Pick '''Properties''' > '''Configuration Properties''' > '''Debugging'''
*** Set '''Command''' to <code>Drive:\your-path\build-vc100\newview\Release\secondlife-bin.exe</code> (adjust <code>Release</code> to the type of build you are doing, e.g. <code>RelWithDebInfo</code>)
*** Set '''Working Directory''' to <code>..\..\indra\newview</code>

== Handling Problems ==

If you encounter errors or run into problems following the instructions above, please first check whether someone else already had the same issue. A solution might be known already. See the [[#Common_Issues.2FBugs.2FGlitches_And_Solutions|issue list below]], check [[{{TALKPAGENAME}}|the talk page]] (and report useful experiences there) and search our [[issue tracker]]. Even when no description of your problem has been written down yet, someone might know about it, so get in touch with the community to [[#Getting_help|get help]].

=== Getting help ===
* Subscribe to [[OpenSource-Dev|OpenSource-Dev Mailing List]] ([https://lists.secondlife.com/cgi-bin/mailman/listinfo/opensource-dev subscribe]) and post your question there.
* For faster response, join the general open source viewer discussion and development [[IRC]] channel [irc://irc.freenode.org/opensl #opensl on freenode]. Hopefully a helpful person is online when you ask your question.

=== Common Issues/Bugs/Glitches And Solutions ===

==== Not being able to find objidl.h in the Microsoft Windows SDK, when compiling llwindow ====
https://lists.secondlife.com/pipermail/opensource-dev/2011-April/006562.html
* Can be caused by path problems or some installation conflicts with the DirectX SDK.

==== stdint.h typedef conflicts between Quicktime and VS2010 ====
https://lists.secondlife.com/pipermail/opensource-dev/2011-April/006565.html
*: Can be solved by some small edits to header files to make sure the two don't bash on each other.

==== Eliminate deprecated switches, messages, and use memory more efficiently ====

The VS2010 compiler uses a lot of memory while compiling the viewer. If you run out of memory you will start to page heavily and your compile time will become much longer. The /Zm1000 switch affects compiler memory usage.

You may see this message while compiling:
use 'EHsc' instead of 'GX'

Here is how to free up some memory the compiler allocates and to eliminate these messages:

*Edit <code>\CMake 2.8\share\cmake-2.8\Modules\Platform\Windows-cl.cmake</code>

*Replace line 156 with:
IF(MSVC10)
SET(CMAKE_CXX_FLAGS_INIT "/DWIN32 /D_WINDOWS /W3 /EHsc /GR")
ELSEIF(NOT MSVC10)
SET(CMAKE_CXX_FLAGS_INIT "/DWIN32 /D_WINDOWS /W3 /Zm1000 /EHsc /GR")
ENDIF(MSVC10)

*Replace line 172 with:
IF(MSVC10)
SET(CMAKE_CXX_FLAGS_INIT "/DWIN32 /D_WINDOWS /W3 /EHsc /GR")
ELSEIF(NOT MSVC10)
SET(CMAKE_CXX_FLAGS_INIT "/DWIN32 /D_WINDOWS /W3 /Zm1000 /GX /GR")
ENDIF(MSVC10)

*Replace line 184 with:
IF(MSVC10)
SET(CMAKE_CXX_FLAGS_INIT "/DWIN32 /D_WINDOWS /W3 /EHsc /GR")
ELSEIF(NOT MSVC10)
SET(CMAKE_CXX_FLAGS_INIT "/DWIN32 /D_WINDOWS /W3 /Zm1000 /GX /GR")
ENDIF(MSVC10)

== References ==

Tip of the hat to Nicky_Perian for [[User:Nicky_Perian/Visual_Studio_10_Autobuild]]

[[Category:Compiling viewer]]

Viewer 2 Microsoft Windows Builds

2012-05-08T23:32:01Z

Ima Mechanique: /* Fmod method 1 (using autobuild) */

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

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

{{KBnote|Following this recipe will probably take 6 to 12 hours of wall-clock time, and 2 to 6 hours of your time, if you're starting from a fresh Windows XP/Vista/7 system.}}

== Establish your programming environment ==

This is needed for compiling any viewer based on the LL open source code and only needs to be done once.

=== Install and update Visual Studio and SDKs ===

*Install [http://www.microsoft.com/visualstudio/en-us/products/2010-editions/visual-cpp-express Visual C++ 2010 Express] (Web install) or [http://go.microsoft.com/?linkid=9709969 Visual C++ 2010 Express] (ISO)
*Install [http://www.microsoft.com/downloads/en/details.aspx?FamilyID=a7b7a05e-6de6-4d3a-a423-37bf0912db84&displaylang=en Microsoft Visual C++ 2010 Redistributable Package]
*Install [http://www.microsoft.com/downloads/en/details.aspx?FamilyID=6B6C21D2-2006-4AFA-9702-529FA782D63B Windows SDK for Windows 7 and .NET Framework 4] (Web install) [Note: uncheck the Redistributable Package option to prevent installation failure] or [http://www.microsoft.com/downloads/en/details.aspx?FamilyID=35aeda01-421d-4ba5-b44b-543dc8c33a20 Windows SDK for Windows 7 and .NET Framework 4] (ISO)
*Install [http://www.microsoft.com/downloads/en/details.aspx?displaylang=en&FamilyID=3021d52b-514e-41d3-ad02-438a3ba730ba DirectX SDK (June 2010)]
*Run [http://www.update.microsoft.com/microsoftupdate/v6 Microsoft Update], and keep running it until no updates are needed. This may take 6~8 iterations on older versions of windows.
** For Windows Vista and Windows 7, you need to select "Get updates from other Microsoft products" to get the updates for Visual Studio.
** For Windows XP, use the provided link above. The Windows Update menu item on your computer is not the correct updater to use.
** During the update cycles make sure you have picked up [http://www.microsoft.com/downloads/en/confirmation.aspx?FamilyID=75568aa6-8107-475d-948a-ef22627e57a5 Microsoft Visual Studio 2010 Service Pack 1] (Web install) or [http://go.microsoft.com/fwlink/?LinkId=210710 Microsoft Visual Studio 2010 Service Pack 1] (ISO)

=== Install required development tools ===

{{KBnote|The order of the following installations should not matter.}}
{{KBnote|If the installer for a particular package does not update your PATH environment variable you will have to do this manually.}}

* '''CMake''' ([http://www.cmake.org/HTML/Download.html download CMake])
** This should be version 2.8.4 (or above in the 2.8.x series).
**Add the <code>\bin</code> directory to your path.
* '''Python''' (either [http://www.python.org/download/ Standard Python] or [http://www.activestate.com/activepython/downloads ActivePython])
** Version 2.7.1 works with the build scripts.
* '''Mercurial''' (either [http://tortoisehg.bitbucket.org/ TortoiseHg] or [http://mercurial.selenic.com/ Mercurial Hg])
**Create a new file <code>%USERPROFILE%\Mercurial.ini</code> and in it put your Second Life name and optionally your email address:
[ui]
username = John Doe <john@example.com>
* '''Cygwin''' ([http://www.cygwin.com/ download Cygwin])
** When you run the cygwin setup utility make sure you have selected to install '''unzip''' (under "Archives"), '''bison''', '''flex''', '''patchutils''' (all located under "devel"), and '''curl''' (under "Web"), which are not part of the default install. Do not install Cygwin Python or Mercurial. You won't need to use the Cygwin shell for anything.
**Add the <code>cygwin\bin</code> directory to the '''very end''' of your path and make sure it stays that way.

=== Install optional development tools ===

* [http://code.google.com/p/unsis/downloads/list Unicode NSIS (Nullsoft Scriptable Install System)]
** This is the package installer used to build <code>Second_Life_<version-code>_LindenDeveloper_Setup.exe</code>. You only need this package if you are going to distribute the viewer you compile or if you want to install it locally.
*: In the [[#Configuring_the_Viewer|Configure VS2010 step]] below you will need to add a line in the '''Executable Directories''' section:
*:* 64 bit systems use <code>%ProgramFiles(x86)%\NSIS\Unicode</code>
*:* 32 bit systems use <code>%ProgramFiles%\NSIS\Unicode</code>
* [http://notepadplusplus.org/ Notepad++]
** You need to use an editor that conforms to the [[Coding Standard]]. In particular, you must not check in files with DOS line endings except in very limited circumstances; see [[How to avoid DOS line endings in Windows tools]].
* [[Mercurial_Tools]] (strongly recommended)
** When you are following these instructions you will be updating the <code>%USERPROFILE%\Mercurial.ini</code> file you created when you installed Mercurial.

=== Install Autobuild ===
* Follow the directions at [[Autobuild#Getting_Autobuild|Getting Autobuild]] to install Autobuild
* Add an environment variable, so that autobuild doesn't default to using (or trying) older compiler versions:
** Right-click "My Computer" and select '''Properties''' or press the windows logo key and the pause key at the same time.
** For XP, when the Properties dialog opens, click the '''Advanced''' tab followed by the '''Environmental Variables''' button. This will open a new window with a list of System and User variables. For Vista and later, when the System Properties window opens, click the '''Advanced system settings''' on the left column, then click '''Environment Variables...'''
** In the User section, click '''New'''. Set '''Variable Name''' to AUTOBUILD_VSVER and set '''Variable Value''' to 100.
** Click the OK/Close buttons to close all the windows.

=== Configure VC2010 ===
While you may choose to use autobuild for all your compiling you still need to establish certain settings internal to VC2010.

*Start the IDE

*Navigate to '''Tools''' > '''Options''' > '''Projects and Solutions''' > '''Build and Run''' and set '''maximum number of parallel projects builds''' to <code>1</code>.

* (VC Express only) Enable '''Tools''' > '''Settings''' > '''Expert Settings''' to get the '''Build''' (and other) menus. If you already have a '''Build''' menu you do not need to perform this step.

{{KBnote|The following steps require an open visual studio project. It does not matter which project you use, as you will only change some global settings used by all projects when they are opened. The open project itself won't be changed.}}

You need to set a number of paths.
* Open any existing project you may have or make a New Project.

At the bottom on the Solution Explorer you will see three tabs.
*Click the one on the right labeled '''Property Manager'''. (The name may be somewhat truncated.)

[[File:VS2010_Property_Manager.PNG|100px]]
[[:File:VS2010_Property_Manager.PNG|Example image]]

*On the left side click to expand any project and then click again to expand the '''Release''' folder.

[[File:VS2010_Project_Config.PNG|100px]]
[[:File:VS2010_Project_Config.PNG|Example image]]

*Right click on '''Microsoft.Cpp.Win32.user'''.

*Pick '''Properties''' > '''VC++ Directories'''.

This is where the build environment is pulled together into a functional VC2010 build system and also where much hand wringing, hair pulling, and fist pounding frustration takes place.

*Set '''Executable Directories''' to:

$(ExecutablePath)
$(DXSDK_DIR)
$(WindowsSdkDir)\Bin
C:\cygwin\bin
$(SystemRoot)

[[File:32BitExecutableDirectories.png|100px]]
[[:File:32BitExecutableDirectories.png|32 bit Executable Directories example image]]

*Set '''Include Directories''' to:

$(WindowsSdkDir)\Include
$(WindowsSdkDir)\Include\gl
$(DXSDK_DIR)\Include

[[File:32BitIncludeDirectories.png|100px]]
[[:File:32BitIncludeDirectories.png|32 bit Include Directories example image]]

*Set '''Library Directories''' to:

$(WindowsSdkDir)\Lib
$(DXSDK_DIR)

[[File:32BitLibraryDirectories.png|100px]]
[[:File:32BitLibraryDirectories.png|32 bit Library Directories example image]]

== Set up your source code tree ==

Plan your directory structure ahead of time. If you are going to be producing changes or patches you will be cloning a copy of an unaltered source code tree for every change or patch you make, so you might want to have all this work stored in it's own directory.

To get a copy of the source code tree:
* Open up a DOS Command window
* CD to where you want to install viewer-release. Do not have any spaces in this path.
* Do:
hg clone <nowiki>http://hg.secondlife.com/viewer-release</nowiki>

Let's say some time has gone by since you have performed the previous steps and now you want to develop a change or work on a jira. You will update your clean local repository with all the changes committed to viewer-release since you last synchronized your files:
* CD into <code>viewer-release</code>
* Do:
hg pull -u

* Move up one level from <code>viewer-release</code>
* Do:
hg clone viewer-release VWR-nnnnn
Note: <code>nnnnn</code> is the jira number. You can also clone to a name of your choosing if you are making changes not associated with the LL jira system.

== Prepare third party libraries ==
Most third party libraries needed to build the viewer will be automatically downloaded for you and installed into the build directory within your source tree during the [[#Configuring_the_Viewer|configuration step]] below. Some few need to be manually set up, though, when using an open source developer configuration (<code>Release'''OS'''</code>, <code>RelWithDebInfo'''OS'''</code> or <code>Debug'''OS'''</code>)

=== Fmod method 1 (using autobuild) ===

CD to where you want to install the 3p-fmod repository and do:
hg clone <nowiki>https://bitbucket.org/lindenlab/3p-fmod</nowiki>

CD into the <code>3p-fmod</code> directory you created and build it:
autobuild build --all

Package the results:
autobuild package

Update autobuild with the filename and hash just displayed. CD to the directory where you cloned viewer-release and do:

copy autobuild.xml my_autobuild.xml
set AUTOBUILD_CONFIG_FILE=my_autobuild.xml
autobuild installables edit fmod platform=windows hash=<hash> url=file:///<fmod-filespec>

Example:

copy autobuild.xml my_autobuild.xml
autobuild installables edit fmod platform=windows hash=0f196f00e7dff49f22252efb68525658 url=file:///C:/3p-fmod/fmod-3.75-windows-20110531.tar.bz2

{{KBnote|Having to copy <code>autobuild.xml</code> and modify the copy from within a cloned repository is a lot of work for every repository you make, but this is the only way to guarantee you pick up upstream changes to <code>autobuild.xml</code> and do not send up a modified <code>autobuild.xml</code> when you do an hg push.}}

=== Fmod method 2 (using switches) ===
[To be written up]

== Configuring the Viewer Build ==

Fmod is the audio library the viewer uses. If you are compiling with Fmod you will need to do:
set AUTOBUILD_CONFIG_FILE=my_autobuild.xml

The environment variable <code>AUTOBUILD_INSTALLABLE_CACHE</code> controls the placement of library files downloaded as part of the configure process. If you do not want these library files going into your Windows <code>%TEMP%</code> directory define the environment variable to point to some other location you have established:
set AUTOBUILD_INSTALLABLE_CACHE=E:\SSfiles\Libraries

At the command line in the source tree's root directory (presumably a directory you have cloned from viewer-development, as it is not a good idea to work in viewer-development, unless you are only compiling for youself) e.g. <code>C:\linden\VWR-12345\</code>) run:
autobuild configure -c [CONFIGURATION]
where <code>[CONFIGURATION]</code> is one of those listed at [[Building the Viewer with Autobuild#Build a desired configuration]] (<code>ReleaseOS</code>, <code>RelWithDebInfoOS</code>, <code>DebugOS</code>)

=== Configuration Switches ===
There are a number of switches you can use to modify the configuration process. The name of each switch is followed by its type and then by the value you want to set.

* '''FMOD''' (bool) controls if the Fmod package is incorporated into the viewer. You must have performed the Fmod installation steps in [[Viewer_2_Microsoft_Windows_Builds#Fmod_method_1_.28using_autobuild.29]] for this to work.
* '''LL_TESTS''' (bool) controls if the tests are compiled and run. There are quite a lot of them so excluding them is recommended unless you have some reason to need one or more of them.
* '''PACKAGE''' (bool) controls if the package step is run. You must have installed NSIS described in [[Viewer_2_Microsoft_Windows_Builds#Install_optional_development_tools]] for this to work.

{{KBnote|'''OFF''' and '''NO''' are the same as '''FALSE'''; anything else is considered to be '''TRUE'''.}}

Example:
autobuild configure -c ReleaseOS -- -DLL_TESTS:BOOL=FALSE -DPACKAGE:BOOL=FALSE -DFMOD:BOOL=TRUE

== Compiling the Viewer ==
=== Compiling the viewer with autobuild ===
You can compile the viewer with either autobuild (the encouraged/supported method) or with the VS IDE.

When compiling with autobuild you will have the best chance of success if you work from within a preconfigured Command Prompt window. Depending on how your computer has been set up there are two possible ways to open this window and you need to find which works in your particular case:
*Method 1
**From '''All Programs''' Navigate into the '''Microsoft Windows SDK V7.1''' program menu
**Click on '''Windows SDK 7.1 Command Prompt'''
*Method 2
**From '''All Programs''' Navigate into the '''Microsoft Visual Studio 2010''' program menu
**Click on '''Microsoft Visual Studio Command Prompt (2010)'''

{{KBcaution|If you are building with Fmod and have followed the previous Fmod setup instructions AND you are now using a new command window you will need to redo the <code>set AUTOBUILD_CONFIG_FILE{{=}}my_autobuild.xml</code>.}}

*Run:
autobuild build -c [CONFIGURATION] --no-configure

There are some useful switches to know about, so your commands may look like this:
autobuild configure -c ReleaseOS -- -DLL_TESTS:BOOL=FALSE -DPACKAGE:BOOL=FALSE -DFMOD:BOOL=TRUE
autobuild build -c ReleaseOS --no-configure

{{KBnote|It is possible to use autobuild to do both the configure step (only needed once) and the build step with one command. I find it is clearer and saves a bit of time if these steps are done separately.}}

{{KBnote|Do not be alarmed if you see groups of messages with '''warning LNK4099: PDB''' in them.}}

=== Compiling the viewer with the IDE ===

The autobuild configure step created the <code>\build-vc100</code> directory at the root of the source tree. In here is the <code>SecondLife.sln</code> solution file.

Start the IDE and open this solution.

You might want to change the build type in the drop-down located in the toolbar from '''Debug''' to '''Release''' or '''RelWithDebInfo'''.

[[File:VS2010BuildType.png|100px]]
[[:File:VS2010BuildType.png|Changing build type example image]]

You need to adjust the Platform Toolset setting.
* Select all the projects in the Solution Explorer list on the left of the screen.
** Click on the first project and scroll to the bottom of this list and {{K|shift}}-click on the last project.
* Right click on the selected list
* Navigate to '''Properties''' > '''Configuration Properties''' > '''General''' > '''Platform Toolset'''
* Change this value to <code>Windows7.1SDK</code>

* Push {{K|F7}} to start the compiler.

== Running your newly built viewer ==
=== Running from a desktop shortcut ===
* Make a desktop shortcut for <code>Drive:\your-path\build-vc100\newview\Release\secondlife-bin.exe</code>

* Right-click the shortcut
* Select '''Properties'''
* Set '''Start in:''' to <code>Drive:\your-path\indra\newview</code>

=== Running from within the IDE ===
* In the Solution Explorer pane right click on '''secondlife-bin'''
** Click '''Set as StartUp Project'''
** Pick '''Properties''' > '''Configuration Properties''' > '''Debugging'''
*** Set '''Command''' to <code>Drive:\your-path\build-vc100\newview\Release\secondlife-bin.exe</code> (adjust <code>Release</code> to the type of build you are doing, e.g. <code>RelWithDebInfo</code>)
*** Set '''Working Directory''' to <code>..\..\indra\newview</code>

== Handling Problems ==

If you encounter errors or run into problems following the instructions above, please first check whether someone else already had the same issue. A solution might be known already. See the [[#Common_Issues.2FBugs.2FGlitches_And_Solutions|issue list below]], check [[{{TALKPAGENAME}}|the talk page]] (and report useful experiences there) and search our [[issue tracker]]. Even when no description of your problem has been written down yet, someone might know about it, so get in touch with the community to [[#Getting_help|get help]].

=== Getting help ===
* Subscribe to [[OpenSource-Dev|OpenSource-Dev Mailing List]] ([https://lists.secondlife.com/cgi-bin/mailman/listinfo/opensource-dev subscribe]) and post your question there.
* For faster response, join the general open source viewer discussion and development [[IRC]] channel [irc://irc.freenode.org/opensl #opensl on freenode]. Hopefully a helpful person is online when you ask your question.

=== Common Issues/Bugs/Glitches And Solutions ===

==== Not being able to find objidl.h in the Microsoft Windows SDK, when compiling llwindow ====
https://lists.secondlife.com/pipermail/opensource-dev/2011-April/006562.html
* Can be caused by path problems or some installation conflicts with the DirectX SDK.

==== stdint.h typedef conflicts between Quicktime and VS2010 ====
https://lists.secondlife.com/pipermail/opensource-dev/2011-April/006565.html
*: Can be solved by some small edits to header files to make sure the two don't bash on each other.

==== Eliminate deprecated switches, messages, and use memory more efficiently ====

The VS2010 compiler uses a lot of memory while compiling the viewer. If you run out of memory you will start to page heavily and your compile time will become much longer. The /Zm1000 switch affects compiler memory usage.

You may see this message while compiling:
use 'EHsc' instead of 'GX'

Here is how to free up some memory the compiler allocates and to eliminate these messages:

*Edit <code>\CMake 2.8\share\cmake-2.8\Modules\Platform\Windows-cl.cmake</code>

*Replace line 156 with:
IF(MSVC10)
SET(CMAKE_CXX_FLAGS_INIT "/DWIN32 /D_WINDOWS /W3 /EHsc /GR")
ELSEIF(NOT MSVC10)
SET(CMAKE_CXX_FLAGS_INIT "/DWIN32 /D_WINDOWS /W3 /Zm1000 /EHsc /GR")
ENDIF(MSVC10)

*Replace line 172 with:
IF(MSVC10)
SET(CMAKE_CXX_FLAGS_INIT "/DWIN32 /D_WINDOWS /W3 /EHsc /GR")
ELSEIF(NOT MSVC10)
SET(CMAKE_CXX_FLAGS_INIT "/DWIN32 /D_WINDOWS /W3 /Zm1000 /GX /GR")
ENDIF(MSVC10)

*Replace line 184 with:
IF(MSVC10)
SET(CMAKE_CXX_FLAGS_INIT "/DWIN32 /D_WINDOWS /W3 /EHsc /GR")
ELSEIF(NOT MSVC10)
SET(CMAKE_CXX_FLAGS_INIT "/DWIN32 /D_WINDOWS /W3 /Zm1000 /GX /GR")
ENDIF(MSVC10)

== References ==

Tip of the hat to Nicky_Perian for [[User:Nicky_Perian/Visual_Studio_10_Autobuild]]

[[Category:Compiling viewer]]

Viewer 2 Microsoft Windows Builds

2012-05-08T23:31:07Z

Ima Mechanique: /* Set up your source code tree */

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

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

{{KBnote|Following this recipe will probably take 6 to 12 hours of wall-clock time, and 2 to 6 hours of your time, if you're starting from a fresh Windows XP/Vista/7 system.}}

== Establish your programming environment ==

This is needed for compiling any viewer based on the LL open source code and only needs to be done once.

=== Install and update Visual Studio and SDKs ===

*Install [http://www.microsoft.com/visualstudio/en-us/products/2010-editions/visual-cpp-express Visual C++ 2010 Express] (Web install) or [http://go.microsoft.com/?linkid=9709969 Visual C++ 2010 Express] (ISO)
*Install [http://www.microsoft.com/downloads/en/details.aspx?FamilyID=a7b7a05e-6de6-4d3a-a423-37bf0912db84&displaylang=en Microsoft Visual C++ 2010 Redistributable Package]
*Install [http://www.microsoft.com/downloads/en/details.aspx?FamilyID=6B6C21D2-2006-4AFA-9702-529FA782D63B Windows SDK for Windows 7 and .NET Framework 4] (Web install) [Note: uncheck the Redistributable Package option to prevent installation failure] or [http://www.microsoft.com/downloads/en/details.aspx?FamilyID=35aeda01-421d-4ba5-b44b-543dc8c33a20 Windows SDK for Windows 7 and .NET Framework 4] (ISO)
*Install [http://www.microsoft.com/downloads/en/details.aspx?displaylang=en&FamilyID=3021d52b-514e-41d3-ad02-438a3ba730ba DirectX SDK (June 2010)]
*Run [http://www.update.microsoft.com/microsoftupdate/v6 Microsoft Update], and keep running it until no updates are needed. This may take 6~8 iterations on older versions of windows.
** For Windows Vista and Windows 7, you need to select "Get updates from other Microsoft products" to get the updates for Visual Studio.
** For Windows XP, use the provided link above. The Windows Update menu item on your computer is not the correct updater to use.
** During the update cycles make sure you have picked up [http://www.microsoft.com/downloads/en/confirmation.aspx?FamilyID=75568aa6-8107-475d-948a-ef22627e57a5 Microsoft Visual Studio 2010 Service Pack 1] (Web install) or [http://go.microsoft.com/fwlink/?LinkId=210710 Microsoft Visual Studio 2010 Service Pack 1] (ISO)

=== Install required development tools ===

{{KBnote|The order of the following installations should not matter.}}
{{KBnote|If the installer for a particular package does not update your PATH environment variable you will have to do this manually.}}

* '''CMake''' ([http://www.cmake.org/HTML/Download.html download CMake])
** This should be version 2.8.4 (or above in the 2.8.x series).
**Add the <code>\bin</code> directory to your path.
* '''Python''' (either [http://www.python.org/download/ Standard Python] or [http://www.activestate.com/activepython/downloads ActivePython])
** Version 2.7.1 works with the build scripts.
* '''Mercurial''' (either [http://tortoisehg.bitbucket.org/ TortoiseHg] or [http://mercurial.selenic.com/ Mercurial Hg])
**Create a new file <code>%USERPROFILE%\Mercurial.ini</code> and in it put your Second Life name and optionally your email address:
[ui]
username = John Doe <john@example.com>
* '''Cygwin''' ([http://www.cygwin.com/ download Cygwin])
** When you run the cygwin setup utility make sure you have selected to install '''unzip''' (under "Archives"), '''bison''', '''flex''', '''patchutils''' (all located under "devel"), and '''curl''' (under "Web"), which are not part of the default install. Do not install Cygwin Python or Mercurial. You won't need to use the Cygwin shell for anything.
**Add the <code>cygwin\bin</code> directory to the '''very end''' of your path and make sure it stays that way.

=== Install optional development tools ===

* [http://code.google.com/p/unsis/downloads/list Unicode NSIS (Nullsoft Scriptable Install System)]
** This is the package installer used to build <code>Second_Life_<version-code>_LindenDeveloper_Setup.exe</code>. You only need this package if you are going to distribute the viewer you compile or if you want to install it locally.
*: In the [[#Configuring_the_Viewer|Configure VS2010 step]] below you will need to add a line in the '''Executable Directories''' section:
*:* 64 bit systems use <code>%ProgramFiles(x86)%\NSIS\Unicode</code>
*:* 32 bit systems use <code>%ProgramFiles%\NSIS\Unicode</code>
* [http://notepadplusplus.org/ Notepad++]
** You need to use an editor that conforms to the [[Coding Standard]]. In particular, you must not check in files with DOS line endings except in very limited circumstances; see [[How to avoid DOS line endings in Windows tools]].
* [[Mercurial_Tools]] (strongly recommended)
** When you are following these instructions you will be updating the <code>%USERPROFILE%\Mercurial.ini</code> file you created when you installed Mercurial.

=== Install Autobuild ===
* Follow the directions at [[Autobuild#Getting_Autobuild|Getting Autobuild]] to install Autobuild
* Add an environment variable, so that autobuild doesn't default to using (or trying) older compiler versions:
** Right-click "My Computer" and select '''Properties''' or press the windows logo key and the pause key at the same time.
** For XP, when the Properties dialog opens, click the '''Advanced''' tab followed by the '''Environmental Variables''' button. This will open a new window with a list of System and User variables. For Vista and later, when the System Properties window opens, click the '''Advanced system settings''' on the left column, then click '''Environment Variables...'''
** In the User section, click '''New'''. Set '''Variable Name''' to AUTOBUILD_VSVER and set '''Variable Value''' to 100.
** Click the OK/Close buttons to close all the windows.

=== Configure VC2010 ===
While you may choose to use autobuild for all your compiling you still need to establish certain settings internal to VC2010.

*Start the IDE

*Navigate to '''Tools''' > '''Options''' > '''Projects and Solutions''' > '''Build and Run''' and set '''maximum number of parallel projects builds''' to <code>1</code>.

* (VC Express only) Enable '''Tools''' > '''Settings''' > '''Expert Settings''' to get the '''Build''' (and other) menus. If you already have a '''Build''' menu you do not need to perform this step.

{{KBnote|The following steps require an open visual studio project. It does not matter which project you use, as you will only change some global settings used by all projects when they are opened. The open project itself won't be changed.}}

You need to set a number of paths.
* Open any existing project you may have or make a New Project.

At the bottom on the Solution Explorer you will see three tabs.
*Click the one on the right labeled '''Property Manager'''. (The name may be somewhat truncated.)

[[File:VS2010_Property_Manager.PNG|100px]]
[[:File:VS2010_Property_Manager.PNG|Example image]]

*On the left side click to expand any project and then click again to expand the '''Release''' folder.

[[File:VS2010_Project_Config.PNG|100px]]
[[:File:VS2010_Project_Config.PNG|Example image]]

*Right click on '''Microsoft.Cpp.Win32.user'''.

*Pick '''Properties''' > '''VC++ Directories'''.

This is where the build environment is pulled together into a functional VC2010 build system and also where much hand wringing, hair pulling, and fist pounding frustration takes place.

*Set '''Executable Directories''' to:

$(ExecutablePath)
$(DXSDK_DIR)
$(WindowsSdkDir)\Bin
C:\cygwin\bin
$(SystemRoot)

[[File:32BitExecutableDirectories.png|100px]]
[[:File:32BitExecutableDirectories.png|32 bit Executable Directories example image]]

*Set '''Include Directories''' to:

$(WindowsSdkDir)\Include
$(WindowsSdkDir)\Include\gl
$(DXSDK_DIR)\Include

[[File:32BitIncludeDirectories.png|100px]]
[[:File:32BitIncludeDirectories.png|32 bit Include Directories example image]]

*Set '''Library Directories''' to:

$(WindowsSdkDir)\Lib
$(DXSDK_DIR)

[[File:32BitLibraryDirectories.png|100px]]
[[:File:32BitLibraryDirectories.png|32 bit Library Directories example image]]

== Set up your source code tree ==

Plan your directory structure ahead of time. If you are going to be producing changes or patches you will be cloning a copy of an unaltered source code tree for every change or patch you make, so you might want to have all this work stored in it's own directory.

To get a copy of the source code tree:
* Open up a DOS Command window
* CD to where you want to install viewer-release. Do not have any spaces in this path.
* Do:
hg clone <nowiki>http://hg.secondlife.com/viewer-release</nowiki>

Let's say some time has gone by since you have performed the previous steps and now you want to develop a change or work on a jira. You will update your clean local repository with all the changes committed to viewer-release since you last synchronized your files:
* CD into <code>viewer-release</code>
* Do:
hg pull -u

* Move up one level from <code>viewer-release</code>
* Do:
hg clone viewer-release VWR-nnnnn
Note: <code>nnnnn</code> is the jira number. You can also clone to a name of your choosing if you are making changes not associated with the LL jira system.

== Prepare third party libraries ==
Most third party libraries needed to build the viewer will be automatically downloaded for you and installed into the build directory within your source tree during the [[#Configuring_the_Viewer|configuration step]] below. Some few need to be manually set up, though, when using an open source developer configuration (<code>Release'''OS'''</code>, <code>RelWithDebInfo'''OS'''</code> or <code>Debug'''OS'''</code>)

=== Fmod method 1 (using autobuild) ===

CD to where you want to install the 3p-fmod repository and do:
hg clone <nowiki>https://bitbucket.org/lindenlab/3p-fmod</nowiki>

CD into the <code>3p-fmod</code> directory you created and build it:
autobuild build --all

Package the results:
autobuild package

Update autobuild with the filename and hash just displayed. CD to the directory where you cloned viewer-development and do:

copy autobuild.xml my_autobuild.xml
set AUTOBUILD_CONFIG_FILE=my_autobuild.xml
autobuild installables edit fmod platform=windows hash=<hash> url=file:///<fmod-filespec>

Example:

copy autobuild.xml my_autobuild.xml
autobuild installables edit fmod platform=windows hash=0f196f00e7dff49f22252efb68525658 url=file:///C:/3p-fmod/fmod-3.75-windows-20110531.tar.bz2

{{KBnote|Having to copy <code>autobuild.xml</code> and modify the copy from within a cloned repository is a lot of work for every repository you make, but this is the only way to guarantee you pick up upstream changes to <code>autobuild.xml</code> and do not send up a modified <code>autobuild.xml</code> when you do an hg push.}}

=== Fmod method 2 (using switches) ===
[To be written up]

== Configuring the Viewer Build ==

Fmod is the audio library the viewer uses. If you are compiling with Fmod you will need to do:
set AUTOBUILD_CONFIG_FILE=my_autobuild.xml

The environment variable <code>AUTOBUILD_INSTALLABLE_CACHE</code> controls the placement of library files downloaded as part of the configure process. If you do not want these library files going into your Windows <code>%TEMP%</code> directory define the environment variable to point to some other location you have established:
set AUTOBUILD_INSTALLABLE_CACHE=E:\SSfiles\Libraries

At the command line in the source tree's root directory (presumably a directory you have cloned from viewer-development, as it is not a good idea to work in viewer-development, unless you are only compiling for youself) e.g. <code>C:\linden\VWR-12345\</code>) run:
autobuild configure -c [CONFIGURATION]
where <code>[CONFIGURATION]</code> is one of those listed at [[Building the Viewer with Autobuild#Build a desired configuration]] (<code>ReleaseOS</code>, <code>RelWithDebInfoOS</code>, <code>DebugOS</code>)

=== Configuration Switches ===
There are a number of switches you can use to modify the configuration process. The name of each switch is followed by its type and then by the value you want to set.

* '''FMOD''' (bool) controls if the Fmod package is incorporated into the viewer. You must have performed the Fmod installation steps in [[Viewer_2_Microsoft_Windows_Builds#Fmod_method_1_.28using_autobuild.29]] for this to work.
* '''LL_TESTS''' (bool) controls if the tests are compiled and run. There are quite a lot of them so excluding them is recommended unless you have some reason to need one or more of them.
* '''PACKAGE''' (bool) controls if the package step is run. You must have installed NSIS described in [[Viewer_2_Microsoft_Windows_Builds#Install_optional_development_tools]] for this to work.

{{KBnote|'''OFF''' and '''NO''' are the same as '''FALSE'''; anything else is considered to be '''TRUE'''.}}

Example:
autobuild configure -c ReleaseOS -- -DLL_TESTS:BOOL=FALSE -DPACKAGE:BOOL=FALSE -DFMOD:BOOL=TRUE

== Compiling the Viewer ==
=== Compiling the viewer with autobuild ===
You can compile the viewer with either autobuild (the encouraged/supported method) or with the VS IDE.

When compiling with autobuild you will have the best chance of success if you work from within a preconfigured Command Prompt window. Depending on how your computer has been set up there are two possible ways to open this window and you need to find which works in your particular case:
*Method 1
**From '''All Programs''' Navigate into the '''Microsoft Windows SDK V7.1''' program menu
**Click on '''Windows SDK 7.1 Command Prompt'''
*Method 2
**From '''All Programs''' Navigate into the '''Microsoft Visual Studio 2010''' program menu
**Click on '''Microsoft Visual Studio Command Prompt (2010)'''

{{KBcaution|If you are building with Fmod and have followed the previous Fmod setup instructions AND you are now using a new command window you will need to redo the <code>set AUTOBUILD_CONFIG_FILE{{=}}my_autobuild.xml</code>.}}

*Run:
autobuild build -c [CONFIGURATION] --no-configure

There are some useful switches to know about, so your commands may look like this:
autobuild configure -c ReleaseOS -- -DLL_TESTS:BOOL=FALSE -DPACKAGE:BOOL=FALSE -DFMOD:BOOL=TRUE
autobuild build -c ReleaseOS --no-configure

{{KBnote|It is possible to use autobuild to do both the configure step (only needed once) and the build step with one command. I find it is clearer and saves a bit of time if these steps are done separately.}}

{{KBnote|Do not be alarmed if you see groups of messages with '''warning LNK4099: PDB''' in them.}}

=== Compiling the viewer with the IDE ===

The autobuild configure step created the <code>\build-vc100</code> directory at the root of the source tree. In here is the <code>SecondLife.sln</code> solution file.

Start the IDE and open this solution.

You might want to change the build type in the drop-down located in the toolbar from '''Debug''' to '''Release''' or '''RelWithDebInfo'''.

[[File:VS2010BuildType.png|100px]]
[[:File:VS2010BuildType.png|Changing build type example image]]

You need to adjust the Platform Toolset setting.
* Select all the projects in the Solution Explorer list on the left of the screen.
** Click on the first project and scroll to the bottom of this list and {{K|shift}}-click on the last project.
* Right click on the selected list
* Navigate to '''Properties''' > '''Configuration Properties''' > '''General''' > '''Platform Toolset'''
* Change this value to <code>Windows7.1SDK</code>

* Push {{K|F7}} to start the compiler.

== Running your newly built viewer ==
=== Running from a desktop shortcut ===
* Make a desktop shortcut for <code>Drive:\your-path\build-vc100\newview\Release\secondlife-bin.exe</code>

* Right-click the shortcut
* Select '''Properties'''
* Set '''Start in:''' to <code>Drive:\your-path\indra\newview</code>

=== Running from within the IDE ===
* In the Solution Explorer pane right click on '''secondlife-bin'''
** Click '''Set as StartUp Project'''
** Pick '''Properties''' > '''Configuration Properties''' > '''Debugging'''
*** Set '''Command''' to <code>Drive:\your-path\build-vc100\newview\Release\secondlife-bin.exe</code> (adjust <code>Release</code> to the type of build you are doing, e.g. <code>RelWithDebInfo</code>)
*** Set '''Working Directory''' to <code>..\..\indra\newview</code>

== Handling Problems ==

If you encounter errors or run into problems following the instructions above, please first check whether someone else already had the same issue. A solution might be known already. See the [[#Common_Issues.2FBugs.2FGlitches_And_Solutions|issue list below]], check [[{{TALKPAGENAME}}|the talk page]] (and report useful experiences there) and search our [[issue tracker]]. Even when no description of your problem has been written down yet, someone might know about it, so get in touch with the community to [[#Getting_help|get help]].

=== Getting help ===
* Subscribe to [[OpenSource-Dev|OpenSource-Dev Mailing List]] ([https://lists.secondlife.com/cgi-bin/mailman/listinfo/opensource-dev subscribe]) and post your question there.
* For faster response, join the general open source viewer discussion and development [[IRC]] channel [irc://irc.freenode.org/opensl #opensl on freenode]. Hopefully a helpful person is online when you ask your question.

=== Common Issues/Bugs/Glitches And Solutions ===

==== Not being able to find objidl.h in the Microsoft Windows SDK, when compiling llwindow ====
https://lists.secondlife.com/pipermail/opensource-dev/2011-April/006562.html
* Can be caused by path problems or some installation conflicts with the DirectX SDK.

==== stdint.h typedef conflicts between Quicktime and VS2010 ====
https://lists.secondlife.com/pipermail/opensource-dev/2011-April/006565.html
*: Can be solved by some small edits to header files to make sure the two don't bash on each other.

==== Eliminate deprecated switches, messages, and use memory more efficiently ====

The VS2010 compiler uses a lot of memory while compiling the viewer. If you run out of memory you will start to page heavily and your compile time will become much longer. The /Zm1000 switch affects compiler memory usage.

You may see this message while compiling:
use 'EHsc' instead of 'GX'

Here is how to free up some memory the compiler allocates and to eliminate these messages:

*Edit <code>\CMake 2.8\share\cmake-2.8\Modules\Platform\Windows-cl.cmake</code>

*Replace line 156 with:
IF(MSVC10)
SET(CMAKE_CXX_FLAGS_INIT "/DWIN32 /D_WINDOWS /W3 /EHsc /GR")
ELSEIF(NOT MSVC10)
SET(CMAKE_CXX_FLAGS_INIT "/DWIN32 /D_WINDOWS /W3 /Zm1000 /EHsc /GR")
ENDIF(MSVC10)

*Replace line 172 with:
IF(MSVC10)
SET(CMAKE_CXX_FLAGS_INIT "/DWIN32 /D_WINDOWS /W3 /EHsc /GR")
ELSEIF(NOT MSVC10)
SET(CMAKE_CXX_FLAGS_INIT "/DWIN32 /D_WINDOWS /W3 /Zm1000 /GX /GR")
ENDIF(MSVC10)

*Replace line 184 with:
IF(MSVC10)
SET(CMAKE_CXX_FLAGS_INIT "/DWIN32 /D_WINDOWS /W3 /EHsc /GR")
ELSEIF(NOT MSVC10)
SET(CMAKE_CXX_FLAGS_INIT "/DWIN32 /D_WINDOWS /W3 /Zm1000 /GX /GR")
ENDIF(MSVC10)

== References ==

Tip of the hat to Nicky_Perian for [[User:Nicky_Perian/Visual_Studio_10_Autobuild]]

[[Category:Compiling viewer]]

Viewer 2 Microsoft Windows Builds

2012-05-08T23:30:41Z

Ima Mechanique: /* Set up your source code tree */

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

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

{{KBnote|Following this recipe will probably take 6 to 12 hours of wall-clock time, and 2 to 6 hours of your time, if you're starting from a fresh Windows XP/Vista/7 system.}}

== Establish your programming environment ==

This is needed for compiling any viewer based on the LL open source code and only needs to be done once.

=== Install and update Visual Studio and SDKs ===

*Install [http://www.microsoft.com/visualstudio/en-us/products/2010-editions/visual-cpp-express Visual C++ 2010 Express] (Web install) or [http://go.microsoft.com/?linkid=9709969 Visual C++ 2010 Express] (ISO)
*Install [http://www.microsoft.com/downloads/en/details.aspx?FamilyID=a7b7a05e-6de6-4d3a-a423-37bf0912db84&displaylang=en Microsoft Visual C++ 2010 Redistributable Package]
*Install [http://www.microsoft.com/downloads/en/details.aspx?FamilyID=6B6C21D2-2006-4AFA-9702-529FA782D63B Windows SDK for Windows 7 and .NET Framework 4] (Web install) [Note: uncheck the Redistributable Package option to prevent installation failure] or [http://www.microsoft.com/downloads/en/details.aspx?FamilyID=35aeda01-421d-4ba5-b44b-543dc8c33a20 Windows SDK for Windows 7 and .NET Framework 4] (ISO)
*Install [http://www.microsoft.com/downloads/en/details.aspx?displaylang=en&FamilyID=3021d52b-514e-41d3-ad02-438a3ba730ba DirectX SDK (June 2010)]
*Run [http://www.update.microsoft.com/microsoftupdate/v6 Microsoft Update], and keep running it until no updates are needed. This may take 6~8 iterations on older versions of windows.
** For Windows Vista and Windows 7, you need to select "Get updates from other Microsoft products" to get the updates for Visual Studio.
** For Windows XP, use the provided link above. The Windows Update menu item on your computer is not the correct updater to use.
** During the update cycles make sure you have picked up [http://www.microsoft.com/downloads/en/confirmation.aspx?FamilyID=75568aa6-8107-475d-948a-ef22627e57a5 Microsoft Visual Studio 2010 Service Pack 1] (Web install) or [http://go.microsoft.com/fwlink/?LinkId=210710 Microsoft Visual Studio 2010 Service Pack 1] (ISO)

=== Install required development tools ===

{{KBnote|The order of the following installations should not matter.}}
{{KBnote|If the installer for a particular package does not update your PATH environment variable you will have to do this manually.}}

* '''CMake''' ([http://www.cmake.org/HTML/Download.html download CMake])
** This should be version 2.8.4 (or above in the 2.8.x series).
**Add the <code>\bin</code> directory to your path.
* '''Python''' (either [http://www.python.org/download/ Standard Python] or [http://www.activestate.com/activepython/downloads ActivePython])
** Version 2.7.1 works with the build scripts.
* '''Mercurial''' (either [http://tortoisehg.bitbucket.org/ TortoiseHg] or [http://mercurial.selenic.com/ Mercurial Hg])
**Create a new file <code>%USERPROFILE%\Mercurial.ini</code> and in it put your Second Life name and optionally your email address:
[ui]
username = John Doe <john@example.com>
* '''Cygwin''' ([http://www.cygwin.com/ download Cygwin])
** When you run the cygwin setup utility make sure you have selected to install '''unzip''' (under "Archives"), '''bison''', '''flex''', '''patchutils''' (all located under "devel"), and '''curl''' (under "Web"), which are not part of the default install. Do not install Cygwin Python or Mercurial. You won't need to use the Cygwin shell for anything.
**Add the <code>cygwin\bin</code> directory to the '''very end''' of your path and make sure it stays that way.

=== Install optional development tools ===

* [http://code.google.com/p/unsis/downloads/list Unicode NSIS (Nullsoft Scriptable Install System)]
** This is the package installer used to build <code>Second_Life_<version-code>_LindenDeveloper_Setup.exe</code>. You only need this package if you are going to distribute the viewer you compile or if you want to install it locally.
*: In the [[#Configuring_the_Viewer|Configure VS2010 step]] below you will need to add a line in the '''Executable Directories''' section:
*:* 64 bit systems use <code>%ProgramFiles(x86)%\NSIS\Unicode</code>
*:* 32 bit systems use <code>%ProgramFiles%\NSIS\Unicode</code>
* [http://notepadplusplus.org/ Notepad++]
** You need to use an editor that conforms to the [[Coding Standard]]. In particular, you must not check in files with DOS line endings except in very limited circumstances; see [[How to avoid DOS line endings in Windows tools]].
* [[Mercurial_Tools]] (strongly recommended)
** When you are following these instructions you will be updating the <code>%USERPROFILE%\Mercurial.ini</code> file you created when you installed Mercurial.

=== Install Autobuild ===
* Follow the directions at [[Autobuild#Getting_Autobuild|Getting Autobuild]] to install Autobuild
* Add an environment variable, so that autobuild doesn't default to using (or trying) older compiler versions:
** Right-click "My Computer" and select '''Properties''' or press the windows logo key and the pause key at the same time.
** For XP, when the Properties dialog opens, click the '''Advanced''' tab followed by the '''Environmental Variables''' button. This will open a new window with a list of System and User variables. For Vista and later, when the System Properties window opens, click the '''Advanced system settings''' on the left column, then click '''Environment Variables...'''
** In the User section, click '''New'''. Set '''Variable Name''' to AUTOBUILD_VSVER and set '''Variable Value''' to 100.
** Click the OK/Close buttons to close all the windows.

=== Configure VC2010 ===
While you may choose to use autobuild for all your compiling you still need to establish certain settings internal to VC2010.

*Start the IDE

*Navigate to '''Tools''' > '''Options''' > '''Projects and Solutions''' > '''Build and Run''' and set '''maximum number of parallel projects builds''' to <code>1</code>.

* (VC Express only) Enable '''Tools''' > '''Settings''' > '''Expert Settings''' to get the '''Build''' (and other) menus. If you already have a '''Build''' menu you do not need to perform this step.

{{KBnote|The following steps require an open visual studio project. It does not matter which project you use, as you will only change some global settings used by all projects when they are opened. The open project itself won't be changed.}}

You need to set a number of paths.
* Open any existing project you may have or make a New Project.

At the bottom on the Solution Explorer you will see three tabs.
*Click the one on the right labeled '''Property Manager'''. (The name may be somewhat truncated.)

[[File:VS2010_Property_Manager.PNG|100px]]
[[:File:VS2010_Property_Manager.PNG|Example image]]

*On the left side click to expand any project and then click again to expand the '''Release''' folder.

[[File:VS2010_Project_Config.PNG|100px]]
[[:File:VS2010_Project_Config.PNG|Example image]]

*Right click on '''Microsoft.Cpp.Win32.user'''.

*Pick '''Properties''' > '''VC++ Directories'''.

This is where the build environment is pulled together into a functional VC2010 build system and also where much hand wringing, hair pulling, and fist pounding frustration takes place.

*Set '''Executable Directories''' to:

$(ExecutablePath)
$(DXSDK_DIR)
$(WindowsSdkDir)\Bin
C:\cygwin\bin
$(SystemRoot)

[[File:32BitExecutableDirectories.png|100px]]
[[:File:32BitExecutableDirectories.png|32 bit Executable Directories example image]]

*Set '''Include Directories''' to:

$(WindowsSdkDir)\Include
$(WindowsSdkDir)\Include\gl
$(DXSDK_DIR)\Include

[[File:32BitIncludeDirectories.png|100px]]
[[:File:32BitIncludeDirectories.png|32 bit Include Directories example image]]

*Set '''Library Directories''' to:

$(WindowsSdkDir)\Lib
$(DXSDK_DIR)

[[File:32BitLibraryDirectories.png|100px]]
[[:File:32BitLibraryDirectories.png|32 bit Library Directories example image]]

== Set up your source code tree ==

Plan your directory structure ahead of time. If you are going to be producing changes or patches you will be cloning a copy of an unaltered source code tree for every change or patch you make, so you might want to have all this work stored in it's own directory.

To get a copy of the source code tree:
* Open up a DOS Command window
* CD to where you want to install viewer-release. Do not have any spaces in this path.
* Do:
hg clone <nowiki>http://hg.secondlife.com/viewer-release</nowiki>

Let's say some time has gone by since you have performed the previous steps and now you want to develop a change or work on a jira. You will update your clean local repository with all the changes committed to viewer-release since you last synchronized your files:
* CD into <code>viewer-release</code>
* Do:
hg pull -u

* Move up one level from <code>viewer-release</code>
* Do:
hg clone viewer-releaseVWR-nnnnn
Note: <code>nnnnn</code> is the jira number. You can also clone to a name of your choosing if you are making changes not associated with the LL jira system.

== Prepare third party libraries ==
Most third party libraries needed to build the viewer will be automatically downloaded for you and installed into the build directory within your source tree during the [[#Configuring_the_Viewer|configuration step]] below. Some few need to be manually set up, though, when using an open source developer configuration (<code>Release'''OS'''</code>, <code>RelWithDebInfo'''OS'''</code> or <code>Debug'''OS'''</code>)

=== Fmod method 1 (using autobuild) ===

CD to where you want to install the 3p-fmod repository and do:
hg clone <nowiki>https://bitbucket.org/lindenlab/3p-fmod</nowiki>

CD into the <code>3p-fmod</code> directory you created and build it:
autobuild build --all

Package the results:
autobuild package

Update autobuild with the filename and hash just displayed. CD to the directory where you cloned viewer-development and do:

copy autobuild.xml my_autobuild.xml
set AUTOBUILD_CONFIG_FILE=my_autobuild.xml
autobuild installables edit fmod platform=windows hash=<hash> url=file:///<fmod-filespec>

Example:

copy autobuild.xml my_autobuild.xml
autobuild installables edit fmod platform=windows hash=0f196f00e7dff49f22252efb68525658 url=file:///C:/3p-fmod/fmod-3.75-windows-20110531.tar.bz2

{{KBnote|Having to copy <code>autobuild.xml</code> and modify the copy from within a cloned repository is a lot of work for every repository you make, but this is the only way to guarantee you pick up upstream changes to <code>autobuild.xml</code> and do not send up a modified <code>autobuild.xml</code> when you do an hg push.}}

=== Fmod method 2 (using switches) ===
[To be written up]

== Configuring the Viewer Build ==

Fmod is the audio library the viewer uses. If you are compiling with Fmod you will need to do:
set AUTOBUILD_CONFIG_FILE=my_autobuild.xml

The environment variable <code>AUTOBUILD_INSTALLABLE_CACHE</code> controls the placement of library files downloaded as part of the configure process. If you do not want these library files going into your Windows <code>%TEMP%</code> directory define the environment variable to point to some other location you have established:
set AUTOBUILD_INSTALLABLE_CACHE=E:\SSfiles\Libraries

At the command line in the source tree's root directory (presumably a directory you have cloned from viewer-development, as it is not a good idea to work in viewer-development, unless you are only compiling for youself) e.g. <code>C:\linden\VWR-12345\</code>) run:
autobuild configure -c [CONFIGURATION]
where <code>[CONFIGURATION]</code> is one of those listed at [[Building the Viewer with Autobuild#Build a desired configuration]] (<code>ReleaseOS</code>, <code>RelWithDebInfoOS</code>, <code>DebugOS</code>)

=== Configuration Switches ===
There are a number of switches you can use to modify the configuration process. The name of each switch is followed by its type and then by the value you want to set.

* '''FMOD''' (bool) controls if the Fmod package is incorporated into the viewer. You must have performed the Fmod installation steps in [[Viewer_2_Microsoft_Windows_Builds#Fmod_method_1_.28using_autobuild.29]] for this to work.
* '''LL_TESTS''' (bool) controls if the tests are compiled and run. There are quite a lot of them so excluding them is recommended unless you have some reason to need one or more of them.
* '''PACKAGE''' (bool) controls if the package step is run. You must have installed NSIS described in [[Viewer_2_Microsoft_Windows_Builds#Install_optional_development_tools]] for this to work.

{{KBnote|'''OFF''' and '''NO''' are the same as '''FALSE'''; anything else is considered to be '''TRUE'''.}}

Example:
autobuild configure -c ReleaseOS -- -DLL_TESTS:BOOL=FALSE -DPACKAGE:BOOL=FALSE -DFMOD:BOOL=TRUE

== Compiling the Viewer ==
=== Compiling the viewer with autobuild ===
You can compile the viewer with either autobuild (the encouraged/supported method) or with the VS IDE.

When compiling with autobuild you will have the best chance of success if you work from within a preconfigured Command Prompt window. Depending on how your computer has been set up there are two possible ways to open this window and you need to find which works in your particular case:
*Method 1
**From '''All Programs''' Navigate into the '''Microsoft Windows SDK V7.1''' program menu
**Click on '''Windows SDK 7.1 Command Prompt'''
*Method 2
**From '''All Programs''' Navigate into the '''Microsoft Visual Studio 2010''' program menu
**Click on '''Microsoft Visual Studio Command Prompt (2010)'''

{{KBcaution|If you are building with Fmod and have followed the previous Fmod setup instructions AND you are now using a new command window you will need to redo the <code>set AUTOBUILD_CONFIG_FILE{{=}}my_autobuild.xml</code>.}}

*Run:
autobuild build -c [CONFIGURATION] --no-configure

There are some useful switches to know about, so your commands may look like this:
autobuild configure -c ReleaseOS -- -DLL_TESTS:BOOL=FALSE -DPACKAGE:BOOL=FALSE -DFMOD:BOOL=TRUE
autobuild build -c ReleaseOS --no-configure

{{KBnote|It is possible to use autobuild to do both the configure step (only needed once) and the build step with one command. I find it is clearer and saves a bit of time if these steps are done separately.}}

{{KBnote|Do not be alarmed if you see groups of messages with '''warning LNK4099: PDB''' in them.}}

=== Compiling the viewer with the IDE ===

The autobuild configure step created the <code>\build-vc100</code> directory at the root of the source tree. In here is the <code>SecondLife.sln</code> solution file.

Start the IDE and open this solution.

You might want to change the build type in the drop-down located in the toolbar from '''Debug''' to '''Release''' or '''RelWithDebInfo'''.

[[File:VS2010BuildType.png|100px]]
[[:File:VS2010BuildType.png|Changing build type example image]]

You need to adjust the Platform Toolset setting.
* Select all the projects in the Solution Explorer list on the left of the screen.
** Click on the first project and scroll to the bottom of this list and {{K|shift}}-click on the last project.
* Right click on the selected list
* Navigate to '''Properties''' > '''Configuration Properties''' > '''General''' > '''Platform Toolset'''
* Change this value to <code>Windows7.1SDK</code>

* Push {{K|F7}} to start the compiler.

== Running your newly built viewer ==
=== Running from a desktop shortcut ===
* Make a desktop shortcut for <code>Drive:\your-path\build-vc100\newview\Release\secondlife-bin.exe</code>

* Right-click the shortcut
* Select '''Properties'''
* Set '''Start in:''' to <code>Drive:\your-path\indra\newview</code>

=== Running from within the IDE ===
* In the Solution Explorer pane right click on '''secondlife-bin'''
** Click '''Set as StartUp Project'''
** Pick '''Properties''' > '''Configuration Properties''' > '''Debugging'''
*** Set '''Command''' to <code>Drive:\your-path\build-vc100\newview\Release\secondlife-bin.exe</code> (adjust <code>Release</code> to the type of build you are doing, e.g. <code>RelWithDebInfo</code>)
*** Set '''Working Directory''' to <code>..\..\indra\newview</code>

== Handling Problems ==

If you encounter errors or run into problems following the instructions above, please first check whether someone else already had the same issue. A solution might be known already. See the [[#Common_Issues.2FBugs.2FGlitches_And_Solutions|issue list below]], check [[{{TALKPAGENAME}}|the talk page]] (and report useful experiences there) and search our [[issue tracker]]. Even when no description of your problem has been written down yet, someone might know about it, so get in touch with the community to [[#Getting_help|get help]].

=== Getting help ===
* Subscribe to [[OpenSource-Dev|OpenSource-Dev Mailing List]] ([https://lists.secondlife.com/cgi-bin/mailman/listinfo/opensource-dev subscribe]) and post your question there.
* For faster response, join the general open source viewer discussion and development [[IRC]] channel [irc://irc.freenode.org/opensl #opensl on freenode]. Hopefully a helpful person is online when you ask your question.

=== Common Issues/Bugs/Glitches And Solutions ===

==== Not being able to find objidl.h in the Microsoft Windows SDK, when compiling llwindow ====
https://lists.secondlife.com/pipermail/opensource-dev/2011-April/006562.html
* Can be caused by path problems or some installation conflicts with the DirectX SDK.

==== stdint.h typedef conflicts between Quicktime and VS2010 ====
https://lists.secondlife.com/pipermail/opensource-dev/2011-April/006565.html
*: Can be solved by some small edits to header files to make sure the two don't bash on each other.

==== Eliminate deprecated switches, messages, and use memory more efficiently ====

The VS2010 compiler uses a lot of memory while compiling the viewer. If you run out of memory you will start to page heavily and your compile time will become much longer. The /Zm1000 switch affects compiler memory usage.

You may see this message while compiling:
use 'EHsc' instead of 'GX'

Here is how to free up some memory the compiler allocates and to eliminate these messages:

*Edit <code>\CMake 2.8\share\cmake-2.8\Modules\Platform\Windows-cl.cmake</code>

*Replace line 156 with:
IF(MSVC10)
SET(CMAKE_CXX_FLAGS_INIT "/DWIN32 /D_WINDOWS /W3 /EHsc /GR")
ELSEIF(NOT MSVC10)
SET(CMAKE_CXX_FLAGS_INIT "/DWIN32 /D_WINDOWS /W3 /Zm1000 /EHsc /GR")
ENDIF(MSVC10)

*Replace line 172 with:
IF(MSVC10)
SET(CMAKE_CXX_FLAGS_INIT "/DWIN32 /D_WINDOWS /W3 /EHsc /GR")
ELSEIF(NOT MSVC10)
SET(CMAKE_CXX_FLAGS_INIT "/DWIN32 /D_WINDOWS /W3 /Zm1000 /GX /GR")
ENDIF(MSVC10)

*Replace line 184 with:
IF(MSVC10)
SET(CMAKE_CXX_FLAGS_INIT "/DWIN32 /D_WINDOWS /W3 /EHsc /GR")
ELSEIF(NOT MSVC10)
SET(CMAKE_CXX_FLAGS_INIT "/DWIN32 /D_WINDOWS /W3 /Zm1000 /GX /GR")
ENDIF(MSVC10)

== References ==

Tip of the hat to Nicky_Perian for [[User:Nicky_Perian/Visual_Studio_10_Autobuild]]

[[Category:Compiling viewer]]

Viewer 2 Microsoft Windows Builds

2012-05-08T23:30:10Z

Ima Mechanique: /* Set up your source code tree */

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

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

{{KBnote|Following this recipe will probably take 6 to 12 hours of wall-clock time, and 2 to 6 hours of your time, if you're starting from a fresh Windows XP/Vista/7 system.}}

== Establish your programming environment ==

This is needed for compiling any viewer based on the LL open source code and only needs to be done once.

=== Install and update Visual Studio and SDKs ===

*Install [http://www.microsoft.com/visualstudio/en-us/products/2010-editions/visual-cpp-express Visual C++ 2010 Express] (Web install) or [http://go.microsoft.com/?linkid=9709969 Visual C++ 2010 Express] (ISO)
*Install [http://www.microsoft.com/downloads/en/details.aspx?FamilyID=a7b7a05e-6de6-4d3a-a423-37bf0912db84&displaylang=en Microsoft Visual C++ 2010 Redistributable Package]
*Install [http://www.microsoft.com/downloads/en/details.aspx?FamilyID=6B6C21D2-2006-4AFA-9702-529FA782D63B Windows SDK for Windows 7 and .NET Framework 4] (Web install) [Note: uncheck the Redistributable Package option to prevent installation failure] or [http://www.microsoft.com/downloads/en/details.aspx?FamilyID=35aeda01-421d-4ba5-b44b-543dc8c33a20 Windows SDK for Windows 7 and .NET Framework 4] (ISO)
*Install [http://www.microsoft.com/downloads/en/details.aspx?displaylang=en&FamilyID=3021d52b-514e-41d3-ad02-438a3ba730ba DirectX SDK (June 2010)]
*Run [http://www.update.microsoft.com/microsoftupdate/v6 Microsoft Update], and keep running it until no updates are needed. This may take 6~8 iterations on older versions of windows.
** For Windows Vista and Windows 7, you need to select "Get updates from other Microsoft products" to get the updates for Visual Studio.
** For Windows XP, use the provided link above. The Windows Update menu item on your computer is not the correct updater to use.
** During the update cycles make sure you have picked up [http://www.microsoft.com/downloads/en/confirmation.aspx?FamilyID=75568aa6-8107-475d-948a-ef22627e57a5 Microsoft Visual Studio 2010 Service Pack 1] (Web install) or [http://go.microsoft.com/fwlink/?LinkId=210710 Microsoft Visual Studio 2010 Service Pack 1] (ISO)

=== Install required development tools ===

{{KBnote|The order of the following installations should not matter.}}
{{KBnote|If the installer for a particular package does not update your PATH environment variable you will have to do this manually.}}

* '''CMake''' ([http://www.cmake.org/HTML/Download.html download CMake])
** This should be version 2.8.4 (or above in the 2.8.x series).
**Add the <code>\bin</code> directory to your path.
* '''Python''' (either [http://www.python.org/download/ Standard Python] or [http://www.activestate.com/activepython/downloads ActivePython])
** Version 2.7.1 works with the build scripts.
* '''Mercurial''' (either [http://tortoisehg.bitbucket.org/ TortoiseHg] or [http://mercurial.selenic.com/ Mercurial Hg])
**Create a new file <code>%USERPROFILE%\Mercurial.ini</code> and in it put your Second Life name and optionally your email address:
[ui]
username = John Doe <john@example.com>
* '''Cygwin''' ([http://www.cygwin.com/ download Cygwin])
** When you run the cygwin setup utility make sure you have selected to install '''unzip''' (under "Archives"), '''bison''', '''flex''', '''patchutils''' (all located under "devel"), and '''curl''' (under "Web"), which are not part of the default install. Do not install Cygwin Python or Mercurial. You won't need to use the Cygwin shell for anything.
**Add the <code>cygwin\bin</code> directory to the '''very end''' of your path and make sure it stays that way.

=== Install optional development tools ===

* [http://code.google.com/p/unsis/downloads/list Unicode NSIS (Nullsoft Scriptable Install System)]
** This is the package installer used to build <code>Second_Life_<version-code>_LindenDeveloper_Setup.exe</code>. You only need this package if you are going to distribute the viewer you compile or if you want to install it locally.
*: In the [[#Configuring_the_Viewer|Configure VS2010 step]] below you will need to add a line in the '''Executable Directories''' section:
*:* 64 bit systems use <code>%ProgramFiles(x86)%\NSIS\Unicode</code>
*:* 32 bit systems use <code>%ProgramFiles%\NSIS\Unicode</code>
* [http://notepadplusplus.org/ Notepad++]
** You need to use an editor that conforms to the [[Coding Standard]]. In particular, you must not check in files with DOS line endings except in very limited circumstances; see [[How to avoid DOS line endings in Windows tools]].
* [[Mercurial_Tools]] (strongly recommended)
** When you are following these instructions you will be updating the <code>%USERPROFILE%\Mercurial.ini</code> file you created when you installed Mercurial.

=== Install Autobuild ===
* Follow the directions at [[Autobuild#Getting_Autobuild|Getting Autobuild]] to install Autobuild
* Add an environment variable, so that autobuild doesn't default to using (or trying) older compiler versions:
** Right-click "My Computer" and select '''Properties''' or press the windows logo key and the pause key at the same time.
** For XP, when the Properties dialog opens, click the '''Advanced''' tab followed by the '''Environmental Variables''' button. This will open a new window with a list of System and User variables. For Vista and later, when the System Properties window opens, click the '''Advanced system settings''' on the left column, then click '''Environment Variables...'''
** In the User section, click '''New'''. Set '''Variable Name''' to AUTOBUILD_VSVER and set '''Variable Value''' to 100.
** Click the OK/Close buttons to close all the windows.

=== Configure VC2010 ===
While you may choose to use autobuild for all your compiling you still need to establish certain settings internal to VC2010.

*Start the IDE

*Navigate to '''Tools''' > '''Options''' > '''Projects and Solutions''' > '''Build and Run''' and set '''maximum number of parallel projects builds''' to <code>1</code>.

* (VC Express only) Enable '''Tools''' > '''Settings''' > '''Expert Settings''' to get the '''Build''' (and other) menus. If you already have a '''Build''' menu you do not need to perform this step.

{{KBnote|The following steps require an open visual studio project. It does not matter which project you use, as you will only change some global settings used by all projects when they are opened. The open project itself won't be changed.}}

You need to set a number of paths.
* Open any existing project you may have or make a New Project.

At the bottom on the Solution Explorer you will see three tabs.
*Click the one on the right labeled '''Property Manager'''. (The name may be somewhat truncated.)

[[File:VS2010_Property_Manager.PNG|100px]]
[[:File:VS2010_Property_Manager.PNG|Example image]]

*On the left side click to expand any project and then click again to expand the '''Release''' folder.

[[File:VS2010_Project_Config.PNG|100px]]
[[:File:VS2010_Project_Config.PNG|Example image]]

*Right click on '''Microsoft.Cpp.Win32.user'''.

*Pick '''Properties''' > '''VC++ Directories'''.

This is where the build environment is pulled together into a functional VC2010 build system and also where much hand wringing, hair pulling, and fist pounding frustration takes place.

*Set '''Executable Directories''' to:

$(ExecutablePath)
$(DXSDK_DIR)
$(WindowsSdkDir)\Bin
C:\cygwin\bin
$(SystemRoot)

[[File:32BitExecutableDirectories.png|100px]]
[[:File:32BitExecutableDirectories.png|32 bit Executable Directories example image]]

*Set '''Include Directories''' to:

$(WindowsSdkDir)\Include
$(WindowsSdkDir)\Include\gl
$(DXSDK_DIR)\Include

[[File:32BitIncludeDirectories.png|100px]]
[[:File:32BitIncludeDirectories.png|32 bit Include Directories example image]]

*Set '''Library Directories''' to:

$(WindowsSdkDir)\Lib
$(DXSDK_DIR)

[[File:32BitLibraryDirectories.png|100px]]
[[:File:32BitLibraryDirectories.png|32 bit Library Directories example image]]

== Set up your source code tree ==

Plan your directory structure ahead of time. If you are going to be producing changes or patches you will be cloning a copy of an unaltered source code tree for every change or patch you make, so you might want to have all this work stored in it's own directory.

To get a copy of the source code tree:
* Open up a DOS Command window
* CD to where you want to install viewer-release. Do not have any spaces in this path.
* Do:
hg clone <nowiki>http://hg.secondlife.com/viewer-release</nowiki>

Let's say some time has gone by since you have performed the previous steps and now you want to develop a change or work on a jira. You will update your clean local repository with all the changes committed to viewer-releasesince you last synchronized your files:
* CD into <code>viewer-release</code>
* Do:
hg pull -u

* Move up one level from <code>viewer-release</code>
* Do:
hg clone viewer-releaseVWR-nnnnn
Note: <code>nnnnn</code> is the jira number. You can also clone to a name of your choosing if you are making changes not associated with the LL jira system.

== Prepare third party libraries ==
Most third party libraries needed to build the viewer will be automatically downloaded for you and installed into the build directory within your source tree during the [[#Configuring_the_Viewer|configuration step]] below. Some few need to be manually set up, though, when using an open source developer configuration (<code>Release'''OS'''</code>, <code>RelWithDebInfo'''OS'''</code> or <code>Debug'''OS'''</code>)

=== Fmod method 1 (using autobuild) ===

CD to where you want to install the 3p-fmod repository and do:
hg clone <nowiki>https://bitbucket.org/lindenlab/3p-fmod</nowiki>

CD into the <code>3p-fmod</code> directory you created and build it:
autobuild build --all

Package the results:
autobuild package

Update autobuild with the filename and hash just displayed. CD to the directory where you cloned viewer-development and do:

copy autobuild.xml my_autobuild.xml
set AUTOBUILD_CONFIG_FILE=my_autobuild.xml
autobuild installables edit fmod platform=windows hash=<hash> url=file:///<fmod-filespec>

Example:

copy autobuild.xml my_autobuild.xml
autobuild installables edit fmod platform=windows hash=0f196f00e7dff49f22252efb68525658 url=file:///C:/3p-fmod/fmod-3.75-windows-20110531.tar.bz2

{{KBnote|Having to copy <code>autobuild.xml</code> and modify the copy from within a cloned repository is a lot of work for every repository you make, but this is the only way to guarantee you pick up upstream changes to <code>autobuild.xml</code> and do not send up a modified <code>autobuild.xml</code> when you do an hg push.}}

=== Fmod method 2 (using switches) ===
[To be written up]

== Configuring the Viewer Build ==

Fmod is the audio library the viewer uses. If you are compiling with Fmod you will need to do:
set AUTOBUILD_CONFIG_FILE=my_autobuild.xml

The environment variable <code>AUTOBUILD_INSTALLABLE_CACHE</code> controls the placement of library files downloaded as part of the configure process. If you do not want these library files going into your Windows <code>%TEMP%</code> directory define the environment variable to point to some other location you have established:
set AUTOBUILD_INSTALLABLE_CACHE=E:\SSfiles\Libraries

At the command line in the source tree's root directory (presumably a directory you have cloned from viewer-development, as it is not a good idea to work in viewer-development, unless you are only compiling for youself) e.g. <code>C:\linden\VWR-12345\</code>) run:
autobuild configure -c [CONFIGURATION]
where <code>[CONFIGURATION]</code> is one of those listed at [[Building the Viewer with Autobuild#Build a desired configuration]] (<code>ReleaseOS</code>, <code>RelWithDebInfoOS</code>, <code>DebugOS</code>)

=== Configuration Switches ===
There are a number of switches you can use to modify the configuration process. The name of each switch is followed by its type and then by the value you want to set.

* '''FMOD''' (bool) controls if the Fmod package is incorporated into the viewer. You must have performed the Fmod installation steps in [[Viewer_2_Microsoft_Windows_Builds#Fmod_method_1_.28using_autobuild.29]] for this to work.
* '''LL_TESTS''' (bool) controls if the tests are compiled and run. There are quite a lot of them so excluding them is recommended unless you have some reason to need one or more of them.
* '''PACKAGE''' (bool) controls if the package step is run. You must have installed NSIS described in [[Viewer_2_Microsoft_Windows_Builds#Install_optional_development_tools]] for this to work.

{{KBnote|'''OFF''' and '''NO''' are the same as '''FALSE'''; anything else is considered to be '''TRUE'''.}}

Example:
autobuild configure -c ReleaseOS -- -DLL_TESTS:BOOL=FALSE -DPACKAGE:BOOL=FALSE -DFMOD:BOOL=TRUE

== Compiling the Viewer ==
=== Compiling the viewer with autobuild ===
You can compile the viewer with either autobuild (the encouraged/supported method) or with the VS IDE.

When compiling with autobuild you will have the best chance of success if you work from within a preconfigured Command Prompt window. Depending on how your computer has been set up there are two possible ways to open this window and you need to find which works in your particular case:
*Method 1
**From '''All Programs''' Navigate into the '''Microsoft Windows SDK V7.1''' program menu
**Click on '''Windows SDK 7.1 Command Prompt'''
*Method 2
**From '''All Programs''' Navigate into the '''Microsoft Visual Studio 2010''' program menu
**Click on '''Microsoft Visual Studio Command Prompt (2010)'''

{{KBcaution|If you are building with Fmod and have followed the previous Fmod setup instructions AND you are now using a new command window you will need to redo the <code>set AUTOBUILD_CONFIG_FILE{{=}}my_autobuild.xml</code>.}}

*Run:
autobuild build -c [CONFIGURATION] --no-configure

There are some useful switches to know about, so your commands may look like this:
autobuild configure -c ReleaseOS -- -DLL_TESTS:BOOL=FALSE -DPACKAGE:BOOL=FALSE -DFMOD:BOOL=TRUE
autobuild build -c ReleaseOS --no-configure

{{KBnote|It is possible to use autobuild to do both the configure step (only needed once) and the build step with one command. I find it is clearer and saves a bit of time if these steps are done separately.}}

{{KBnote|Do not be alarmed if you see groups of messages with '''warning LNK4099: PDB''' in them.}}

=== Compiling the viewer with the IDE ===

The autobuild configure step created the <code>\build-vc100</code> directory at the root of the source tree. In here is the <code>SecondLife.sln</code> solution file.

Start the IDE and open this solution.

You might want to change the build type in the drop-down located in the toolbar from '''Debug''' to '''Release''' or '''RelWithDebInfo'''.

[[File:VS2010BuildType.png|100px]]
[[:File:VS2010BuildType.png|Changing build type example image]]

You need to adjust the Platform Toolset setting.
* Select all the projects in the Solution Explorer list on the left of the screen.
** Click on the first project and scroll to the bottom of this list and {{K|shift}}-click on the last project.
* Right click on the selected list
* Navigate to '''Properties''' > '''Configuration Properties''' > '''General''' > '''Platform Toolset'''
* Change this value to <code>Windows7.1SDK</code>

* Push {{K|F7}} to start the compiler.

== Running your newly built viewer ==
=== Running from a desktop shortcut ===
* Make a desktop shortcut for <code>Drive:\your-path\build-vc100\newview\Release\secondlife-bin.exe</code>

* Right-click the shortcut
* Select '''Properties'''
* Set '''Start in:''' to <code>Drive:\your-path\indra\newview</code>

=== Running from within the IDE ===
* In the Solution Explorer pane right click on '''secondlife-bin'''
** Click '''Set as StartUp Project'''
** Pick '''Properties''' > '''Configuration Properties''' > '''Debugging'''
*** Set '''Command''' to <code>Drive:\your-path\build-vc100\newview\Release\secondlife-bin.exe</code> (adjust <code>Release</code> to the type of build you are doing, e.g. <code>RelWithDebInfo</code>)
*** Set '''Working Directory''' to <code>..\..\indra\newview</code>

== Handling Problems ==

If you encounter errors or run into problems following the instructions above, please first check whether someone else already had the same issue. A solution might be known already. See the [[#Common_Issues.2FBugs.2FGlitches_And_Solutions|issue list below]], check [[{{TALKPAGENAME}}|the talk page]] (and report useful experiences there) and search our [[issue tracker]]. Even when no description of your problem has been written down yet, someone might know about it, so get in touch with the community to [[#Getting_help|get help]].

=== Getting help ===
* Subscribe to [[OpenSource-Dev|OpenSource-Dev Mailing List]] ([https://lists.secondlife.com/cgi-bin/mailman/listinfo/opensource-dev subscribe]) and post your question there.
* For faster response, join the general open source viewer discussion and development [[IRC]] channel [irc://irc.freenode.org/opensl #opensl on freenode]. Hopefully a helpful person is online when you ask your question.

=== Common Issues/Bugs/Glitches And Solutions ===

==== Not being able to find objidl.h in the Microsoft Windows SDK, when compiling llwindow ====
https://lists.secondlife.com/pipermail/opensource-dev/2011-April/006562.html
* Can be caused by path problems or some installation conflicts with the DirectX SDK.

==== stdint.h typedef conflicts between Quicktime and VS2010 ====
https://lists.secondlife.com/pipermail/opensource-dev/2011-April/006565.html
*: Can be solved by some small edits to header files to make sure the two don't bash on each other.

==== Eliminate deprecated switches, messages, and use memory more efficiently ====

The VS2010 compiler uses a lot of memory while compiling the viewer. If you run out of memory you will start to page heavily and your compile time will become much longer. The /Zm1000 switch affects compiler memory usage.

You may see this message while compiling:
use 'EHsc' instead of 'GX'

Here is how to free up some memory the compiler allocates and to eliminate these messages:

*Edit <code>\CMake 2.8\share\cmake-2.8\Modules\Platform\Windows-cl.cmake</code>

*Replace line 156 with:
IF(MSVC10)
SET(CMAKE_CXX_FLAGS_INIT "/DWIN32 /D_WINDOWS /W3 /EHsc /GR")
ELSEIF(NOT MSVC10)
SET(CMAKE_CXX_FLAGS_INIT "/DWIN32 /D_WINDOWS /W3 /Zm1000 /EHsc /GR")
ENDIF(MSVC10)

*Replace line 172 with:
IF(MSVC10)
SET(CMAKE_CXX_FLAGS_INIT "/DWIN32 /D_WINDOWS /W3 /EHsc /GR")
ELSEIF(NOT MSVC10)
SET(CMAKE_CXX_FLAGS_INIT "/DWIN32 /D_WINDOWS /W3 /Zm1000 /GX /GR")
ENDIF(MSVC10)

*Replace line 184 with:
IF(MSVC10)
SET(CMAKE_CXX_FLAGS_INIT "/DWIN32 /D_WINDOWS /W3 /EHsc /GR")
ELSEIF(NOT MSVC10)
SET(CMAKE_CXX_FLAGS_INIT "/DWIN32 /D_WINDOWS /W3 /Zm1000 /GX /GR")
ENDIF(MSVC10)

== References ==

Tip of the hat to Nicky_Perian for [[User:Nicky_Perian/Visual_Studio_10_Autobuild]]

[[Category:Compiling viewer]]

Template:LSL Constants/llCreateCharacter

2012-05-01T23:45:29Z

Ima Mechanique:

<noinclude>{{Pathfinding alpha}}</noinclude>
{| {{Prettytable}}
|-{{Hl2}}
!Option
!Value
!Default
!Description
|-
|CHARACTER_DESIRED_SPEED
|1
|6
|Speed of pursuit in meters per second.
|-
|CHARACTER_RADIUS
|2
|
|Set collision capsule radius.
|-
|CHARACTER_LENGTH
|3
|
|Set collision capsule length - cannot be less than twice the radius plus 0.1m.
|-
|CHARACTER_ORIENTATION
|4
|VERTICAL
|Valid options are: VERTICAL, HORIZONTAL.
|-
|TRAVERSAL_TYPE
|7
|TRAVERSAL_TYPE_SLOW
|Valid options are: TRAVERSAL_TYPE_FAST, TRAVERSAL_TYPE_SLOW, and TRAVERSAL_TYPE_NONE. Controls the speed at which characters move on <100% walkable surfaces. To use _FAST or _SLOW, you must specify a CHARACTER_TYPE.
|-
|CHARACTER_TYPE
|6
|CHARACTER_TYPE_NONE
|Specifies which walkability coefficient will be used by this character. Options are CHARACTER_TYPE_A, CHARACTER_TYPE_B, CHARACTER_TYPE_C, CHARACTER_TYPE_D, and CHARACTER_TYPE_NONE
|-
|CHARACTER_AVOIDANCE_MODE
|5
|AVOID_CHARACTERS <nowiki>|</nowiki> AVOID_DYNAMIC_OBSTACLES
|Allows you to specify that a character should not try to avoid other characters, should not try to avoid dynamic obstacles (relatively fast moving objects and avatars), or both. This is framed in the positive sense ([CHARACTER_AVOIDANCE_MODE, AVOID_CHARACTERS] would create a character that avoided other characters but not agents or moving vehicles).
|-
|CHARACTER_MAX_ACCEL
|8
|20
|The character's maximum acceleration rate.
|-
|CHARACTER_MAX_DECEL
|9
|30
|The character's maximum deceleration rate.
|-
|CHARACTER_MAX_TURN_SPEED
|12
|6
|The character's maximum speed while turning--note that this is only loosely enforced (i.e., a character may turn at higher speeds under certain conditions)
|-
|CHARACTER_MAX_TURN_RADIUS
|10
|1.25
|The character's turn radius when traveling at CHARACTER_MAX_TURN_SPEED
|-
|CHARACTER_MAX_SPEED
|13
|20
|The character's maximum speed. Affects speed when avoiding dynamic obstacles and when traversing low-walkability objects in TRAVERSAL_TYPE_FAST mode.
|}

AGENT LIST PARCEL

2012-04-21T06:44:28Z

Ima Mechanique:

<onlyinclude>{{#if:

{{{{LSL Const|AGENT_LIST_PARCEL|integer||c=}}}}

}}</onlyinclude>{{#if:

{{:AGENT_LIST_PARCEL}}

}}{{LSL Constant
|name=AGENT_LIST_PARCEL
|type=integer
|value=1
|desc=Agents on the same parcel where the script is running.
|examples=
|constants=
|functions=
{{LSL DefineRow||[[llGetAgentList]]|}}
|events
|location
|cat1=Agent
|cat2=Parcel
|cat3
|cat4
}}

AGENT LIST PARCEL OWNER

2012-04-21T06:43:58Z

Ima Mechanique:

<onlyinclude>{{#if:

{{{{LSL Const|AGENT_LIST_PARCEL_OWNER|integer||c=}}}}

}}</onlyinclude>{{#if:

{{:AGENT_LIST_PARCEL_OWNER}}

}}{{LSL Constant
|name=AGENT_LIST_PARCEL_OWNER
|type=integer
|value=2
|desc=Agents on any parcel in the region where the parcel owner is the same as the owner of the parcel under the scripted object.
|examples=
|constants=
|functions=
{{LSL DefineRow||[[llGetAgentList]]|}}
|events
|location
|cat1=Agent
|cat2=Parcel
|cat3
|cat4
}}

AGENT LIST REGION

2012-04-21T06:43:13Z

Ima Mechanique:

<onlyinclude>{{#if:

{{{{LSL Const|AGENT_LIST_REGION|integer||c=}}}}

}}</onlyinclude>{{#if:

{{:AGENT_LIST_REGION}}

}}{{LSL Constant
|name=AGENT_LIST_REGION
|type=integer
|value=4
|desc=Agents on any parcel in the region where the parcel owner is the same as the owner of the parcel under the scripted object.
|examples=
|constants=
|functions=
{{LSL DefineRow||[[llGetAgentList]]|}}
|events
|location
|cat1=Agent
|cat2=Parcel
|cat3
|cat4
}}

AGENT LIST PARCEL

2012-04-21T06:40:39Z

Ima Mechanique:

<onlyinclude>{{#if:

{{#vardefine:slice_const|{{LSL Const|AGENT_LIST_PARCEL|integer||c=}}}}

}}</onlyinclude>{{#if:

{{:PRIM_TYPE}}

}}{{LSL Constant
|name=AGENT_LIST_PARCEL
|type=integer
|value=1
|desc=Agents on the same parcel where the script is running.
|examples=
|constants=
|functions=
{{LSL DefineRow||[[llGetAgentList]]|}}
|events
|location
|cat1=Agent
|cat2=Parcel
|cat3
|cat4
}}

AGENT LIST PARCEL OWNER

2012-04-21T06:39:26Z

Ima Mechanique:

<onlyinclude>{{#if:

{{#vardefine:slice_const|{{LSL Const|AGENT_LIST_PARCEL_OWNER|integer||c=}}}}

}}</onlyinclude>{{#if:

{{:PRIM_TYPE}}

}}{{LSL Constant
|name=AGENT_LIST_PARCEL_OWNER
|type=integer
|value=2
|desc=Agents on any parcel in the region where the parcel owner is the same as the owner of the parcel under the scripted object.
|examples=
|constants=
|functions=
{{LSL DefineRow||[[llGetAgentList]]|}}
|events
|location
|cat1=Agent
|cat2=Parcel
|cat3
|cat4
}}

AGENT LIST PARCEL OWNER

2012-04-21T06:26:38Z

Ima Mechanique: Created page with "AGENT_LIST_PARCEL_OWNER"

AGENT_LIST_PARCEL_OWNER

AGENT LIST PARCEL

2012-04-21T06:26:27Z

Ima Mechanique: Created page with "AGENT_LIST_PARCEL"

AGENT_LIST_PARCEL

LlGetAgentList

2012-04-21T06:26:10Z

Ima Mechanique:

{{LSL_Function
|inject-2={{Issues/SVC-5488}}{{Issues/MISC-243}}{{LSL_Function/avatar|avatar|sim=*}}
|func=llGetAgentList
|sort=GetAgentList
|func_id
|func_sleep=0
|func_energy=0
|func_desc=Requests a list of agents currently in the region, limited by the scope parameter.
|func_footnote=
|return_type=list
|return_text=[key id0, key id1, ..., key idn] or [string error_msg] - returns avatar keys for all agents in the region limited to the area(s) specified by scope
|spec=
|p1_type=integer|p1_name=scope|p1_desc=selection scope
* [[AGENT_LIST_PARCEL]] - returns only agents on the same parcel where the script is running.
* [[AGENT_LIST_PARCEL_OWNER]] - returns only agents on any parcel in the region where the parcel owner is the same as the owner of the parcel under the scripted object.
* [[AGENT_LIST_REGION]] - returns any/all agents in the region.
|p2_type=list|p2_name=options|p2_desc=Unused.
|p2_hover=selection flags
|constants=
|caveats=
* There is no guaranteed understandable order or randomness to the list returned.
* Will only return up to 100 agents.
|examples=<lsl>//Displays up to 100 avatar key: name pairs detected in the entire region
list gaAgents;

default
{
touch_start(integer total_number)
{
integer i;
integer liCount;

gaAgents = llGetAgentList(AGENT_LIST_REGION, []);
liCount = llGetListLength(gaAgents);
if (liCount > 0)
if (llGetListEntryType(gaAgents,0) == TYPE_STRING)
llOwnerSay("Error: "+llList2String(gaAgents,0));
else
for (i=0; i < liCount; ++i)
llOwnerSay(llList2String(gaAgents,i)+": "+llKey2Name(llList2String(gaAgents,i)));
}
}</lsl>
|helpers
|also_header
|also_functions=*[[llGetRegionAgentCount]]
|also_tests
|also_events
|also_articles
|also_footer
|notes=
|mode=pre-release
|deprecated
|location
|history=
* New function proposed by LL, reconciling the feature suggestions {{Jira|SVC-805}}, {{Jira|SVC-6427}}, {{Jira|MISC-243}} and {{Jira|SVC-5488}}.
* Pre-Released [[Release_Notes/Second_Life_RC_Magnum/12]]
|cat1=Functions
|cat2=Avatar
|cat3=Owner
|cat4=Parcel
|cat5=Region
|cat6
}}

AGENT LIST REGION

2012-04-21T06:16:54Z

Ima Mechanique: Created page with "AGENT_LIST_REGION"

AGENT_LIST_REGION

PRIM SLICE

2012-04-21T06:04:06Z

Ima Mechanique:

<onlyinclude>{{#if:

{{#vardefine:slice_const|{{LSL Const|PRIM_SLICE|integer||c=Used to {{GetSet|{{{1|}}}|get|set|/}} the prim's slice (a shape attribute)}}}}

}}</onlyinclude>{{#if:

{{:PRIM_TYPE}}

}}{{LSL Constant
|name=PRIM_SLICE
|type=integer
|value=35
|desc=Used to get or set the prim's name.
|pa={{LSL Constant/List|i_front=[[llSetPrimitiveParams]]([ {{#var:slice_const}}, |i_end= ]);
|text={{LSL Constant/PrimParamText|set}}
|i1_type=vector|i1_disp=slice|i1_name=cut
|toc=llSetPrimitiveParams
}}
|pb={{LSL Constant/List|i_front=[[llGetPrimitiveParams]]([ {{#var:slice_const}}|i_end= ]);|
|r_front=Returns the list [ |r_end= ]
|text={{LSL Constant/PrimParamText|get}}
|r1_type=vector|r1_disp=slice|r1_name=cut
|toc=llGetPrimitiveParams
}}
|examples=
|constants=
|functions=
{{LSL DefineRow||[[llSetPrimitiveParams]]|}}
{{LSL DefineRow||[[llSetLinkPrimitiveParams]]|}}
{{LSL DefineRow||[[llSetLinkPrimitiveParamsFast]]|}}
{{LSL DefineRow||[[llGetPrimitiveParams]]|}}
{{LSL DefineRow||[[llGetLinkPrimitiveParams]]|}}
|events
|location
|cat1=Prim
|cat2=PrimitiveParams
|cat3
|cat4
}}

Talk:PRIM PHYSICS MATERIAL

2012-03-13T16:10:02Z

Ima Mechanique: /* Categorization */

== Categorization ==

I expected to see this page under the Physics category, more so given that [[llSetPhysicsMaterial]] and [[llGetPhysicsMaterial]] are in it. The Physics/Material category sounds a bit over the top to me, at least while there are no other functions; it's a bit like creating an LSL Name category and put there llSetObjectName, llGetObjectName and PRIM_NAME. Is it acceptable to just use [[:Category:LSL Physics]] instead of [[:Category:LSL Physics/Material]]? --[[User:Pedro Oval|Pedro Oval]] 22:34, 23 January 2012 (PST)

:[[:Category:LSL Physics/Material]] (as it hasn't been created yet) is just an idea for a category, it can be changed to Physics instead. The reasoning behind having it in a subcategory is so that the ''material_bits'' flags don't flood the category. I forgot about this when I was putting together the function articles so I put them in physics/materials. Do you still think they should be in Physics? On this topic, does llGetPrimitiveParams return a materials_bit for PRIM_PHYSICS_MATERIAL? I wasn't sure when writing this article and the release notes make no mention of it. -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 21:19, 24 January 2012 (PST)

::I think the constants fit nicely in the Physics category. As for llGPP, no idea, as PRIM_PHYSICS_MATERIAL does not work for me at the time of this writing. My guess is that it won't be returned. I don't know if it will be required as part of the request, kind of like e.g. <nowiki>[PRIM_TEXTURE, face_num]</nowiki> works, to specify what data to return. --[[User:Pedro Oval|Pedro Oval]] 11:19, 26 January 2012 (PST)

== Invalid constant ==
This constant doesn't actually exist in LSL. It was removed from beta code before release to agni, as it isn't needed for the function llSetPhysicsMaterial().

Server Beta User Group

2012-02-23T23:14:46Z

Ima Mechanique: /* Any Other Items */

This is the meeting tracking and progress page for the weekly Server BETA QA Meeting, moderated by Oskar Linden. Please contact him on AGNI for more information. You can join the '''Second Life Beta''' group for updates.

'''The next meeting is Thursday, February 23rd 2012, 3PM PDT at {{SLurl|region=Morris|x=210|y=250|z=35|title=Morris}} on the preview grid, [[Preview_Grid | ADITI]].'''

* Join the email list - sign up here: https://lists.secondlife.com/cgi-bin/mailman/listinfo/server-beta

== Agenda ==

=== Updates ===

* '''Second Life Server Channel'''
This is the same code as last week.

* '''BlueSteel RC Channel'''
* This channel has some voice code changes to help with region crossings.
** Properly merged with trunk.
** https://wiki.secondlife.com/wiki/Release_Notes/Second_Life_RC_BlueSteel/12#12.02.15.249527

* '''LeTigre RC Channel'''
* This code is identical to the code on BlueSteel
** Properly merged with trunk.
** https://wiki.secondlife.com/wiki/Release_Notes/Second_Life_RC_LeTigre/12#12.02.15.249527

* '''Magnum RC Channel'''
* This is the threaded region crossing code.
* Now with LESS ghosting!
** Properly merged with trunk.
** https://wiki.secondlife.com/wiki/Release_Notes/Second_Life_RC_Magnum/12#12.02.21.249728

* '''Pathfinding Alpha Q&A'''
** Who has looked into this?
** https://wiki.secondlife.com/wiki/Pathfinding_in_Second_Life
** http://community.secondlife.com/t5/Featured-News/Take-a-Sneak-Peek-at-the-Pathfinding-Experiments-Being-Conducted/ba-p/1386511

* '''Received Items Beta Test'''
** Introducing Gecko!
** Forums: http://community.secondlife.com/t5/Merchants/Try-out-the-new-Received-Items-Beta/td-p/1397409
** Blog: http://community.secondlife.com/t5/Inworld/Received-Items-Beta-Launch/ba-p/1397377
** How you can help: https://wiki.secondlife.com/wiki/ReceivedItemsBetaTesting

=== Upcoming Stuff ===

=== Interesting Stuff ===

=== Any Other Items ===
SVC-6 Agni code now breaks llDeleteSubstring()

== Open Items ==
* {{jira|SVC-4632}} - People getting past Estate and Land bans | Critical & 325 (402 as of 8/11/10) votes!
** Dante has commented on this issue and reopened it.
* {{jira|SVC-5925}} - Erratic behavior on script rezzed prims set physical
* {{jira|SVC-3044}} - [[DEBUG_CHANNEL|Debug channel]] and script error reporting needs a major rethink
** related to {{jira|vwr-199}} and {{jira|vwr-7062}}
** [15:17] Roberto Salubrius: can we get that standarized pleaaaaaaaaaaaseeeeeeeeee so we can listen to the debug channel whenever there's a problem PLEAAAAAAAAAASEEEEEEE
** [15:17] Roberto Salubrius: preeeeeeeetty pleaaseeeeee
* {{jira|svc-4196}} - "Avatar entering sim or rezzing object causes sim to freeze for up to 30 seconds - everything stops for everybody there"
* wassup with {{jira|SVC-3895}}
* status on {{jira|SVC-3618}} - estate managers unable to freeze / eject
* status on {{jira|SVC-1253}} - users sitting on prims, which are set to phantom are not affected by damage. | 108 votes!
* status on {{jira|SVC-5404}} - Vehicles can no longer enter a region if no-object-entry flag is set
* What is going on with {{jira|SVC-421}} - Cannot delete contents from no-modify objects
* status on {{jira|SVC-5880}} - Vehicles "Jumping" when crossing prims
* {{jira|SVC-5922}} -Physics unset on vehicles when seated avatars goes beyond the physical 'prim' limit where agents are counted towards prims
* {{jira|SVC-6104}} script sim crossing bug
* {{jira|SVC-6123}} cant catch sphere type exact shape with lsl functions
* What is the story on the bug that allows the Meeroos food vending scam? Nalates U
* At what point do you want me document functions that appear here or in the RC release notes? (I won't be attending the meeting but I'll review the transcript) -- '''[[User:Strife_Onizuka|Strife]]''' ([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]]) 12:29, 11 January 2012 (PST)

= Minutes from Previous Meetings =
*2012
** February
*** [[Beta_Server_Office_Hours/Minutes/2012-02-16 | 2012-02-16]]
*** [[Beta_Server_Office_Hours/Minutes/2012-02-09 | 2012-02-09]]
*** [[Beta_Server_Office_Hours/Minutes/2012-02-02 | 2012-02-02]]
** January
*** [[Beta_Server_Office_Hours/Minutes/2012-01-26 | 2012-01-26]]
*** [[Beta_Server_Office_Hours/Minutes/2012-01-19 | 2012-01-19]]
*** [[Beta_Server_Office_Hours/Minutes/2012-01-12 | 2012-01-12]]
*** [[Beta_Server_Office_Hours/Minutes/2012-01-05 | 2012-01-05]]
*2011
** December
*** [[Beta_Server_Office_Hours/Minutes/2011-12-15 | 2011-12-15]]
*** [[Beta_Server_Office_Hours/Minutes/2011-12-08 | 2011-12-08]]
*** [[Beta_Server_Office_Hours/Minutes/2011-12-01 | 2011-12-01]]
** November
*** 2010-11-24 *NO MEETING* Happy Thanksgiving!
*** [[Beta_Server_Office_Hours/Minutes/2011-11-17 | 2011-11-17]]
*** [[Beta_Server_Office_Hours/Minutes/2011-11-10 | 2011-11-10]]
*** [[Beta_Server_Office_Hours/Minutes/2011-11-03 | 2011-11-03]]
** October
*** [[Beta_Server_Office_Hours/Minutes/2011-10-27 | 2011-10-27]]
*** [[Beta_Server_Office_Hours/Minutes/2011-10-20 | 2011-10-20]]
*** [[Beta_Server_Office_Hours/Minutes/2011-10-13 | 2011-10-13]]
*** [[Beta_Server_Office_Hours/Minutes/2011-10-06 | 2011-10-06]]
** September
*** [[Beta_Server_Office_Hours/Minutes/2011-09-29 | 2011-09-29]]
*** [[Beta_Server_Office_Hours/Minutes/2011-09-22 | 2011-09-22]]
*** [[Beta_Server_Office_Hours/Minutes/2011-09-15 | 2011-09-15]]
*** [[Beta_Server_Office_Hours/Minutes/2011-09-08 | 2011-09-08]]
*** [[Beta_Server_Office_Hours/Minutes/2011-09-01 | 2011-09-01]]
** August
*** [[Beta_Server_Office_Hours/Minutes/2011-08-25 | 2011-08-25]]
*** 2011-08-18 *No meeting. Oskar was on vacation*
*** [[Beta_Server_Office_Hours/Minutes/2011-08-11 | 2011-08-11]]
*** [[Beta_Server_Office_Hours/Minutes/2011-08-04 | 2011-08-04]]
** July
*** [[Beta_Server_Office_Hours/Minutes/2011-07-28 | 2011-07-28]]
*** [[Beta_Server_Office_Hours/Minutes/2011-07-21 | 2011-07-21]]
*** [[Beta_Server_Office_Hours/Minutes/2011-07-14 | 2011-07-14]]
*** [[Beta_Server_Office_Hours/Minutes/2011-07-07 | 2011-07-07]]
** June
*** [[Beta_Server_Office_Hours/Minutes/2011-06-30 | 2011-06-30]]
*** [[Beta_Server_Office_Hours/Minutes/2011-06-23 | 2011-06-23]]
*** [[Beta_Server_Office_Hours/Minutes/2011-06-16 | 2011-06-16]]
*** [[Beta_Server_Office_Hours/Minutes/2011-06-09 | 2011-06-09]]
*** [[Beta_Server_Office_Hours/Minutes/2011-06-02 | 2011-06-02]]
** May
*** [[Beta_Server_Office_Hours/Minutes/2011-05-26 | 2011-05-26]]
*** [[Beta_Server_Office_Hours/Minutes/2011-05-19 | 2011-05-19]]
*** [[Beta_Server_Office_Hours/Minutes/2011-05-12 | 2011-05-12]]
*** [[Beta_Server_Office_Hours/Minutes/2011-05-05 | 2011-05-05]]
** April
*** [[Beta_Server_Office_Hours/Minutes/2011-04-28 | 2011-04-28]]
*** [[Beta_Server_Office_Hours/Minutes/2011-04-21 | 2011-04-21]]
*** [[Beta_Server_Office_Hours/Minutes/2011-04-14 | 2011-04-14]]
*** [[Beta_Server_Office_Hours/Minutes/2011-04-07 | 2011-04-07]]
** March
*** [[Beta_Server_Office_Hours/Minutes/2011-03-31 | 2011-03-31]]
*** [[Beta_Server_Office_Hours/Minutes/2011-03-24 | 2011-03-24]]
*** [[Beta_Server_Office_Hours/Minutes/2011-03-17 | 2011-03-17]]
*** [[Beta_Server_Office_Hours/Minutes/2011-03-10 | 2011-03-10]]
*** [[Beta_Server_Office_Hours/Minutes/2011-03-03 | 2011-03-03]]
** February
*** [[Beta_Server_Office_Hours/Minutes/2011-02-24 | 2011-02-24]]
*** [[Beta_Server_Office_Hours/Minutes/2011-02-17 | 2011-02-17]]
*** [[Beta_Server_Office_Hours/Minutes/2011-02-10 | 2011-02-10]]
*** [[Beta_Server_Office_Hours/Minutes/2011-02-03 | 2011-02-03]]
** January
*** [[Beta_Server_Office_Hours/Minutes/2011-01-27 | 2011-01-27]]
*** [[Beta_Server_Office_Hours/Minutes/2011-01-20 | 2011-01-20]]
*** [[Beta_Server_Office_Hours/Minutes/2011-01-13 | 2011-01-13]]
*** [[Beta_Server_Office_Hours/Minutes/2011-01-06 | 2011-01-06]]
* 2010
** December
*** 2010-12-30 *NO MEETING*
*** 2010-12-23 *NO MEETING*
*** [[Beta_Server_Office_Hours/Minutes/2010-12-16 | 2010-12-16]]
*** [[Beta_Server_Office_Hours/Minutes/2010-12-09 | 2010-12-09]]
*** [[Beta_Server_Office_Hours/Minutes/2010-12-02 | 2010-12-02]]
** November
*** 2010-11-25 *NO MEETING* Happy Thanksgiving!
*** [[Beta_Server_Office_Hours/Minutes/2010-11-18 | 2010-11-18]]
*** [[Beta_Server_Office_Hours/Minutes/2010-11-11 | 2010-11-11]]
*** [[Beta_Server_Office_Hours/Minutes/2010-11-04 | 2010-11-04]]
** October
*** [[Beta_Server_Office_Hours/Minutes/2010-10-28 | 2010-10-28]]
*** [[Beta_Server_Office_Hours/Minutes/2010-10-21 | 2010-10-21]]
*** [[Beta_Server_Office_Hours/Minutes/2010-10-14 | 2010-10-14]]
*** [[Beta_Server_Office_Hours/Minutes/2010-10-07 | 2010-10-07]]
** September
*** [[Beta_Server_Office_Hours/Minutes/2010-09-30 | 2010-09-30]]
*** [[Beta_Server_Office_Hours/Minutes/2010-09-23 | 2010-09-23]]
*** [[Beta_Server_Office_Hours/Minutes/2010-09-16 | 2010-09-16]]
*** [[Beta_Server_Office_Hours/Minutes/2010-09-09 | 2010-09-09]]
*** [[Beta_Server_Office_Hours/Minutes/2010-09-02 | 2010-09-02]]
** August
*** [[Beta_Server_Office_Hours/Minutes/2010-08-26 | 2010-08-26]]
*** [[Beta_Server_Office_Hours/Minutes/2010-08-19 | 2010-08-19]]
*** [[Beta_Server_Office_Hours/Minutes/2010-08-12 | 2010-08-12]]
*** [[Beta_Server_Office_Hours/Minutes/2010-08-05 | 2010-08-05]]
** July
*** [[Beta_Server_Office_Hours/Minutes/2010-07-29 | 2010-07-29]]
*** [[Beta_Server_Office_Hours/Minutes/2010-07-22 | 2010-07-22]]
*** [[Beta_Server_Office_Hours/Minutes/2010-07-15 | 2010-07-15]]
*** [[Beta_Server_Office_Hours/Minutes/2010-07-08 | 2010-07-08]]
*** [[Beta_Server_Office_Hours/Minutes/2010-07-01 | 2010-07-01]]
** June
*** [[Beta_Server_Office_Hours/Minutes/2010-06-24 | 2010-06-24]]
*** [[Beta_Server_Office_Hours/Minutes/2010-06-10 | 2010-06-10]]
*** [[Beta_Server_Office_Hours/Minutes/2010-06-03 | 2010-06-03]]
** May
*** [[Beta_Server_Office_Hours/Minutes/2010-05-27 | 2010-05-27]]
*** [[Beta_Server_Office_Hours/Minutes/2010-05-20 | 2010-05-20]]
*** [[Beta_Server_Office_Hours/Minutes/2010-05-13 | 2010-05-13]]
*** [[Beta_Server_Office_Hours/Minutes/2010-05-06 | 2010-05-06]]
** April
*** [[Beta_Server_Office_Hours/Minutes/2010-04-29 | 2010-04-29]]
*** [[Beta_Server_Office_Hours/Minutes/2010-04-22 | 2010-04-22]]
*** [[Beta_Server_Office_Hours/Minutes/2010-04-15 | 2010-04-15]]
*** [[Beta_Server_Office_Hours/Minutes/2010-04-08 | 2010-04-08]]
*** [[Beta_Server_Office_Hours/Minutes/2010-04-01 | 2010-04-01]]
** March
*** [[Beta_Server_Office_Hours/Minutes/2010-03-25 | 2010-03-25]]
*** [[Beta_Server_Office_Hours/Minutes/2010-03-18 | 2010-03-18]]
*** [[Beta_Server_Office_Hours/Minutes/2010-03-11 | 2010-03-11]]
*** [[Beta_Server_Office_Hours/Minutes/2010-03-04 | 2010-03-04]]
** February
*** [[Beta_Server_Office_Hours/Minutes/2010-02-25 | 2010-02-25]]
*** [[Beta_Server_Office_Hours/Minutes/2010-02-18 | 2010-02-18]]
*** [[Beta_Server_Office_Hours/Minutes/2010-02-11 | 2010-02-11]]
*** [[Beta_Server_Office_Hours/Minutes/2010-02-04 | 2010-02-04]]
** January
*** [[Beta_Server_Office_Hours/Minutes/2010-01-21 | 2010-01-21]]
*** [[Beta_Server_Office_Hours/Minutes/2010-01-14 | 2010-01-14]]
*** [[Beta_Server_Office_Hours/Minutes/2010-01-07 | 2010-01-07]]
* 2009
** December
*** [[Beta_Server_Office_Hours/Minutes/2009-12-17 | 2009-12-17]]
*** [[Beta_Server_Office_Hours/Minutes/2009-12-10 | 2009-12-10]]
*** [[Beta_Server_Office_Hours/Minutes/2009-12-04 | 2009-12-04]]
** November
*** [[Beta_Server_Office_Hours/Minutes/2009-11-26 | 2009-11-26]]
*** [[Beta_Server_Office_Hours/Minutes/2009-11-19 | 2009-11-19]]
*** [[Beta_Server_Office_Hours/Minutes/2009-11-12 | 2009-11-12]]
*** [[Beta_Server_Office_Hours/Minutes/2009-11-05 | 2009-11-05]]
** October
*** [[Beta_Server_Office_Hours/Minutes/2009-10-29 | 2009-10-29]]
*** [[Beta_Server_Office_Hours/Minutes/2009-10-22 | 2009-10-22]]
*** [[Beta_Server_Office_Hours/Minutes/2009-10-15 | 2009-10-15]]
*** [[Beta_Server_Office_Hours/Minutes/2009-10-08 | 2009-10-08]]
*** [[Beta_Server_Office_Hours/Minutes/2009-10-01 | 2009-10-01]]

[[Category:Bug Tracker]]
[[Category:Quality Assurance]]
[[Category:QA_Portal]]
[[Category:User Groups]]

Pathfinding in Second Life

2012-02-17T22:58:58Z

Ima Mechanique:

{{Pathfinding alpha}}
__TOC__

== Pathfinding alpha information ==
* [[Pathfinding alpha]] - Information and tips on how to test the alpha version of Pathfinding on the Aditi test grid.
* [[Preview_Grid#How_do_I_log_in_to_Aditi.3F|How do I log into the Aditi test grid?]] - This test is being run on the Aditi test grid; for more information, read this article about Aditi and how you can log in.

==Pathfinding API documentation==

* [[Overview of pathfinding]] - Introduction and overview of pathfinding.
* [[Pathfinding tutorial]] - Short "walkthrough" of setting up and using pathfinding. TBD.
* [[Pathfinding/Alpha release notes]] - Restrictions, known issues, and so on.

=== LSL reference ===
==== Pathfinding functions ====
* [[llCreateCharacter]] - Convert the current linkset to an AI character. By default, the character's shape will be an upright capsule approximately the size of the linkset, adjustable via the options list. The linkset must use mesh accounting.
* [[llDeleteCharacter]] - Convert the current linkset back to a standard object
* [[llEvade]] - Causes the character to keep away from the object or avatar identified by the key.
* [[llExecPathingCmd]] - Send a command to the pathing system - currently only supports stopping pathing.
* [[llFleeFrom]] - Attempt to get at least 'distance' away from 'source' - provided in region-local coordinates.
* [[llGetClosestNavPoint]] - Accepts a point in region-local space and returns either an empty list or a list containing a single vector which is the closest point on the navmesh to the point provided.
* [[llNavigateTo]] - Navigate to a destination provided in region coordinates. The destination may be in another region.
* [[llPatrolPoints]] - Patrol a provided set of points provided as vectors.
* [[llPursue]] - Causes the character to chase after the object or avatar identified by the key.
* [[llUpdateCharacter]] - Update character properties.
* [[llWanderWithin]] - Wander within an area approximately 'scale' in radius centered at 'origin'. Wandering means choosing a random point in the area and navigating to it. After arrival, a new random point will be chosen and navigated to.
==== Pathfinding events ====

* [[path_update]] - Informs the script of events that happen within the pathfinding system.