Channel and Version Requirements
Revision as of 15:57, 26 September 2007 by Steve Linden (talk | contribs) (New page: == Setting a Channel and Version for an Open Source Viewer == 1. Choose a channel name * The default channel name is "Second Life Release" * Other Linden Lab channel names are "Second Life...)
Setting a Channel and Version for an Open Source Viewer
1. Choose a channel name
- The default channel name is "Second Life Release"
- Other Linden Lab channel names are "Second Life Release Candidate" and "Second Life First Look [Feature]"
- The channel name can be any ASCII string, however we suggest something along the lines of:
- "Second Life Open Source [Brand and/or Feature]"
2. Choose a version number
- The version number is in the form Major.Minor.Patch.Build
- The version number can be any four numbers
- We recommend using the Major, Minor, and Patch numbers from the most recently merged Linden Lab source code.
- We recommend using a Build number >= 100 to indicate a non Linden Lab version.
- Linden Lab uses the Subversion revision number for the build number for non Release / Release Candidate builds
3. Set the Channel and Version in the code
- Edit indra/llcommon/llversionviewer.h
- Modify LL_CHANNEL with the Channel Name
- Modify LL_VERSION_BUILD with the appropriate build number
- Update the version number in the following files:
- indra/newview/res/newViewRes.rc - "FileVersion" and "ProductVersion" in the Version section
- indra/newview/Info-SecondLife.plist - CFBundleVersion
- indra/newview/English.lproj/InfoPlist.strings - CFBundleShortVersionString
- Build the code
Packaging for Distribution
- From the indra/newview directory run viewer_manifest.py with the following arguments:
- viewer_manifest.py --login_url=http://your.login.url.com
- See http://wiki.secondlife.com/wiki/Viewer_Manifest for more information on packaging the Viewer
Updating an Open Source Viewer
- Anyone distributing an Open Source version of the Viewer is responsible for messaging updates to residents using that client.
- We recommend using your login url for directing residents to updates.