Please note, this is a STATIC archive of website developer.mozilla.org from 03 Nov 2016, cach3.com does not collect or store any user information, there is no "phishing" involved.

Revision 513947 of Getting SpiderMonkey source code

  • Revision slug: SpiderMonkey/Getting_SpiderMonkey_source_code
  • Revision title: Getting SpiderMonkey source code
  • Revision id: 513947
  • Created:
  • Creator: wilberto
  • Is current revision? No
  • Comment

Revision Content

You can get the SpiderMonkey source code in gzipped form or directly from the Mercurial repository.

Downloading gzipped SpiderMonkey source code

You can download gzipped SpiderMonkey source code from the following URL:

https://ftp.mozilla.org/pub/mozilla.org/js/

Here is a command-line example of downloading and unzipping SpiderMonkey source code version 24.2:

mkdir mozilla
cd mozilla
wget https://ftp.mozilla.org/pub/mozilla.org/js/mozjs-24.2.0.tar.bz2
tar xzf mozjs-24.2.0.tar.bz2

These commands should work on most platforms including Windows, as long as on Windows you are using the MozillaBuild bash shell.

Getting the latest SpiderMonkey source code from Mercurial

The Mercurial repository at https://hg.mozilla.org/mozilla-central/ hosts the latest SpiderMonkey sources. Mercurial is also known as hg.

The following command line downloads the entire Mozilla repository, including the full change history and a lot of Gecko and Firefox source code that isn't part of SpiderMonkey. It also changes to the SpiderMonkey directory (js/src).

hg clone https://hg.mozilla.org/mozilla-central/
cd js/src

To avoid getting the full change history, click the zip or gz links at https://hg.mozilla.org/index.cgi/mozilla-central/file/tip. This fetches a snapshot of the current Mozilla tree.

If you have problems with the instructions above, you can read the full details of using Mercurial to get Mozilla code here. That page also contains links to several bundles, which can be useful if you have a poor network connection.

Getting the latest SpiderMonkey source code from Git

The following command line downloads the entire Mozilla repository, including the full change history and a lot of Gecko and Firefox source code that isn't part of SpiderMonkey. It also changes to the SpiderMonkey directory (js/src).

git clone https://github.com/mozilla/gecko-dev.git
cd mozilla-central/js/src

If you have any problems check the https://wiki.mozilla.org/Github page.

Getting older SpiderMonkey sources from CVS

Note: You will need to explicitly fetch the JavaScript shell sources even if you currently build another Mozilla project, as there are files specific to the shell that are not normally found in a Mozilla source tree.

Just like when you're fetching any other Mozilla project from CVS, you need to log into the CVS server first. To do this, cd into the base directory you'd like to check out the code into, then enter the following command at your command line:

cvs -d :pserver:[email protected]:/cvsroot login

When prompted, enter the password anonymous.

Once you've logged in, cd into the root of your CVS tree and enter the following command:

cvs -d :pserver:[email protected]:/cvsroot co -l mozilla/js/src mozilla/js/src/config mozilla/js/src/editline mozilla/js/src/fdlibm

This checks out all the files needed in order to build the JavaScript shell.

If you also want the regression tests, add this command:

cvs -d :pserver:[email protected]:/cvsroot co mozilla/js/tests

Getting older branch versions of SpiderMonkey

If you want to experiment with a specific branch's version of SpiderMonkey, you need to check out js/src from branch but check out editline and config from trunk:

cvs -d :pserver:[email protected]:/cvsroot co -l -r BRANCH_NAME mozilla/js/src mozilla/js/src/fdlibm
cvs -d :pserver:[email protected]:/cvsroot co -l mozilla/js/src/config mozilla/js/src/editline

Change BRANCH_NAME to the name of the branch you want to check out. You can use a JavaScript branch name (e.g. JS_1_7_ALPHA_BRANCH) or a Mozilla branch name (e.g. MOZILLA_1_8_BRANCH).

Revision Source

<p>You can get the SpiderMonkey source code in gzipped form or directly from the Mercurial repository.</p>
<h2 id="Downloading_gzipped_SpiderMonkey_source_code">Downloading gzipped SpiderMonkey source code</h2>
<p>You can download gzipped SpiderMonkey source code from the following URL:</p>
<pre>
<span class="plain"><a href="https://ftp.mozilla.org/pub/mozilla.org/js/" title="https://ftp.mozilla.org/pub/mozilla.org/js/">https://ftp.mozilla.org/pub/mozilla.org/js/</a></span>
</pre>
<p>Here is a command-line example of downloading and unzipping SpiderMonkey source code version 24.2:</p>
<pre>
mkdir mozilla
cd mozilla
wget <a href="https://ftp.mozilla.org/pub/mozilla.org/js/mozjs-24.2.0.tar.bz2">https://ftp.mozilla.org/pub/mozilla.org/js/mozjs-24.2.0.tar.bz2</a>
tar xzf mozjs-24.2.0.tar.bz2
</pre>
<p>These commands should work on most platforms including Windows, as long as on Windows you are using the <a href="/En/Developer_Guide/Build_Instructions/Windows_Prerequisites#mozillabuild" title="https://developer.mozilla.org/en/Windows_Build_Prerequisites#mozillabuild">MozillaBuild</a> bash shell.</p>
<h2 id="Getting_the_latest_SpiderMonkey_source_code" name="Getting_the_latest_SpiderMonkey_source_code">Getting the latest SpiderMonkey source code from Mercurial</h2>
<p>The <a href="/en/Mercurial" title="en/Mercurial">Mercurial</a> repository at <a class="external" href="https://hg.mozilla.org/mozilla-central/" title="https://hg.mozilla.org/mozilla-central/">https://hg.mozilla.org/mozilla-central/</a> hosts the latest SpiderMonkey sources. Mercurial is also known as hg.</p>
<p>The following command line downloads the entire Mozilla repository, including the full change history and a lot of Gecko and Firefox source code that isn't part of SpiderMonkey. It also changes to the SpiderMonkey directory (js/src).</p>
<pre class="eval">
hg clone <span class="nowiki">https://hg.mozilla.org/mozilla-central/</span>
cd js/src
</pre>
<p>To avoid getting the full change history, click the <code>zip</code> or <code>gz</code> links at <a class="external" href="https://hg.mozilla.org/index.cgi/mozilla-central/file/tip" title="https://hg.mozilla.org/index.cgi/mozilla-central/file/tip">https://hg.mozilla.org/index.cgi/mozilla-central/file/tip</a>. This fetches a snapshot of the current Mozilla tree.</p>
<p>If you have problems with the instructions above, you can read the full details of using Mercurial to get Mozilla code <a href="https://developer.mozilla.org/en-US/docs/Developer_Guide/Source_Code/Mercurial" title="https://developer.mozilla.org/en-US/docs/Developer_Guide/Source_Code/Mercurial">here</a>. That page also contains links to several bundles, which can be useful if you have a poor network connection.</p>
<h2 id="Getting_the_latest_SpiderMonkey_source_code" name="Getting_the_latest_SpiderMonkey_source_code">Getting the latest SpiderMonkey source code from Git</h2>
<p>The following command line downloads the entire Mozilla repository, including the full change history and a lot of Gecko and Firefox source code that isn't part of SpiderMonkey. It also changes to the SpiderMonkey directory (js/src).</p>
<pre class="eval">
git clone https://github.com/mozilla/gecko-dev.git
cd mozilla-central/js/src
</pre>
<p>If you have any problems check the <a href="https://wiki.mozilla.org/Github" title="https://wiki.mozilla.org/Github">https://wiki.mozilla.org/Github</a> page.</p>
<h2 id="Getting_older_SpiderMonkey_sources_from_CVS" name="Getting_older_SpiderMonkey_sources_from_CVS">Getting older SpiderMonkey sources from CVS</h2>
<div class="note">
 <strong>Note:</strong> You will need to explicitly fetch the JavaScript shell sources even if you currently build another Mozilla project, as there are files specific to the shell that are not normally found in a Mozilla source tree.</div>
<p>Just like when you're fetching any other Mozilla project from CVS, you need to log into the CVS server first. To do this, <code>cd</code> into the base directory you'd like to check out the code into, then enter the following command at your command line:</p>
<pre>
cvs -d&nbsp;:pserver:[email protected]:/cvsroot login
</pre>
<p>When prompted, enter the password&nbsp;<code>anonymous</code>.</p>
<p>Once you've logged in, <code>cd</code> into the root of your CVS tree and enter the following command:</p>
<pre>
cvs -d&nbsp;:pserver:[email protected]:/cvsroot co -l mozilla/js/src mozilla/js/src/config mozilla/js/src/editline mozilla/js/src/fdlibm
</pre>
<p>This checks out all the files needed in order to build the JavaScript shell.</p>
<p>If you also want the regression tests, add this command:</p>
<pre>
cvs -d&nbsp;:pserver:[email protected]:/cvsroot co mozilla/js/tests
</pre>
<h2 id="Getting_older_branch_versions_of_SpiderMonkey" name="Getting_older_branch_versions_of_SpiderMonkey">Getting older branch versions of SpiderMonkey</h2>
<p>If you want to experiment with a specific branch's version of SpiderMonkey, you need to check out js/src from branch but check out <code>editline</code> and <code>config</code> from trunk:</p>
<pre>
cvs -d&nbsp;:pserver:[email protected]:/cvsroot co -l -r <em><var>BRANCH_NAME</var></em> mozilla/js/src mozilla/js/src/fdlibm
cvs -d&nbsp;:pserver:[email protected]:/cvsroot co -l mozilla/js/src/config mozilla/js/src/editline
</pre>
<p>Change <code><em>BRANCH_NAME</em></code> to the name of the branch you want to check out. You can use a JavaScript branch name (e.g. <code>JS_1_7_ALPHA_BRANCH</code>) or a Mozilla branch name (e.g. <code>MOZILLA_1_8_BRANCH</code>).</p>
Revert to this revision