Home page
Latest release
Browse CVS
Checkout CVS
Mailing list
NewsRSS Feed Available


You should read the Autoconf based configuration if you use ECL on a unix-like platform, such as

  • Linux, NetBSD, FreeBSD, Solaris 9
  • Mac OSX (See below)
  • Cygwin or Mingw32 on Windows.

If you want to compile ECL using Microsoft C++ you should read the appropiate section.

For OSX you should also read a section which specifies how to build ECL for different versions of the operating system.

If you want to cross-compile ECL, there is also a chapter on how to pre-configure, write down a configuration file and finish the compilation.

Autoconf based configuration

  • Unpack the tar file
    	gunzip -c ecl.tgz | tar xf -
  • Run the configuration file.
    	cd ecl-@PACKAGE_VERSION@
    The previous step creates a directory with the name build, and stores a bunch of makefiles in it. Note: If you are building under Solaris 9, you should rather use
    	./configure --enable-slow-config --with-system-gmp=no
    because otherwise ECL will fail to detect the 64-bit capabilities of the operating system.
  • Use GNU make to begin building ECL
  • If you want to test the fresh new executable before installing, you can do it. You should invoke ECL from withing the build directory using the "-dir ./" argument to advice it about the right place to find header files, libraries, etc
    	$ ./configure --prefix=$HOME
    	$ cd build
    	$ make
    	$ ./ecl -dir ./
  • Install it in the preconfigured location
    	make install

Microsoft C++

If you have a commercial version of Microsoft Visual Studio, the steps are simple:

  • Change to the msvc directory.
  • Run nmake to build ECL.
  • Run nmake flatinstall prefix=d:\Software\ECL where the prefix is the directory where you want to install ECL.
  • Optionally, if you want to build a self-installing executable, you can install NSIS and run nmake windows-nsi.

If you want to build ECL using the free Microsoft Visual C++ Toolkit 2003, you should follow these before building ECL:

  • Download and install Microsoft Visual C++ Toolkit.
  • Download and install the Microsoft Platform SDK
  • Download NMAKE and install. There is an old version in Microsoft's download page.
  • Download and install the .NET Framework SDK. Copy the files msvcrt.lib an msvcrtd.lib from this toolkit to the directory where the Visual C++ Toolkit keeps it libraries. Afterwards you can uninstall the .NET SDK.
  • Make sure that
    • %PATH% includes the directories bin of both the C++ Toolkit, NMAKE and the SDK.
    • %INCLUDE% includes the directories include of both the C++ Toolkit and the SDK.
    • %LIB%includes the directories lib of both the C++ Toolkit and the SDK.


ECL now compiles with GCC 4.0. You need not specify any particular options. But if you still experience some strange behaviour, try compiling with a previous version of the compiler before reporting the bug.

For compiling with GCC 3.3 (shipped with XCode >= 2) you must instruct configure to use a different compiler, as in

$ CC=gcc-3.3 ./configure --prefix=/opt/local

Cross compiling ECL

[To be written]


SourceForge Logo