Difference between revisions of "Get source and compile"

Latest revision as of 13:40, 17 November 2022

This information is for people who want to work with the source code for the viewer.

Open Source Viewer

Viewer code is hosted by GitHub using git.

Second Life Viewer

Other repositories where development for future features can be seen are listed on the Release Notes Repositories page. If you have not worked with GitHub or distributed version control you may be interested in GitHub's introductory material.

Checking out Code

To clone the current release repository:

git clone https://github.com/secondlife/viewer.git

Compiling

Per platform instructions are available in these topics:

Notes

Common compilation problems

Autobuild

Autobuild is the new Linden Lab framework to maintain and build everything, from viewer to 3rd party libraries.

Instructions:

Channels and Versions

Channels are just groupings of versions. Linden Lab uses channels to track and supply updates for Project, Beta, and Release Viewers separately.

On login, the combination of channel plus version is checked against a set of rules in the Viewer Version Management service. Within each channel, some versions are allowed and some are blocked. Viewers are blocked if they are too old, are unsafe (security issues), incompatible (the protocol has been changed in some fundamental way), or are a test version and Linden Lab only wants data from the most recent. See Viewer Integration and Release Processes for an explanation of how different versions are managed by Linden Lab.

If you are building a viewer, the Policy on Third Party Viewers requires that you set your own channel name.

See:

Channel and Version Requirements: a detailed explanation and official policy on channels and versions in Second Life, and an explanation of how to set your channel name when building.

@@ Line 1: / Line 1: @@
+{{multi-lang|Get source and compile|pt}}
 {{OSWikiContribBox}}
+This information is for people who want to work with the source code for the viewer.
-Even if you don't plan to develop, just the act of downloading and compiling can uncover problems. If the version you download doesn't build on your platform, file a bug.
+==Open Source Viewer==
-== Getting the source ==
+Viewer code is hosted by [https://github.com/secondlife GitHub] using [https://en.wikipedia.org/wiki/Git git].
-Get a Subversion account from [[User:Rob Linden|Rob Linden]] and check out using the following command
+* [https://github.com/secondlife/viewer Second Life Viewer]
- svn co https://www.lindenlab.dreamhosters.com/svn/linden/release/
+Other repositories where development for future features can be seen are listed on the [https://releasenotes.secondlife.com/repositories.html Release Notes Repositories] page. If you have not worked with GitHub or distributed version control you may be interested in [https://docs.github.com/en/get-started GitHub's introductory material].
-=== Installing windows core development tools and libraries ===
+=== Checking out Code ===
-* Visual Studio .NET 2003 Professional
-* Microsoft Platform SDK
+To clone the current release repository:
-* DirectX 9.0 SDK Update (Summer 2003)
+ git clone https://github.com/secondlife/viewer.git
-* Set up the project globals:
-** Start Visual C++
+== Compiling ==
-** Go to Tools/Options/Projects/VC++ Directories
-** Make sure that the '''includes''' and '''libraries''' paths have the DirectX SDK paths first, then the Platform SDK paths, and then the Visual C++ paths.
+Per platform instructions are available in these topics:
-* Open indra/indra_complete/indra_complete.sln and build the project.
+* [[Build the Viewer on Windows|Windows]]
+* [[Build the Viewer on macOS|macOS]]
+=== Notes ===
+*  [[Common compilation problems]]
+=== Autobuild ===
+[[Autobuild]] is the new Linden Lab framework to maintain and build everything, from viewer to 3rd party libraries.
+Instructions:
+* [[Build Viewer With Autobuild]]
+* [[Build_3rd_Party_lib_with_Autobuild]]
+== Channels and Versions ==
+Channels are just groupings of versions. Linden Lab uses channels to track and supply updates for Project, Beta, and Release Viewers separately.
+On login, the combination of channel plus version is checked against a set of rules in the Viewer Version Management service. Within each channel, some versions are allowed and some are blocked. Viewers are blocked if they are too old, are unsafe (security issues),
+incompatible (the protocol has been changed in some fundamental way), or
+are a test version and Linden Lab only wants data from the most recent.  See [[Viewer Integration and Release Processes]] for an explanation of how different versions are managed by Linden Lab.
+'''If you are building a viewer, the [http://secondlife.com/corporate/tpv.php Policy on Third Party Viewers] requires that you set your own channel name.'''
+See:
+:;[[Channel and Version Requirements]]
+::a detailed explanation and official policy on channels and versions in Second Life, and an explanation of how to set your channel name when building.
+[[Category:Compiling viewer]]