diff options
author | Peter Bengtsson <mail@peterbe.com> | 2021-04-29 11:14:49 -0400 |
---|---|---|
committer | GitHub <noreply@github.com> | 2021-04-29 16:14:49 +0100 |
commit | 50c10e22a2a094f9d46edd56eb64d12f7652246f (patch) | |
tree | bd5e7be4288b36a314eb38039261fe973c91468c /files/pt-br/mozilla | |
parent | 7ce9d46289c8931c157dd1f676d427bee517dca2 (diff) | |
download | translated-content-50c10e22a2a094f9d46edd56eb64d12f7652246f.tar.gz translated-content-50c10e22a2a094f9d46edd56eb64d12f7652246f.tar.bz2 translated-content-50c10e22a2a094f9d46edd56eb64d12f7652246f.zip |
Remove Mozilla/Developer_guide (#691)
Diffstat (limited to 'files/pt-br/mozilla')
3 files changed, 0 insertions, 396 deletions
diff --git a/files/pt-br/mozilla/developer_guide/index.html b/files/pt-br/mozilla/developer_guide/index.html deleted file mode 100644 index 67a437715d..0000000000 --- a/files/pt-br/mozilla/developer_guide/index.html +++ /dev/null @@ -1,140 +0,0 @@ ---- -title: Guia do Desenvolvedor -slug: Mozilla/Developer_guide -translation_of: Mozilla/Developer_guide ---- -<p><span id="result_box" lang="pt"><span class="hps">Seja você</span> <span class="hps">um veterano</span> <span class="hps">ou</span> <span class="hps">apenas um iniciante,</span> <span class="hps alt-edited">os artigos que você pode</span> <span class="hps">encontrar</span> <span class="hps">a partir desta</span> <span class="hps">página</span> <span class="hps">irá ajudá-lo</span> <span class="hps">enquanto você está trabalhando</span> <span class="hps">no desenvolvimento</span> <span class="hps">da Mozilla.</span></span></p> -<h2 id="Primeira_vez"><span class="short_text" id="result_box" lang="pt"><span class="hps">Primeira vez?</span></span></h2> -<dl> - <dt> - <a href="/pt-BR/docs/Introducao" title="En/Introduction">Introdução</a></dt> - <dd> - <span id="result_box" lang="pt"><span class="hps">Um guia para</span> <span class="hps">iniciantes</span> <span class="hps">passo</span> <span class="hps">a passo</span> <span class="hps">para</span> <span class="hps">se envolver</span> <span class="hps">com a Mozilla</span><span>.</span></span></dd> -</dl> -<table class="mainpage-table"> - <tbody> - <tr> - <td> - <h2 id="Tópicos_da_documentação"><span class="short_text" id="result_box" lang="pt"><span class="hps">Tópicos da documentação</span></span></h2> - <dl> - <dt> - <a class="internal" href="/pt-BR/docs/Developer_Guide/Codigo_Fonte" title="En/Developer_Guide/Source_Code"><span class="short_text" id="result_box" lang="pt"><span class="hps">Trabalhando com o</span> <span class="hps">Código Fonte</span> <span class="hps">Mozilla</span></span></a></dt> - <dd> - <span id="result_box" lang="pt"><span class="hps">Uma visão geral</span> <span class="hps">do código,</span> <span class="hps">como</span> </span>obtê-lo<span id="result_box" lang="pt"><span>, e o</span> <span class="hps">guia de</span> <span class="hps">estilo de codificação.</span></span></dd> - <dt> - <a class="internal" href="/En/Developer_Guide/Build_Instructions" title="En/Developer_Guide/Build_Instructions"><span class="short_text" id="result_box" lang="pt"><span class="hps">Instruções</span> de <span class="hps alt-edited">Compilação</span></span></a></dt> - <dd> - <span id="result_box" lang="pt"><span class="hps alt-edited">Como compilar</span> <span class="hps">o Firefox</span><span>, Thunderbird,</span> <span class="hps">SeaMonkey,</span> <span class="hps">ou outras aplicações</span> <span class="hps">Mozilla.</span></span></dd> - <dt> - <a href="/En/Developer_Guide/Development_process_overview" title="En/Developer Guide/Development process overview"><span class="short_text" id="result_box" lang="pt"><span class="hps">Visão geral do processo</span> <span class="hps">de desenvolvimento</span></span></a></dt> - <dd> - <span id="result_box" lang="pt"><span class="hps">Uma visão geral do</span> <span class="hps">processo de desenvolvimento</span> <span class="hps">da Mozilla.</span></span></dd> - <dt> - <a href="/en/Mozilla/Multiple_Firefox_Profiles" title="en/Mozilla/Multiple_Firefox_Profiles"><span class="short_text" id="result_box" lang="pt"><span class="hps">Gerenciando</span> <span class="hps alt-edited">múltiplos perfis</span></span></a></dt> - <dd> - <span id="result_box" lang="pt"><span class="hps">Ao trabalhar com</span> <span class="hps">versões</span> <span class="hps alt-edited">de pré-lançamento do</span> <span class="hps">Firefox</span><span>, é</span> <span class="hps">sempre útil</span> <span class="hps">ter</span> <span class="hps alt-edited">múltiplos perfis</span> <span class="hps">do Firefox</span><span>, como</span> <span class="hps">um para cada canal</span><span>, ou</span> <span class="hps">para diferentes tipos de</span> <span class="hps">testes.</span></span></dd> - <dt> - <a class="internal" href="/en/Mozilla_automated_testing" title="en/Mozilla automated testing"><span class="short_text" id="result_box" lang="pt"><span class="hps">Teste Automatizado</span></span></a></dt> - <dd> - <span id="result_box" lang="pt"><span class="hps">Como executar</span> <span class="hps">testes automatizados</span> <span class="hps">da Mozilla</span><span>,</span> <span class="hps">e como escrever</span> <span class="hps">novos testes</span><span>.</span></span></dd> - <dt> - <a class="internal" href="/En/Developer_Guide/How_to_Submit_a_Patch" title="En/Getting your patch in the tree"><span class="short_text" id="result_box" lang="pt"><span class="hps">Como</span> <span class="hps">enviar um patch</span></span></a></dt> - <dd> - <span id="result_box" lang="pt"><span class="hps alt-edited">Após </span> <span class="hps alt-edited">o seu patch</span> <span class="hps alt-edited">ser escrito, você</span> <span class="hps alt-edited">precisa colocá-lo para ser </span> <span class="hps">verificado</span> <span class="hps alt-edited">na árvore de diretórios.</span> <span class="hps">Este artigo explica</span> <span class="hps">o processo de revisão</span> <span class="hps">e como obter</span> <span class="hps">o seu patch</span> <span class="hps">aprovado.</span></span></dd> - <dt> - <a href="/En/Developer_Guide/Getting_documentation_updated" title="En/Developer_Guide/Getting documentation updated"><span class="short_text" id="result_box" lang="pt"><span class="hps">Obtendo</span> <span class="hps">a documentação atualizada</span></span></a></dt> - <dd> - <span id="result_box" lang="pt"><span class="hps">Como garantir</span> <span class="hps">que a documentação seja</span> <span class="hps">mantida atualizada</span> <span class="hps alt-edited">à medida que você desenvolve</span><span>.</span></span></dd> - <dt> - <a class="internal" href="/en/Mozilla_Modules_and_Module_Ownership" title="En/Mozilla Modules and Module Ownership"><span id="result_box" lang="pt"><span class="hps">Módulos</span> <span class="hps alt-edited">da Mozilla</span> <span class="hps">e suas propriedades</span></span></a></dt> - <dd> - <span id="result_box" lang="pt"><span class="hps">Este artigo fornece informações</span> <span class="hps">sobre os módulos</span> <span class="hps">da Mozilla</span><span>,</span> <span class="hps alt-edited">qual</span> <span class="hps">o papel</span> <span class="hps alt-edited">de um proprietário</span> <span class="hps alt-edited">do módulo</span><span class="hps alt-edited">, e</span> <span class="hps">como os proprietários</span> <span class="hps">do módulo</span> <span class="hps">são selecionados.</span></span></dd> - <dt> - <a class="internal" href="/en/Code_snippets" title="en/Code_snippets"><span class="short_text" id="result_box" lang="pt"><span class="hps">Trechos de código</span></span></a></dt> - <dd> - <span id="result_box" lang="pt"><span class="hps">Exemplos de códigos</span> <span class="hps">úteis para</span> <span class="hps">uma ampla variedade de</span> <span class="hps">coisas que você</span> <span class="hps">pode precisar</span> <span class="hps">para descobrir</span> <span class="hps">como fazer</span><span>.</span></span></dd> - <dt> - <a class="internal" href="/en/Mozilla_Development_Strategies" title="En/Mozilla Development Strategies"><span class="short_text" id="result_box" lang="pt">E<span class="hps">stratégias de desenvolvimento</span></span></a> <a class="internal" href="/en/Mozilla_Development_Strategies" title="En/Mozilla Development Strategies"><span class="short_text" id="result_box" lang="pt"><span class="hps alt-edited">da Mozilla</span></span></a><a class="internal" href="/en/Mozilla_Development_Strategies" title="En/Mozilla Development Strategies"><span class="short_text" id="result_box" lang="pt"> </span></a></dt> - <dd> - <span id="result_box" lang="pt"><span class="hps">Dicas</span> <span class="hps">de como</span> <span class="hps alt-edited">tirar o máximo proveito</span> <span class="hps">do seu tempo trabalhando</span> <span class="hps">no projeto</span> <span class="hps alt-edited">da Mozilla</span><span>.</span></span></dd> - <dt> - <a class="internal" href="/En/Debugging" title="en/Debugging">Depuração</a></dt> - <dd> - <span id="result_box" lang="pt"><span class="hps">Encontre dicas</span> <span class="hps">úteis</span> <span class="hps">e guias para</span> <span class="hps">a depuração do código</span> <span class="hps">do Mozilla.</span></span></dd> - <dt> - <a href="/en/Performance" title="en/Performance"><span id="result_box" lang="pt"><span class="hps">Desempenho</span></span></a></dt> - <dd> - <span id="result_box" lang="pt"><span class="hps">Guias</span> <span class="hps">de desempenho</span> <span class="hps">e utilitários</span> <span class="hps">para ajudar você a</span> <span class="hps alt-edited">fazer o seu código ter</span> <span class="hps">um bom desempenho</span> <span class="hps">(e</span> <span class="hps alt-edited">trabalhar bem com</span> <span class="hps alt-edited">outros</span><span>).</span></span></dd> - <dt> - <a class="internal" href="/En/The_Mozilla_platform" title="En/The Mozilla platform"><span class="short_text" id="result_box" lang="pt"><span class="hps">A plataforma</span> <span class="hps">Mozilla</span></span></a></dt> - <dd> - <span id="result_box" lang="pt"><span class="hps">Informações</span> <span class="hps">sobre o funcionamento</span> <span class="hps">da plataforma</span> <span class="hps">Mozilla.</span></span></dd> - <dt> - <a href="/En/Developer_Guide/Adding_APIs_to_the_navigator_object" title="en/Developer_Guide/Adding_APIs_to_the_navigator_object"><span class="short_text" id="result_box" lang="pt"><span class="hps">Adicionando</span> <span class="hps">as APIs</span> <span class="hps">para o objeto</span> <span class="hps">navigator</span></span></a></dt> - <dt> - {{ gecko_minversion_inline("9.0") }}</dt> - <dd> - Como argumentar o objeto {{ domxref("window.navigator") }} com APIs adicionais.</dd> - <dt> - <a href="/En/Developer_Guide/Interface_Compatibility" title="En/Developer Guide/Interface Compatibility"><span class="short_text" id="result_box" lang="pt"><span class="hps">Compatibilidade</span> <span class="hps">de Interface</span></span></a></dt> - <dd> - <span id="result_box" lang="pt"><span class="hps">Diretrizes para</span> <span class="hps">modificar</span> <span class="hps">APIs</span> <span class="hps alt-edited">programáveis e</span> <span class="hps alt-edited">binárias no</span> <span class="hps">Mozilla</span><span>.</span></span></dd> - <dt> - <a href="/En/Developer_Guide/Customizing_Firefox" title="En/Developer Guide/Customizing Firefox"><span class="short_text" id="result_box" lang="pt"><span class="hps">Personalizando</span> <span class="hps">o Firefox</span></span></a></dt> - <dd> - <span id="result_box" lang="pt"><span class="hps">Informações sobre como criar</span> <span class="hps">versões personalizadas do</span> <span class="hps">Firefox.</span></span></dd> - <dt> - <a href="/en/Developer_Guide/Virtual_ARM_Linux_environment" title="Virtual ARM Linux environment">Ambiente Virtual ARM Linux</a></dt> - <dd> - <span id="result_box" lang="pt"><span class="hps">Como configurar</span> <span class="hps">um emulador</span> <span class="hps">ARM</span> <span class="hps">rodando Linux</span> <span class="hps">para testar</span> <span class="hps atn">ARM-</span><span>específico, mas não</span> <span class="hps">necessariamente</span> <span class="hps">código específico da plataforma</span><span>.</span> <span class="hps">Útil para desenvolvedores</span> <span class="hps">móveis.</span></span></dd> - </dl> - </td> - <td> - <h2 id="Ferramentas">Ferramentas</h2> - <dl> - <dt> - <a class="link-https" href="https://bugzilla.mozilla.org/" title="https://bugzilla.mozilla.org/">Bugzilla</a></dt> - <dd> - <span id="result_box" lang="pt"><span class="hps">O banco de dados</span> </span><a class="link-https" href="https://bugzilla.mozilla.org/" title="https://bugzilla.mozilla.org/">Bugzilla</a> é <span id="result_box" lang="pt"><span class="hps">usado</span> <span class="hps alt-edited">para rastrear problemas</span> <span class="hps alt-edited">nos</span> <span class="hps">projetos Mozilla.</span></span></dd> - <dt> - <a class="external" href="http://mxr.mozilla.org/" title="http://mxr.mozilla.org/">MXR</a></dt> - <dd> - <span id="result_box" lang="pt"><span class="hps">Navegar e pesquisar</span> <span class="hps">o repositório de código</span> <span class="hps">fonte</span> <span class="hps">Mozilla</span> <span class="hps">na web.</span></span></dd> - <dt> - <a class="external" href="http://bonsai.mozilla.org/cvsqueryform.cgi" title="http://bonsai.mozilla.org/cvsqueryform.cgi">Bonsai</a></dt> - <dd> - <span id="result_box" lang="pt"><span class="hps">A ferramenta</span> </span><a class="internal" href="https://developer.mozilla.org/en/Bonsai" title="En/Bonsai">Bonsai</a><span id="result_box" lang="pt"> <span class="hps">permite que você</span> <span class="hps alt-edited">descubra quem</span> <span class="hps">mudou o</span> <span class="hps">arquivo no repositório</span><span>,</span> <span class="hps">e quando</span> <span class="hps">o fizeram.</span></span></dd> - <dt> - <a class="internal" href="/en/Mercurial" title="en/Mercurial">Mercurial</a></dt> - <dd> - <span id="result_box" lang="pt"><span class="hps">O</span> <span class="hps">sistema distribuído</span> <span class="hps">de controle de versão</span> <span class="hps">utilizado para</span> <span class="hps">gerenciar o código</span><span>-fonte do</span> <span class="hps">Mozilla</span><span>.</span></span></dd> - <dt> - <a class="external" href="http://tinderbox.mozilla.org/showbuilds.cgi" title="http://tinderbox.mozilla.org/showbuilds.cgi">Tinderbox</a></dt> - <dd> - <span id="result_box" lang="pt"><span class="hps">O</span><span class="hps"> </span></span><a class="internal" href="https://developer.mozilla.org/en/Tinderbox" title="En/Tinderbox">Tinderbox</a> <span id="result_box" lang="pt"><span class="hps">mostra o estado</span> <span class="hps atn">da árvore (</span><span>Se está ou não construída </span><span class="hps">com sucesso)</span><span>.</span> <span class="hps">Verifique isso antes</span> <span class="hps">e</span> <span class="hps">depois,</span> <span class="hps">para ter certeza de</span> <span class="hps">que você está trabalhando</span> <span class="hps">com uma</span> <span class="hps">árvore de trabalho</span><span>.</span></span></dd> - <dt> - <a class="internal" href="/en/Crash_reporting" title="en/Crash reporting">Monitoramento de falhas</a></dt> - <dd> - Informações sobre <a class="link-https" href="https://crash-reports.mozilla.com/reports" title="https://crash-reports.mozilla.com/reports">Socorro</a> e <a class="external" href="http://talkback-public.mozilla.org/search/start.jsp" title="http://talkback-public.mozilla.org/search/start.jsp">Talkback</a> relato falhas no sistema.</dd> - <dt> - <a class="external" href="http://graphs.mozilla.org/" title="http://graphs.mozilla.org/">Monitoramento de desempenho</a></dt> - <dd> - <span id="result_box" lang="pt"><span class="hps">Veja</span> <span class="hps">informações de desempenho para</span> <span class="hps">projetos Mozilla.</span></span></dd> - <dt> - <a href="/en/Developer_Guide/Callgraph" title="en/Developing Mozilla/Callgraph">Callgraph</a></dt> - <dd> - <span id="result_box" lang="pt"><span class="hps">Uma ferramenta para</span> <span class="hps">ajudar a realizar</span> <span class="hps">a análise estática</span> <span class="hps">do código</span> <span class="hps">Mozilla</span><span>, gerando</span> <span class="hps">callgraphs</span> <span class="hps">automaticamente.</span></span></dd> - <dt> - <a class="external" href="http://www.mozilla.org/community/developer-forums.html" title="http://www.mozilla.org/community/developer-forums.html">Fórums de desenvolvedor</a></dt> - <dd> - <span id="result_box" lang="pt"><span class="hps">A</span> <span class="hps">lista de tópicos</span> <span class="hps">específicos</span> <span class="hps">de fóruns de discussão</span> <span class="hps">onde você pode falar</span> <span class="hps">sobre questões de desenvolvimento</span> <span class="hps">da Mozilla</span><span>.</span></span></dd> - <dt> - <a class="external" href="http://www.brianbondy.com/mozilla/cheatsheet/" title="http://www.brianbondy.com/mozilla/cheatsheet/"><span class="short_text" id="result_box" lang="pt"><span class="hps">Plataforma</span> <span class="hps">de Desenvolvimento</span> <span class="hps">Mozilla</span> <span class="hps">Cheat Sheet</span></span></a></dt> - <dd> - <span id="result_box" lang="pt"><span class="hps">Lista</span> <span class="hps">de </span></span><span id="result_box" lang="pt"><span class="hps">Brian</span> <span class="hps">Bondy</span> c<span class="hps">om </span><span class="hps">informações frequentemente</span> <span class="hps">referenciado para</span> <span class="hps">desenvolvedores da plataforma</span><span>.</span></span></dd> - </dl> - </td> - </tr> - </tbody> -</table> -<p>{{ languages( { "de": "de/Entwicklerhandbuch", "zh-cn": "Cn/Developer_Guide", "ja": "ja/Developer_Guide" } ) }}</p> diff --git a/files/pt-br/mozilla/developer_guide/mozilla_build_faq/index.html b/files/pt-br/mozilla/developer_guide/mozilla_build_faq/index.html deleted file mode 100644 index 5083040403..0000000000 --- a/files/pt-br/mozilla/developer_guide/mozilla_build_faq/index.html +++ /dev/null @@ -1,185 +0,0 @@ ---- -title: FAQ de Compilação da Mozilla -slug: Mozilla/Developer_guide/Mozilla_build_FAQ -translation_of: Mozilla/Developer_guide/Mozilla_build_FAQ ---- -<h2 id="Questões_Gerais">Questões Gerais</h2> - -<dl> - <dt id="platform"><span id="result_box" lang="pt"><span class="hps">Quais sistemas</span> <span class="hps">são suportados</span> <span class="hps">plataformas</span> <span class="alt-edited hps">de compilação</span> <span class="hps">Mozilla</span><span>?</span></span></dt> - <dd>Ver <a href="/en/Supported_build_configurations" title="en/Supported_build_configurations">Supported build configurations</a>.</dd> -</dl> - -<h2 id="Localizando_erros"><span class="short_text" id="result_box" lang="pt"><span class="hps">Localizando</span> <span class="hps">erros</span></span></h2> - -<dl> - <dt><span id="result_box" lang="pt"><span class="alt-edited hps">A Compilação</span> <span class="hps">falhou</span> <span class="hps">sem qualquer</span> <span class="hps">mensagem de erro,</span> <span class="hps">como eu posso</span> <span class="hps">encontrar o problema</span><span>?</span></span></dt> - <dd><span id="result_box" lang="pt"><span class="hps">No seu diretório</span> <span class="hps">obj</span><span>, vá para o</span> <span class="hps">diretório no qual</span> <span class="alt-edited hps">de compilação</span> <span class="hps">falhou</span> <span class="alt-edited hps">e o tipo</span></span> <code>make</code> (ou <code>gmake</code> se necessario). <span id="result_box" lang="pt"><span class="hps">Isso vai</span> <span class="hps">relançar a</span> <span class="alt-edited hps">compilação para</span> <span class="hps">este pedaço</span> <span class="alt-edited hps">de código específico</span><span>, exibindo</span> <span class="hps">mensagens de erro</span> <span class="hps">mais</span> <span class="hps">detalhadas.</span></span></dd> -</dl> - -<h2 id="Questões_específicas_do_Win32"><span class="short_text" id="result_box" lang="pt"><span class="hps">Questões específicas do</span> <span class="hps">Win32</span></span></h2> - -<div class="note"><strong>Nota:</strong> Veja <strong><a href="/En/Developer_Guide/Build_Instructions/Windows_Prerequisites" title="en/Windows_Build_Prerequisites">Windows Build Prerequisites</a> </strong><span class="short_text" id="result_box" lang="pt"><span class="hps">para obter informações adicionais</span><span>.</span></span></div> - -<dl> - <dt>configure: error: installation or configuration problem: C compiler cannot create executables.</dt> - <dd>Look at the <code>config.log</code> in the obj... directory. Try checking to make sure your PATH variable includes all the necessary directories. If you are using mozilla-build, then you need to start ming32 with one of the <code>start-msvc*.bat</code> files. If your build environment has changed, you may need to delete your config.cache file (in your mozilla or object directory) and then build again.</dd> - <dt>xpt_link.exe: cannot find msvcr80d.dll.</dt> - <dd>This occurs with option <code>--enable-optimize=-Od</code> to disable any optimizations. The xpt_link.exe tool is also created using this <code>-Od</code> option. To fix this, copy <code>obj-dir/xpcom/typelib/xpt/tools/xpt_link.exe.manifest</code> to <code>obj-dir/dist/bin</code>. There is another manifest file there, for xpt_dump.exe. Copy that as well. This error will probably appear for any compiled tool that is used during the build process when <code>-Od</code> is specified. To copy all manifest files to the <code>dist/bin</code> directory, issue: <code>find ./ -iname *.exe.manifest -print0 | xargs -0 -t -i cp {} dist/bin</code> from the <code>obj-dir</code></dd> - <dt>client.mk:121 *** This source tree appears to have Windows-style line endings.</dt> - <dd>This occurs when you are using git and do not have the proper line ending settings. The commands to set the proper line endings are: - <pre class="bz_comment_text" id="comment_text_12"><span class="quote">git config core.autocrlf false -git config core.eof lf -git ls-files -z | xargs -0 rm -git checkout .</span> -</pre> - </dd> -</dl> - -<h2 id="Mingw32-specific_questions">Mingw32-specific questions</h2> - -<ul> - <li>If the configure or build fails due to a missing w32api, add the mingw32's /include directory to the end of your INCLUDE environment variable. Mingw32 libraries or binaries should not be needed, only the headers.</li> -</ul> - -<h2 id="Unix-specific_questions">Unix-specific questions</h2> - -<dl> - <dt>How do I build on Solaris 10 x86?</dt> - <dd>See <a href="/En/Developer_Guide/Build_Instructions/Solaris_Prerequisites" title="en/Solaris_Build_Prerequisites">Solaris Build Prerequisites</a>.</dd> -</dl> - -<h2 id="Mac-specific_questions">Mac-specific questions</h2> - -<dl> - <dt> </dt> - <dt>It doesn't work</dt> - <dd>That's not a question :) For common Mac build errors and additional troubleshooting tips, see <a href="/En/Developer_Guide/Build_Instructions/Mac_OS_X_Prerequisites#Troubleshooting" title="en/Mac_OS_X_Build_Prerequisites#Troubleshooting">Troubleshooting</a> in <a href="/En/Developer_Guide/Build_Instructions/Mac_OS_X_Prerequisites" title="en/Mac_OS_X_Build_Prerequisites">Mac OS X Build Prerequisites</a>. In particular, <code>bootstrap.py</code> can diagnose and suggest fixes for most common errors (wrong Xcode version, missing build dependencies).</dd> -</dl> - -<pre class="bz_comment_text" id="comment_text_12">curl https://hg.mozilla.org/mozilla-central/raw-file/default/python/mozboot/bin/bootstrap.py > bootstrap.py && python bootstrap.py</pre> - -<dl> - <dt> </dt> - <dt>Can I build a Mozilla application as a Universal Binary?</dt> - <dd>Yes. See <a href="/en/Mac_OS_X_Universal_Binaries" title="en/Mac_OS_X_Universal_Binaries">Mac OS X Universal Binaries</a> for instructions.</dd> -</dl> - -<h2 id="Fazer_Compilar_mais_rápido"><span class="short_text" id="result_box" lang="pt"><span class="alt-edited hps">Fazer</span> <span class="alt-edited hps">Compilar</span> <span class="hps">mais rápido</span></span></h2> - -<p><a name="rebuild_from_objdir"> </a></p> - -<ul> - <li><a name="rebuild_from_objdir"><span id="result_box" lang="pt"><span class="hps">Em geral</span><span>, a mudança</span> <span class="hps">em sua</span> <span class="hps">objdir</span><span>, mude</span><span>-se</span> <span class="hps">para o diretório específico</span> <span class="hps">onde pretende</span> <span class="alt-edited hps">de compilação</span> <span class="atn hps">(</span><span>a estrutura de diretórios</span> <span class="hps">do</span> <span class="hps">objdir</span> <span class="hps">corresponde à estrutura</span> <span class="hps">dos</span> <span class="hps">diretórios</span> <span class="hps">de origem</span><span>)</span><span>,</span> <span class="alt-edited hps">e o tipo</span> <span class="hps">apenas </span></span>"make" (or "gmake" if necessary). This only works if you find a directory that contains a "Makefile" (the equivalent directory in the source tree will contain a "Makefile.in"). If you want to get even more specific than that, you can try "make <filename>.obj".</a></li> - <li><a name="rebuild_from_objdir">If you have changed code of Gecko, e.g. in content/, dom/ or layout/, you also need to build <code>make -C layout/build/</code></a></li> - <li><a name="rebuild_from_objdir">With libxul (all code in one library, which is the default for opt builds now), you need to also build <code>make -C toolkit/library/</code></a></li> - <li><a name="rebuild_from_objdir">On Mac, you will also have to build<code> make -C browser/app</code></a></li> -</ul> - -<p><a name="rebuild_from_objdir"> </a></p> - -<p>Simply set the integer value after -j to the max number of parellel processes to use. For optimal builds, this should be around the number of processor cores in your system.</p> - -<dl> - <dd><a name="rebuild_from_objdir">See also </a><a href="/en/Incremental_Build" title="en/Incremental_Build">Incremental Build</a>.</dd> - <dt> </dt> - <dt>Windows builds using make are slow, is there any way to speed them up?</dt> - <dd> - <p>Yes! You should be using <a href="/en/pymake" title="en/pymake">PyMake</a> instead. PyMake recurses in a single process reducing the number of shell invocations, which are <a class="external" href="http://benjamin.smedbergs.us/blog/2009-04-02/pymake-25-faster-than-msys-make/" title="http://benjamin.smedbergs.us/blog/2009-04-02/pymake-25-faster-than-msys-make/">particularly expensive on Windows</a>. PyMake also allows for parallel builds on Windows without deadlocks.</p> - </dd> - <dt>Do parallel (make -j) builds work for Mozilla?</dt> - <dd> - <p>Yes. See the <a class="external" href="http://www.gnu.org/software/make/manual/html_node/Parallel.html">GNU Make Parallel Execution</a> manual entry for optimal usage.</p> - On Windows you must use PyMake if doing parallel builds (see above - keep in mind this is done automatically if building with <code>mach</code>). - - <p>As of December 2012, running builds through <code>mach </code>or<code> client.mk</code> will result in the optimal values being passed to make automatically. If you would like to change the default values, add something like the following to your mozconfig file:</p> - - <pre>mk_add_options MOZ_MAKE_FLAGS=-j8 -</pre> - </dd> - <dt>I have less than 4GB RAM, is there any way I can speed up linking?</dt> - <dd> - <p>Yes, disabling debugging symbols can speed up linking considerably. Add the following to your .mozconfig:</p> - - <pre>ac_add_options --disable-debug-symbols -</pre> - </dd> - <dt>How can I turn on distcc to help compilation?</dt> - <dd> - <p>In your .mozconfig file, add:</p> - - <pre>mk_add_options MOZ_MAKE_FLAGS="CC='distcc gcc' CXX='distcc g++' -jN" -</pre> - - <p>See the notes for parallel builds.</p> - </dd> - <dt>Can I use ccache to speed up builds?</dt> - <dd> - <p>Yes. See the <a href="/en/ccache" title="en/ccache">ccache</a> page for more details. Use of ccache is highly encouraged to speed up builds.</p> - </dd> - <dt>Where else can I save cycles?</dt> - <dd>Redirecting stdout, rather than dumping it into a terminal, can save between 30 seconds and 5 minutes on a build. Displaying lots of text is slow!</dd> -</dl> - -<h2 id="Build_configurations">Build configurations</h2> - -<dl> - <dt>Can I build multiple Mozilla-based projects from a single source tree?</dt> - <dd>Yes! Each project must be built in its own objdir.</dd> - <dt>What is a .mozconfig file?</dt> - <dd>It tells which Mozilla application to build and contains configuration options. See <a href="/en/Configuring_Build_Options#Using_a_.mozconfig_Configuration_File" title="https://developer.mozilla.org/en/configuring_build_options#Using_a_.mozconfig_Configuration_File">Using a .mozconfig configuration file</a>.</dd> - <dt>What is an objdir?</dt> - <dd> - <p>An objdir build refers to the process of creating the output files in a different place than where the source lives. This is a standard feature of most configure-based projects. It allows you to build for multiple configurations, including multiple platforms if you use a network filesystem, from a single source tree. It also avoids tainting your source tree so that you know that the files in your tree have not been modified by the build process.</p> - - <p>If you run configure by hand, you can use the standard method of creating an empty directory any place on the disk, changing to that directory and running /path/to/mozilla/configure from there.</p> - - <pre class="eval">mkdir obj-debug -cd obj-debug -../mozilla/configure -</pre> - - <p>If you use client.mk to build, you can add the following to your mozconfig file:</p> - - <pre class="eval">mk_add_options MOZ_OBJDIR=/path/to/objdir -</pre> - </dd> - <dt>Can I cross-compile Mozilla?</dt> - <dd>Yes, see the <a class="external" href="http://www.mozilla.org/build/cross-compiling.html">Cross-Compiling Mozilla</a> document for details.</dd> - <dt>How do I force the build system to pick up any of the changes made to my mozconfig file?</dt> - <dd>Touch any of the configure scripts in the tree. There is no explicit dependency upon the mozconfig file as the file can reside anywhere via the MOZCONFIG environment variable.</dd> - <dt> </dt> -</dl> - -<h2 id="Implementation_questions">Implementation questions</h2> - -<dl> - <dt>What type of build system does Mozilla use?</dt> - <dd>Mozilla uses a thin GNU configure layer on top of a recursive makefile build system on all platforms. Like most configure-based projects, it uses GNU autoconf to generate the configure script. GNU make is used to drive the build process.</dd> - <dt>Why use GNU make?</dt> - <dd>GNU make has been ported to a lot of systems. This makes porting Mozilla to those systems a bit easier. Using only the subset of make features that are supported by the native make program on 10 different platforms would make the build system unnecessarily complicated.</dd> - <dt>Will any other version of make work?</dt> - <dd>No. The Mozilla makefiles use GNU make specific features which will only work with gnu make.</dd> - <dt>Why aren't you using automake?</dt> - <dd>Part of Netscape's legacy system involved using GNU make's -include feature to include a common set of rules from a handful of files in every Makefile that needed to use them. With this centralized rule system, one of the primary selling points of automake was made inconsequential. Also, at the time, Mozilla's method of building libraries did not mesh well with libtool.</dd> - <dt>What happened to the nmake and CodeWarrior build systems?</dt> - <dd>They no longer exist in the current tree. nmake build support was dropped during the Mozilla 1.2a release cycle. The Mac CFM build system was dropped along with OS 9 support shortly after the Mozilla 1.3 release.</dd> - <dt>Why not ant, tmake, scons or <em>insert your favorite build system here</em>?</dt> - <dd>Mainly, because no one has implemented these systems for Mozilla. When Mozilla was first open sourced, it only contained the legacy Netscape system. The autoconf layer was added on a branch and maintained in parallel for 6 months before it became the standard build system for the unix build. Several experimental ports to various systems have failed because of the size of the project. Because building Mozilla involves much more than just compiling, any port requires system investment in creating custom rules.</dd> - <dt>If I wanted to implement my favorite build system for Mozilla, would Mozilla start using it? I don't want to waste my time if you aren't going to use it.</dt> - <dd>There's no guarantee that any code written for Mozilla will be accepted into the default tree. Any build system that is implemented would have to show that it's better overall than the current build system. Speed, flexibility, portability and the ability for a large group of developers who have 3+ years experience with the current build system to easily transition to the new system would be the major factors in deciding to switch. If you are serious and willing to do lots of work, contact <a href="/User:Benjamin_Smedberg" title="User:Benjamin_Smedberg">User:Benjamin Smedberg</a> to discuss the details of your proposal.</dd> - <dt>Why doesn't Mozilla support autoconf 2.5x?</dt> - <dd> - <p>Simply put, autoconf 2.5x does not offer anything to make the upgrade worth the effort. Autoconf 2.5x is not backwards compatible with autoconf 2.13 and the additional restrictions made by the newer versions of autoconf would require a major rewrite of the Mozilla build system for questionable gain.</p> - - <p>Some of the 2.13 features, such as the ability to pass additional arguments to sub-configures, are not available in 2.5x. People have asked repeated about those features on the autoconf mailing list without any favorable response. Rewriting the configures of the sub-projects of Mozilla (NSPR & LDAP) is not an acceptable tradeoff. The sub-projects are also standalone projects and forking an entire codebase because of a build system incompatiblity is silly.</p> - </dd> - <dt>Why doesn't NSS use autoconf?</dt> - <dd>The NSS project is also used outside of the Mozilla project and the NSS project members did not feel that moving to autoconf was worth the cost. See <a class="link-https" href="https://bugzilla.mozilla.org/show_bug.cgi?id=52990" title="https://bugzilla.mozilla.org/show_bug.cgi?id=52990">bug 52990</a> for details.</dd> -</dl> - -<h2 id="See_also">See also</h2> - -<ul> - <li><a href="/en/Debugging_Mozilla_on_Windows_FAQ" title="en/Debugging_Mozilla_on_Windows_FAQ">Debugging Mozilla on Windows FAQ</a>: Tips on how to debug Mozilla on Windows</li> -</ul> diff --git a/files/pt-br/mozilla/developer_guide/source_code/index.html b/files/pt-br/mozilla/developer_guide/source_code/index.html deleted file mode 100644 index e279c02e6e..0000000000 --- a/files/pt-br/mozilla/developer_guide/source_code/index.html +++ /dev/null @@ -1,71 +0,0 @@ ---- -title: Trabalhando com o código-fonte Mozilla -slug: Mozilla/Developer_guide/Source_Code -translation_of: Mozilla/Developer_guide/Source_Code -original_slug: Mozilla/Developer_guide/Codigo_Fonte ---- -<p>Os artigos abaixo vão ajuda-lo a obter o código-fonte Mozilla, aprender a navegar pelo código e como ter as suas modificações aceitas para inclusão no repositório principal.</p> -<table class="mainpage-table"> - <tbody> - <tr> - <td colspan="2"> - <h2 id="Tópicos_da_documentação">Tópicos da documentação</h2> - </td> - </tr> - <tr> - <td> - <dl> - <dt> - <a class="internal" href="/En/Developer_Guide/Source_Code/Mercurial" title="En/Mozilla Source Code (Mercurial)">Obtendo o código do repositório Mercurial</a></dt> - <dd> - Se você planeja contribuir com o projeto Mozilla, a melhor forma de obter o código-fonte é fazendo checkout do repositório versionado. Aprenda aqui como fazê-lo.</dd> - <dt> - <a class="internal" href="/En/Developer_Guide/Source_Code/Downloading_Source_Archives" title="En/Mozilla Source Code (HTTP//FTP)">Baixando o código usando HTTP ou FTP</a></dt> - <dd> - Se você quer obter o código de uma versão específica ou de um produto Mozilla em particular, você pode optar por baixar um pacote de código-fonte.</dd> - <dt> - <a class="internal" href="/en/Viewing_and_searching_Mozilla_source_code_online" title="En/Viewing and searching Mozilla source code online">Vendo e buscando pelo código-fonte Mozilla online</a></dt> - <dd> - Aprenda a usar a MXR, a ferramenta Mozilla de busca e navegação para acessar o código-fonte. Esta não é uma boa forma de baixar o código, mas é uma ótima maneira de fazer buscas nele.</dd> - <dt> - <a class="internal" href="/en/Mozilla_Source_Code_Directory_Structure" title="en/Mozilla Source Code Directory Structure">Navegando no código-fonte Mozilla</a></dt> - <dd> - Aprenda a respeito das várias pastas na árvore de código-fonte da Mozilla e como encontrar o que você está procurando.</dd> - <dt> - <a class="external" href="/en/Introduction#Find_a_bug_we%27ve_identified_as_being_good_for_newcomers" title="/en/Introduction#Find_a_bug_we%27ve_identified_as_being_good_for_newcomers">Bugs para novatos</a></dt> - <dd> - Se você é novo no projeto e quer algo para trabalhar, olhe aqui.</dd> - </dl> - </td> - <td> - <dl> - <dt> - <a class="internal" href="/En/Developer_Guide/Coding_Style" title="En/Mozilla Coding Style Guide">Guia de estilo do código Mozilla</a></dt> - <dd> - O guia de estilo do código provê informações sobre como você deve formatar o seu código-fonte para garantir que você não sofra bullying dos revisadores.</dd> - <dt> - <a href="/En/Developer_Guide/Interface_development_guide" title="En/Developer Guide/Interface development guide">Guia de desenvolvimento de interfaces</a></dt> - <dd> - Diretrizes e documentação sobre como criar e atualizar interfaces XPCOM.</dd> - <dt> - <a class="link-https" href="https://wiki.mozilla.org/Build:TryServer" title="https://wiki.mozilla.org/Build:TryServer">Servidores de teste</a></dt> - <dd> - Os produtos Mozilla são compilados em pelo menos três plataformas. Se você não tem acesso a todas elas, você pode usar os servidores de teste para testar seus patches e ter certeza que eles passam nos testes.</dd> - <dt> - <a class="internal" href="/en/Creating_a_patch" title="En/Creating a patch">Criando um patch</a></dt> - <dd> - Após fazer mudanças no código Mozilla, o próximo passo (depois de ter certeza que ele funciona) é criar um patch e envia-lo para revisão. <em>Esse artigo precisa ser completamente atualizado para o Mercurial.</em></dd> - <dt> - <a class="external" href="http://www.mozilla.org/hacking/committer/" title="http://www.mozilla.org/hacking/committer/">Obtendo acesso para fazer commit no código-fonte</a></dt> - <dd> - Sentindo-se preparado para untar-se aos poucos e orgulhosos <em>committers</em>? Descubra como obter acesso para gravação no código Mozilla.</dd> - <dt> - <a class="internal" href="/En/Developer_Guide/Source_Code/CVS" title="En/Mozilla Source Code (CVS)">Obtendo o código Mozilla antigo usando CVS</a></dt> - <dd> - Versões antigas do código-fonte Mozilla, assim como as versões atuais do NSS e NSPR, são mantidas num repositório CVS. Aprenda sobre isso nesse artigo.</dd> - </dl> - </td> - </tr> - </tbody> -</table> -<p>{{ languages( { "de": "de/Entwicklerhandbuch/Quelltexte", "ja": "ja/Developer_Guide/Source_Code" } ) }}</p> |