Difference between revisions of "Get source and compile"

From Second Life Wiki
Jump to navigation Jump to search
m
m (Switch VCS to GitHub)
 
(90 intermediate revisions by 22 users not shown)
Line 1: Line 1:
{{multi-lang|Get source and compile|pt}}
{{OSWikiContribBox}}
{{OSWikiContribBox}}


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.
This information is for people who want to work with the source code for the viewer.


= Getting the source =
==Open Source Viewer==


== Download Source Archives (Zipfile/Tarball) ==
Viewer code is hosted by [https://github.com/secondlife GitHub] using [https://en.wikipedia.org/wiki/Git git].


Linden Lab does provide current and past downloads in an archived format, see the [[source downloads]] page.
* [https://github.com/secondlife/viewer Second Life Viewer]


== Version Control ==
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].


Linden Lab also maintains a version control repository.  There are some ''unofficial'' repositories, too.  See the [[version control repository]] page for more details.
=== Checking out Code ===


= Compiling =
To clone the current release repository:
git clone https://github.com/secondlife/viewer.git


Per platform instructions are available for the following platforms:
== Compiling ==
* [[Compiling the viewer (MSVS2003)|Microsoft Windows - Visual Studio .NET 2003]] (recommended, Linden Lab uses VS2003)
** see also: [[Compiling the viewer libraries (MSVS 2003)]]
* [[Compiling the viewer (MSVS2005)|Microsoft Windows - Visual Studio 2005 & Visual C++ 2005 Express]]
* [[Cross compiling the viewer (i686-mingw32)|Microsoft Windows - Cross compiling on Linux]]
* [[Compiling the viewer (Mac OS X)|Mac OS X]]
* [[Compiling the viewer (Linux)|Linux]]
* [[Compiling the viewer (FreeBSD)|FreeBSD]]


See [[Common compilation problems]] if you run into errors while building.
Per platform instructions are available in these topics:
* [[Build the Viewer on Windows|Windows]]
* [[Build the Viewer on macOS|macOS]]


See [[Improving compilation time]] for information on how to compile faster
=== 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]]

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.

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

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.