<html lang="en">
<head>
<title>Building the Development Sources - GNU Octave</title>
<meta http-equiv="Content-Type" content="text/html">
<meta name="description" content="GNU Octave">
<meta name="generator" content="makeinfo 4.13">
<link title="Top" rel="start" href="index.html#Top">
<link rel="up" href="Contributing-Guidelines.html#Contributing-Guidelines" title="Contributing Guidelines">
<link rel="prev" href="How-to-Contribute.html#How-to-Contribute" title="How to Contribute">
<link rel="next" href="Basics-of-Generating-a-Changeset.html#Basics-of-Generating-a-Changeset" title="Basics of Generating a Changeset">
<link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage">
<meta http-equiv="Content-Style-Type" content="text/css">
<style type="text/css"><!--
pre.display { font-family:inherit }
pre.format { font-family:inherit }
pre.smalldisplay { font-family:inherit; font-size:smaller }
pre.smallformat { font-family:inherit; font-size:smaller }
pre.smallexample { font-size:smaller }
pre.smalllisp { font-size:smaller }
span.sc { font-variant:small-caps }
span.roman { font-family:serif; font-weight:normal; }
span.sansserif { font-family:sans-serif; font-weight:normal; }
--></style>
</head>
<body>
<div class="node">
<a name="Building-the-Development-Sources"></a>
<p>
Next: <a rel="next" accesskey="n" href="Basics-of-Generating-a-Changeset.html#Basics-of-Generating-a-Changeset">Basics of Generating a Changeset</a>,
Previous: <a rel="previous" accesskey="p" href="How-to-Contribute.html#How-to-Contribute">How to Contribute</a>,
Up: <a rel="up" accesskey="u" href="Contributing-Guidelines.html#Contributing-Guidelines">Contributing Guidelines</a>
<hr>
</div>
<h3 class="section">D.2 Building the Development Sources</h3>
<p>In addition to all the tools (both optional and required) that are
listed in <a href="Build-Dependencies.html#Build-Dependencies">Build Dependencies</a> you will need:
<dl>
<dt>Mercurial<dd>Distributed version control system (<a href="http://mercurial.selenic.com">http://mercurial.selenic.com</a>).
Octave's sources are stored in a Mercurial archive.
<br><dt>Git<dd>Distributed version control system (<a href="http://git-scm.com">http://git-scm.com</a>). The
gnulib sources that Octave depends on are stored in a Git archive.
</dl>
<p>Once you have the required tools installed, you can build Octave by
doing
<ul>
<li>Check out a copy of the Octave sources:
<pre class="example"> hg clone http://www.octave.org/hg/octave
</pre>
<li>Change to the top-level directory of the newly checked out sources:
<pre class="example"> cd octave
</pre>
<li>Generate the necessary configuration files:
<pre class="example"> ./autogen.sh
</pre>
<li>Create a build directory and change to it:
<pre class="example"> mkdir build
cd build
</pre>
<p>By using a separate build directory, you will keep the source directory
clean and it will be easy to completely remove all files generated by
the build. You can also have parallel build trees for different
purposes that all share the same sources. For example, one build tree
may be configured to disable compiler optimization in order to allow for
easier debugging while another may be configured to test building with
other specialized compiler flags.
<li>Run Octave's configure script from the build directory:
<pre class="example"> ../configure
</pre>
<li>Run make in the build directory:
<pre class="example"> make
</pre>
</ul>
<p>Once the build is finished, you will see a message like the following:
<pre class="example"> Octave successfully built. Now choose from the following:
./run-octave - to run in place to test before installing
make check - to run the tests
make install - to install (PREFIX=...)
</pre>
</body></html>
