Difference between revisions of "Get source and compile"

Latest revision as of 14: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].
-== Setting up the development environment w/libraries ==
+=== Checking out Code ===
-=== Windows ===
+To clone the current release repository:
-* Visual Studio .NET 2003 Professional
+ git clone https://github.com/secondlife/viewer.git
-* Microsoft Platform SDK
-* DirectX 9.0 SDK Update (Summer 2003)
-* Set up the project globals:
-** Start Visual C++
-** 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.
-* Open indra/indra_complete/indra_complete.sln and build the project.
+== Compiling ==
-== Platform notes ==
+Per platform instructions are available in these topics:
+* [[Build the Viewer on Windows|Windows]]
+* [[Build the Viewer on macOS|macOS]]
-=== Linux ===
+=== Notes ===
-==== Ubuntu build notes ====
+*  [[Common compilation problems]]
-Ubuntu 5.10 and higher uses a newer version of libc6 with a bug fix that breaks our codebase.
+=== Autobuild ===
-If you see errors of the form:
+[[Autobuild]] is the new Linden Lab framework to maintain and build everything, from viewer to 3rd party libraries.
-<code>
-    obj_dat.c:(.text+0x857): undefined reference to `__ctype_b'
+Instructions:
-</code>
+* [[Build Viewer With Autobuild]]
-...when you try to build our codebase then you need to enable the CTYPE_WORKAROUND.  If you use 'make' or 'dmake', add the
+* [[Build_3rd_Party_lib_with_Autobuild]]
-following lines to your ~/.bashrc file:
-<code>
+== Channels and Versions ==
-    export SIMULATOR_CPPFLAGS="-DCTYPE_WORKAROUND"
-    export RPCSERVER_CPPFLAGS="-DCTYPE_WORKAROUND"
+Channels are just groupings of versions. Linden Lab uses channels to track and supply updates for Project, Beta, and Release Viewers separately.
-    export DATASERVER_CPPFLAGS="-DCTYPE_WORKAROUND"
-    export USERSERVER_CPPFLAGS="-DCTYPE_WORKAROUND"
+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),
-    export TEST_CPPFLAGS="-DCTYPE_WORKAROUND"
+incompatible (the protocol has been changed in some fundamental way), or
-</code>
+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 use 'scons', add the follow line to your ~/.bashrc file:
-<code>
+'''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.'''
-    export SERVER_CPPFLAGS="-DCTYPE_WORKAROUND"
-</code>
+See:
-Source your ~/.bashrc, or open a new terminal, and build again.
+:;[[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]]