ecl/src/doc/install.in.html
2005-03-15 14:22:29 +00:00

75 lines
1.8 KiB
HTML

<h2>Installation</h2>
<p>You should read the <a href="#configure">Autoconf based configuration</a>
if you use ECL on a unix-like platform, such as
<ul>
<li>Linux, NetBSD, FreeBSD, Solaris.
<li>OSX
<li>Cygwin or Mingw32 on Windows.
</ul>
<p>If you want to compile ECL using Microsoft C++ you should read <a
href="#msvc">the appropiate section</a>.
<p>If you want to cross-compile ECL, there is also <a href="#cross">a
chapter</a> on how to pre-configure, write down a configuration file
and finish the compilation.
<h3><a name="msvc">Microsoft C++</a></h3>
<ul>
<li>Change to the <tt>msvc</tt> directory.
<li>Run <tt>nmake</tt> to build ECL.
<li>Run <tt>nmake flatinstall prefix=d:\Software\ECL</tt> where the
<tt>prefix</tt> is the directory where you want to install ECL.
<li>Optionally, if you want to build a self-installing executable, you can install NSIS
and run <tt>nmake windows-nsi</tt>.
</ul>
<h3><a name="configure">Autoconf based configuration</a></h3>
<ul>
<li>Unpack the tar file
<pre>
gunzip -c ecl.tgz | tar xf -
</pre>
<li>Run the configuration file.
<pre>
cd ecl-@VERSION@
./configure
</pre>
The previous step creates a directory with the name <b>build</b>, and
stores a bunch of makefiles in it.
<li>Use GNU make to invoke the compilation
<pre>
make
</pre>
<li>If you want to test the fresh new executable before installing. You you
should invoke ECL from withing the build directory using the "-dir ./"
argument to advice him about the right place to find header files, libraries,
etc. For instance, under linux the build directory is "linux" and we would do
<pre>
$ ./configure --prefix=$HOME
[...]
$ cd build
$ make
[...]
$ ./ecl -dir ./
</pre>
<li>Install it in the desired location
<pre>
make install
</pre>
</ul>
<h3><a name="cross">Cross compiling ECL</a></h3>
[To be written]