diff options
Diffstat (limited to 'files/ko/mozilla/developer_guide/source_code')
| -rw-r--r-- | files/ko/mozilla/developer_guide/source_code/cvs/index.html | 137 | ||||
| -rw-r--r-- | files/ko/mozilla/developer_guide/source_code/index.html | 49 |
2 files changed, 0 insertions, 186 deletions
diff --git a/files/ko/mozilla/developer_guide/source_code/cvs/index.html b/files/ko/mozilla/developer_guide/source_code/cvs/index.html deleted file mode 100644 index 81325c1507..0000000000 --- a/files/ko/mozilla/developer_guide/source_code/cvs/index.html +++ /dev/null @@ -1,137 +0,0 @@ ---- -title: Mozilla Source Code Via CVS -slug: Mozilla/Developer_guide/Source_Code/CVS -original_slug: Mozilla_Source_Code_Via_CVS ---- -<p>Those doing active development can check out the latest source using CVS. This is the preferred method if you plan to provide patches and fix bugs, as it lets you get up-to-the-minute changes and merge them with your own.</p> -<p>If you want to compile a product for release, it is generally better to <a href="ko/Download_Mozilla_Source_Code">Download Mozilla Source Code</a> tarballs.</p> -<h3 id="Quick_Start_Guide" name="Quick_Start_Guide">Quick Start Guide</h3> -<p><span class="comment">I seem to not be editing this page in what others on this development site deem appropriate. So, if you are going to just remove this section, can you please be so kind as to suggest an alternate title of a new page that I can put this information on? Thanks, Jeff Carr</span></p> -<p>The basic steps to checkout the trunk (unstable) Firefox sources are:</p> -<pre class="eval">cvs -d <a class="link-mailto" href="mailto::pserver:anonymous:anonymous@cvs-mirror.mozilla.org" rel="freelink">:pserver:anonymous:anonymous@cvs-mirror.mozilla.org</a>:/cvsroot co mozilla/client.mk -cd mozilla -make -f client.mk checkout MOZ_CO_PROJECT=browser -</pre> -<p>Note that on Windows, your source tree must be located at a /cygdrive/<c> mount point. It must not be located within your /home.</p> -<h3 id="Getting_Started" name="Getting_Started">Getting Started</h3> -<p>CVS means "Concurrent Versioning System". To learn more about CVS in general, visit <a class="external" href="http://ximbiot.com/cvs/manual/">ximbiot.com</a>, or read the <a class="external" href="http://ximbiot.com/cvs/cvshome/docs/blandy.html">tutorial</a>.</p> -<p>Anyone can check out (also known as "pull" or "download") the sources via CVS, but only certain people have the ability to check in (make changes, also known as "commit"). Those people are the <a class="external" href="http://www.mozilla.org/owners.html">module owners</a> and their delegates. Read our document on <a class="external" href="http://www.mozilla.org/hacking/">hacking mozilla</a> to find out how to get the ability to check in. You may also wish to read about <a class="external" href="http://www.mozilla.org/cvs-ssh-faq.html">using SSH to connect to CVS</a>.</p> -<h4 id="Requirements" name="Requirements">Requirements</h4> -<p>To check out the sources, you need to be running <a class="external" href="http://www.nongnu.org/cvs/">CVS</a> 1.11 or later. 1.12.13 does not work with the CVS server, and instead results in hangs, although 1.12.9 is known to work. Furthermore, you must use <a class="external" href="http://www.gnu.org/software/make/">GNU make</a> to check out and build Mozilla. No other "make" program is acceptable. On windows, mac and regular GNU systems (like GNU/Linux), use "make" to run GNU make; on most non-GNU unixes (like e.g. Solaris, etc.), use "gmake".</p> -<h3 id="CVS_Client_Settings" name="CVS_Client_Settings">CVS Client Settings</h3> -<p>The "cvsroot" (repository identification string) used for anonymous access to Mozilla CVS is</p> -<pre class="eval"><a class="link-mailto" href="mailto::pserver:anonymous:anonymous@cvs-mirror.mozilla.org" rel="freelink">:pserver:anonymous:anonymous@cvs-mirror.mozilla.org</a>:/cvsroot -</pre> -<p>If you are using a graphical CVS interface, use the following server data:</p> -<ul> - <li><b>host</b>: "cvs-mirror.mozilla.org"</li> - <li><b>repository path</b>: "/cvsroot"</li> - <li><b>user</b>: "anonymous"</li> - <li><b>password</b>: "anonymous"</li> - <li><b>connection type</b>: pserver</li> - <li><b>port</b>: default (2401)</li> -</ul> -<h3 id="Selecting_a_Project_to_Pull" name="Selecting_a_Project_to_Pull">Selecting a Project to Pull</h3> -<p>Since several different applications are built from the same basic source code, you must choose which application to checkout on the command line using the <code>MOZ_CO_PROJECT</code> variable. This information has to be supplied when it comes to the checkout of the actual source code (see the appropriate <a href="#Checkout">checkout</a> <a href="#Checkout_2">section</a> below, according to the branch you want to checkout). The possible options include the following:</p> -<dl> - <dt> - browser </dt> - <dd> - The standalone "Firefox" browser.</dd> - <dt> - mail </dt> - <dd> - The standalone "Thunderbird" mail/news client.</dd> - <dt> - suite </dt> - <dd> - The traditional "Mozilla" SeaMonkey suite of browser, mail/news, composer, and other applications.</dd> - <dt> - minimo </dt> - <dd> - The standalone browser for small devices.</dd> - <dt> - composer </dt> - <dd> - The standalone HTML composer.</dd> - <dt> - calendar </dt> - <dd> - The standalone "Sunbird" calendar app.</dd> - <dt> - xulrunner </dt> - <dd> - The next-generation XUL application launcher.</dd> - <dt> - macbrowser </dt> - <dd> - The "Camino" native browser for Macintosh.</dd> - <dt> - all </dt> - <dd> - Check out sources for all of the above projects, plus some additional utility code</dd> -</dl> -<p>Multiple projects can be specified with commas: <code>MOZ_CO_PROJECT=suite,browser,xulrunner</code>.</p> -<p><b>Note</b> that if you are using a custom <tt><a href="ko/Configuring_Build_Options#Using_a_.mozconfig_Configuration_File">.mozconfig</a></tt> file, you can also specify <code>MOZ_CO_PROJECT</code> there, instead of including it on the command line.</p> -<h3 id="Checking_Out_a_New_Source_Tree" name="Checking_Out_a_New_Source_Tree">Checking Out a New Source Tree</h3> -<h4 id="Check_Tinderbox" name="Check_Tinderbox">Check Tinderbox</h4> -<p>Before pulling a tree, you should always check the appropriate <a href="ko/Tinderbox">Tinderbox</a> to make sure that the codebase is not broken. If there are red tinderboxes, it is usually advisable to wait until they are green before pulling a tree.</p> -<h4 id="Branch_HEAD" name="Branch_HEAD">Branch HEAD</h4> -<p>To check out a new source tree from scratch, get the <tt>client.mk</tt> file which contains makefile instructions which are used to pull the rest of the tree:</p> -<pre class="eval">$ cvs -d <a class="link-mailto" href="mailto::pserver:anonymous:anonymous@cvs-mirror.mozilla.org" rel="freelink">:pserver:anonymous:anonymous@cvs-mirror.mozilla.org</a>:/cvsroot co mozilla/client.mk -</pre> -<p>Note: if you have already set up a <tt><a href="ko/Configuring_Build_Options#Using_a_.mozconfig_Configuration_File">.mozconfig</a></tt> file, you may also need to check out the following files:</p> -<dl> - <dt> - Firefox </dt> - <dd> - <pre>cvs -d :pserver:anonymous:anonymous@cvs-mirror.mozilla.org:/cvsroot co mozilla/browser/config/mozconfig</pre> - </dd> - <dt> - Thunderbird </dt> - <dd> - <pre>cvs -d :pserver:anonymous:anonymous@cvs-mirror.mozilla.org:/cvsroot co mozilla/mail/config/mozconfig</pre> - </dd> -</dl> -<h4 id="Specific_Branch" name="Specific_Branch">Specific Branch</h4> -<p>If you want to check out the source code of a specific <a class="external" href="http://ximbiot.com/cvs/wiki/index.php?title=CVS--Concurrent_Versions_System_v1.12.12.1:_Branching_and_merging">CVS branch</a>, use</p> -<pre class="eval">$ cvs -d <a class="link-mailto" href="mailto::pserver:anonymous:anonymous@cvs-mirror.mozilla.org" rel="freelink">:pserver:anonymous:anonymous@cvs-mirror.mozilla.org</a>:/cvsroot co -r BRANCH mozilla/client.mk -</pre> -<p>instead. To, for example, pull the Firefox 2.0 development branch, replace BRANCH above with MOZILLA_1_8_BRANCH. For available branch tags in Mozilla, see <a href="ko/CVS_Tags">CVS Tags</a>.</p> -<p>The information on pulling project specific <code>.mozconfig</code> files as listed in the <a href="#Branch_HEAD">previous section</a> apply to other branches than HEAD as well of course.</p> -<h4 id="Checkout" name="Checkout">Checkout</h4> -<p>After having chosen the correct branch, run:</p> -<pre class="eval">$ cd mozilla -$ make -f client.mk checkout MOZ_CO_PROJECT=<i>option,option</i> -</pre> -<p>As mentioned above, if you are using a custom <code>.mozconfig</code> file where you have already specified the <code>MOZ_CO_PROJECT</code> variable, you do not need to repeat it here on command line.</p> -<div class="note"> - Always use <tt>client.mk</tt> to checkout the Mozilla sources: do not check out the <tt>mozilla/</tt> module directly. Various subprojects such as NSS, NSPR, and LDAP C SDK are pulled from stable release tags, even when regular mozilla development occurs on the trunk.</div> -<h3 id="Updating_a_Source_Tree" name="Updating_a_Source_Tree">Updating a Source Tree</h3> -<h4 id="Branch_HEAD_2" name="Branch_HEAD_2">Branch HEAD</h4> -<p>In order to update a source tree (be it branch HEAD or a specific branch) to latest branch HEAD, run:</p> -<pre class="eval">$ cd mozilla -$ cvs up -A client.mk -</pre> -<p>The -A option removes any "sticky branch" information, which leads to the effect that the tree is updated to HEAD.</p> -<h4 id="Specific_Branch_2" name="Specific_Branch_2">Specific Branch</h4> -<p>To update a source tree which was pulled from a specific branch, use</p> -<pre class="eval">$ cd mozilla -$ cvs up -r BRANCH client.mk -</pre> -<p>instead. Replace BRANCH by the tag of the branch you want to update.</p> -<h4 id="Checkout_2" name="Checkout_2">Checkout</h4> -<p>Having updated client.mk, you can do the checkout:</p> -<pre class="eval">$ make -f client.mk checkout MOZ_CO_PROJECT=<i>option,option</i> -</pre> -<p>As always, if you use a custom <code>.mozconfig</code> file where <code>MOZ_CO_PROJECT</code> is already defined, you do not need to repeat it on command line.</p> -<h3 id="Creating_a_Diff_File" name="Creating_a_Diff_File">Creating a Diff File</h3> -<p>In order to create a diff of a single local file against the current file in the repository, use:</p> -<pre class="eval">$ cvs diff -u8p FILENAME -</pre> -<p>See <a href="ko/Creating_a_patch">Creating a patch</a> for more information.</p> -<h3 id="Converting_a_Downloaded_Source_Tree" name="Converting_a_Downloaded_Source_Tree">Converting a Downloaded Source Tree</h3> -<p>Downloaded source trees from mozilla.org (<a href="ko/Download_Mozilla_Source_Code">source tarballs</a>) are already set up with CVS information, like a normal checkout. You can update these trees like normal trees to the latest code, without special action. See previous section on how to update a source tree.</p> -<p><br> - <span class="comment">interwiki link</span></p> -<p>{{ languages( { "fr": "fr/Obtenir_le_code_source_de_Mozilla_via_CVS", "ja": "ja/Mozilla_Source_Code_Via_CVS", "zh-cn": "cn/\u901a\u8fc7CVS\u83b7\u53d6\u6e90\u7801" } ) }}</p> diff --git a/files/ko/mozilla/developer_guide/source_code/index.html b/files/ko/mozilla/developer_guide/source_code/index.html deleted file mode 100644 index 13120b58e7..0000000000 --- a/files/ko/mozilla/developer_guide/source_code/index.html +++ /dev/null @@ -1,49 +0,0 @@ ---- -title: Working with Mozilla source code -slug: Mozilla/Developer_guide/Source_Code -tags: - - Developing Mozilla - - NeedsTranslation -translation_of: Mozilla/Developer_guide/Source_Code ---- -<p>The articles below will help you get your hands on the Mozilla source code, learn to navigate the code, and how to get the changes you propose checked into the tree.</p> - -<div class="row topicpage-table"> -<div class="section"> -<dl> - <dt><a class="internal" href="/en-US/Developer_Guide/Source_Code/Mercurial" title="En/Mozilla Source Code (Mercurial)">Getting the code from the Mercurial repository</a></dt> - <dd>If you plan to contribute to the Mozilla project, the best way to get the code is to check it out from the version control repository. Learn how to do that here.</dd> - <dt><a href="https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Using_the_VM">Getting a pre-configured Mozilla build system virtual machine</a></dt> - <dd>This is the easiest way to get started: use a VirtualBox virtual machine which is already configured with a complete build environment for you to use. Just boot the VM and build!</dd> - <dt><a class="internal" href="/en-US/Developer_Guide/Source_Code/Downloading_Source_Archives" title="En/Mozilla Source Code (HTTP//FTP)">Downloading the source code</a></dt> - <dd>If you want to fetch the code for a specific release of a particular Mozilla product, you may prefer to download a source code archive.</dd> - <dt><a class="internal" href="/en/Viewing_and_searching_Mozilla_source_code_online" title="En/Viewing and searching Mozilla source code online">Viewing and searching Mozilla source code online</a></dt> - <dd>Learn how to use MXR, Mozilla's online search and browsing tool for accessing the source code. This isn't a good way to download the code, but is a great way to search it.</dd> - <dt><a class="internal" href="/en/Mozilla_Source_Code_Directory_Structure" title="en/Mozilla Source Code Directory Structure">Navigating the Mozilla source code</a></dt> - <dd>Learn about the various folders in the Mozilla source tree, and how to find what you're looking for.</dd> - <dt><a class="external" href="/en/Introduction#Find_a_bug_we%27ve_identified_as_a_good_fit_for_new_contributors." title="/en/Introduction#Find_a_bug_we%27ve_identified_as_a_good_fit__for_new_contributors.">Bugs for newcomers</a></dt> - <dd>If you are new to the project and want something to work on, look here.</dd> -</dl> -</div> - -<div class="section"> -<dl> - <dt><a class="internal" href="/en-US/Developer_Guide/Coding_Style" title="En/Mozilla Coding Style Guide">Mozilla Coding Style Guide</a></dt> - <dd>The code style guide provides information about how you should format your source code to ensure that you don't get mocked by the reviewers.</dd> - <dt><a href="/en-US/Developer_Guide/Interface_development_guide" title="En/Developer Guide/Interface development guide">Interface development guide</a></dt> - <dd>Guidelines and documentation for how to create and update XPCOM interfaces.</dd> - <dt><a href="/en-US/docs/Mozilla/Developer_guide/CSS_Guidelines">The Firefox codebase: CSS Guidelines</a></dt> - <dd>This document contains guidelines defining how CSS inside the Firefox codebase should be written, it is notably relevant for Firefox front-end engineers.</dd> - <dt><a href="/en-US/docs/Mozilla/Developer_guide/SVG_Guidelines">SVG Cleanup Guide</a></dt> - <dd>Guidelines and best practices for shipping new SVGs.</dd> - <dt><a class="link-https" href="https://wiki.mozilla.org/Build:TryServer" title="https://wiki.mozilla.org/Build:TryServer">Try Servers</a></dt> - <dd>Mozilla products build on at least three platforms. If you don't have access to them all, you can use the try servers to test your patches and make sure the tests pass.</dd> - <dt><a class="internal" href="/en/Creating_a_patch" title="En/Creating a patch">Creating a patch</a></dt> - <dd>Once you've made a change to the Mozilla code, the next step (after making sure it works) is to create a patch and submit it for review. <em>This article needs to be updated fully for Mercurial.</em></dd> - <dt><a class="external" href="https://www.mozilla.org/hacking/committer/" title="https://www.mozilla.org/hacking/committer/">Getting commit access to the source code</a></dt> - <dd>Feel ready to join the few, the proud, the committers? Find out how to get check-in access to the Mozilla code.</dd> - <dt><a class="internal" href="/en-US/Developer_Guide/Source_Code/CVS" title="En/Mozilla Source Code (CVS)">Getting older Mozilla code from CVS</a></dt> - <dd>Older versions of the Mozilla source code, as well as the current versions of NSS and NSPR, are kept in a CVS repository. Learn about that in this article.</dd> -</dl> -</div> -</div> |