Difference between revisions of "Get source and compile"

Revision as of 14:16, 6 July 2017

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

Project Snowstorm

This is the latest Viewer code. Viewer code is stored in a Mercurial (hg) repository on bitbucket, an Open Source repository web site. There are many versions there; the one you are most likely interested in being

Viewer Release

Other repositories where development for future features can be seen are listed on the Viewer Source Repositories page.

Another good way to browse the source code, including UML diagrams, is using the Doxygen pages.

Be sure to read Creating a version control repository.

Version Control

Viewer development uses the Mercurial (hg) distributed version control system. To clone the current release repository, use:

hg clone http://bitbucket.org/lindenlab/viewer-release

You are strongly encouraged to install the Linden Lab Mercurial Tools as well.

For a step-by-step outline of the source control workflow from the initial clone (above) to integration of your change, see Steps To Submit a Change.

Compiling

Per platform instructions are available in these topics:

Notes

Common compilation problems if you run into errors while building.
Improving compilation time for information on how to compile faster
LLMozLib2 for building LLMozLib2.

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}}
+{{multi-lang|Get source and compile|pt}}
 {{OSWikiContribBox}}
-This information is for people who want to look at the actual source code for the viewer. 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.
-If you have time and skill, adding a feature that you've always wanted, or fixing a bug that most annoys you is welcome.  There is a process for uploading your changes and getting them accepted for a merge into a future release viewer.
 ==Project Snowstorm==
-This is the latest Viewer 2 code that LindenLab has.
+This is the latest Viewer code.
-Viewer 2 source code is stored in a Mercurial (hg) repository on [http://bitbucket.org/lindenlab bitbucket], one of the main Open Source repository web sites.  There are many versions there, with the ones you are most likely interested in being
+Viewer code is stored in a Mercurial (hg) repository on [https://bitbucket.org/lindenlab bitbucket], an  Open Source repository web site.  There are many versions there; the one you are most likely interested in being
-* [http://bitbucket.org/lindenlab/viewer-release Viewer2 Release]
+* [https://bitbucket.org/lindenlab/viewer-release Viewer Release]
-* [http://bitbucket.org/lindenlab/viewer-beta Viewer2 Beta]
-* [http://bitbucket.org/lindenlab/viewer-development The latest developer test builds]
-You can browse the source code using an ordinary web browser, download it to your machine, or use Mercurial to manage the process for you.
+Other repositories where development for future features can be seen are listed on the [[Linden Lab Official:Viewer Source Repositories|Viewer Source Repositories]] page.
-One of the interesting features of the Viewer-Development branch is that you can literally watch Lindens merging bug fixes and new features into the code before your very eyes.
-Another good way to browse the source code, including UML diagrams,  is using  [http://dimentox.com/snowstorm/ Doxygen].
+Another good way to browse the source code, including UML diagrams,  is using the [http://lecs-opensource.secondlife.com/doxygen/index.html Doxygen pages].
 Be sure to read [[Creating a version control repository]].
+=== Version Control ===
+Viewer development uses the Mercurial (hg) distributed version control system.  To clone the current release repository, use:
-=== Version Control ===
+ <nowiki>hg clone http://bitbucket.org/lindenlab/viewer-release</nowiki>
-Viewer development uses the Mercurial (hg) distributed version control system.  To clone the current primary development repository, use:
- hg clone http://hg.secondlife.com/viewer-development
+You are strongly encouraged to install the [[Mercurial Tools|Linden Lab Mercurial Tools]] as well.
 For a step-by-step outline of the source control workflow from the initial clone (above) to integration of your change, see [[Develop Viewer Code#Steps To Submit a Change|Steps To Submit a Change]].
@@ Line 34: / Line 30: @@
 Per platform instructions are available in these topics:
-* [[Microsoft Windows Builds|Microsoft Windows]]
+* [[Visual Studio 2013 Viewer Builds|Windows]]
-* [[Compiling the viewer (Mac OS X)|Mac OS X]]
+* [[Compiling the viewer (Mac OS X XCode 6.1)|Mac OS X]]
 * [[Compiling the viewer (Linux)|Linux]]
-* [[Viewer 2 Microsoft Windows Builds|Viewer 2 Microsoft Windows Builds - under construction]]
 === Notes ===
@@ Line 46: / Line 40: @@
 *  [[LLMozLib2]] for building LLMozLib2.
-== Hints on running ==
+=== Autobuild ===
+[[Autobuild]] is the new Linden Lab framework to maintain and build everything, from viewer to 3rd party libraries.
-=== Channels and Versions ===
+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.
-If you get a message while trying to start your compiled viewer that there is a required update, don't panic.  All of your work is not lost.  You (usually) don't have to apply your changes to a new source release to test your code.  That's where channels come in.
+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
-On login, the combination of channel plus version is checked against a list. Within each channel, some versions are allowed and some are blocked. Viewers are blocked that are unsafe (security issues),
+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.
-incompatible (the protocol has been changed in some fundamental way), not
-supported (so old Linden Lab can't afford to provide support resources), or
-(most relevant here) are in a test channel (Release Candidate, First
-Look) and Linden Lab only wants test data from the most recent.
-See [[Channel_and_Version_Requirements#Setting_a_Channel_and_Version_for_an_Open_Source_Viewer | Setting a Channel and Version for an Open Source Viewer]] for an explanation of how to do it in the source code.
-See [[Channel and Version Requirements]] for a detailed explanation and official policy on how Linden Lab deals with channels and versions in Second Life.
+'''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.'''
-The Third Party Viewer Policy requires that all viewers use a unique channel name.  Please see [http://secondlife.com/corporate/tpv.php here] for more information.
+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]]