Get source and compile

Template:Needs Translation/de Template:Needs Translation/es Template:Needs Translation/el Template:Needs Translation/fr Template:Needs Translation/he Template:Needs Translation/it Template:Needs Translation/ko Template:Needs Translation/nl Template:Needs Translation/hu Template:Needs Translation/no Template:Needs Translation/da Template:Needs Translation/sv Template:Needs Translation/tr Template:Needs Translation/pl Template:Needs Translation/ru Template:Needs Translation/th Template:Needs Translation/uk Template:Needs Translation/zh-Hans Template:Needs Translation/zh-Hant

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

Projeto Snowstorm

Este é o código mais recente Viewer. Código espectador é armazenado em um repositório Mercurial (hg) em 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]
• 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ê.

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.

Outra boa maneira de navegar o código fonte, incluindo diagramas de UML, está usando Doxygen.

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 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 Passos Para enviar uma alteração.

Compiling

Per platform instructions are available in these topics:

• Windows
• Mac OS X
• Linux

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:

• Build Viewer With Autobuild
• Build_3rd_Party_lib_with_Autobuild

Hints on running

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 list. Within each channel, some versions are allowed and some are blocked. Viewers are blocked that are unsafe (security issues), 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 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.

The Third Party Viewer Policy requires that all viewers use a unique channel name. Please see here for more information.