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}}
+{{multi-lang|Get source and compile|pt}}
 {{OSWikiContribBox}}
 This information is for people who want to work with the source code for the viewer.
-== Projeto Snowstorm ==
+==Open Source Viewer==
-Este é o código mais recente Viewer.
+Viewer code is hosted by [https://github.com/secondlife GitHub] using [https://en.wikipedia.org/wiki/Git git].
-Código espectador é armazenado em um repositório Mercurial (hg) em [https://bitbucket.org/lindenlab bitbucket], Open Source um site de repositório web. Há muitas versões lá; o que você é mais provável interessado em ser.
-* [Lançamento Visualizador https://bitbucket.org/lindenlab/viewer-release]
+* [https://github.com/secondlife/viewer Second Life Viewer]
-* [Https://bitbucket.org/lindenlab/viewer-beta Visualizador Beta]
-* [O https://bitbucket.org/lindenlab/viewer-development constrói último teste developer]
-Você pode procurar o código-fonte usando um navegador web comum, fazer o download para seu computador, ou usar Mercurial para gerenciar o processo para você.
+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].
-Uma das características interessantes do ramo Visualizador de Desenvolvimento é que você pode literalmente observar os Lindens trabalhando nas correções, de bugs e novas funcionalidades para o código diante dos seus olhos.
+=== Checking out Code ===
-Outra boa maneira de navegar o código fonte, incluindo diagramas de UML, está usando [http://dimentox.com/snowstorm/ Doxygen].
+To clone the current release repository:
+  git clone https://github.com/secondlife/viewer.git
-Não deixe de ler [[Criando um repositório de controle de versão.]]
-=== Controle de Versão ===
-Viewer de desenvolvimento usa a Mercurial (hg) sistema de controle de versão distribuído. Para clonar o repositório de desenvolvimento corrente primária, use:
-  <nowiki> hg clone http://hg.secondlife.com/viewer-development </ nowiki>
-Você é fortemente encorajado á instalar o [[Mercurial Ferramentas | Linden Lab Mercurial Tools]] também.
-Para uma descrição passo-a-passo do fluxo de trabalho de controle de origem do clone inicial (acima) para integração de sua mudança, veja [[Desenvolver Código Visualizador # Passos Para enviar uma alteração | Passos Para enviar uma alteração.]]
 == Compiling ==
 Per platform instructions are available in these topics:
-* [[Viewer 2 Microsoft Windows Builds|Windows]]
+* [[Build the Viewer on Windows|Windows]]
-* [[Compiling the viewer (Mac OS X)|Mac OS X]]
+* [[Build the Viewer on macOS|macOS]]
-* [[Compiling the viewer (Linux)|Linux]]
 === Notes ===
-*  [[Common compilation problems]] if you run into errors while building.
+*  [[Common compilation problems]]
-*  [[Improving compilation time]] for information on how to compile faster
-*  [[LLMozLib2]] for building LLMozLib2.
 === Autobuild ===
@@ Line 51: / Line 34: @@
 * [[Build_3rd_Party_lib_with_Autobuild]]
-== Hints on running ==
+== Channels and Versions ==
-=== 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]]