help links subscribe changes refresh edit

	OpenAxiom Sources
	↑

BuildOpenAxiom

Edit detail for BuildOpenAxiom revision 4 of 7

	1 2 3 4 5 6 7
Editor: alfredo Time: 2008/04/25 13:18:26 GMT-7
Note: Add information

changed:
-  See: http://svn.open-axiom.org/viewvc/*checkout*/open-axiom/trunk/INSTALL
 1. Lisp and noweb prerequisites

  If any of GCL or noweb is missing from the environment environment
  where you're building, then you need to either separately install
  them, or download the dependency tarball

    open-axiom-1.1.x-dep.tar.bz2

  Please, notice that GCL and noweb are needed only to *build*
  OpenAxiom.  If you plan to build OpenAxiom often, then it probably is
  a good idea to separately build and install those tools once for all.

  If you already have GCL and noweb installed, please go to step 2.

 1.a. Download the dependency tarball open-axiom-1.1.x-dep.tar.bz2

 1.b. Decompress the dependency tarball

      tar jxfv open-axiom-1.1.x-dep.tar.bz2


  That should decompress the dependency tarball in a directory
  named open-axiom-1.1.x.  Rename it to open-axiom-1.2.0, e.g.:

       mv open-axiom-1.1.x open-axiom-1.2.0

 2. Building OpenAxiom

  It is assumed you have already downloaded open-axiom source tarball,
  e.g. open-axiom-1.2.0.tar.bz2.  

  Note: If you don't have GCL or noweb in the build environment, please
  make sure that you have either followed the instructions in step 1.,
  or have separately installed them before proceeding.

 2.a. Decompress the OpenAxiom source tarball

      tar jfxv open-axiom-1.2.0.tar.bz2

 2.b. Configure OpenAxiom

  It is highly recommended that you build OpenAxiom in a directory
  different from the one that contains the sources.  For example, you
  may create a directory sibling to open-axiom-1.2.0 and build the
  system from there:

      mkdir build-oa
      cd build-oa
      ../open-axiom-1.2.0/configure

  It is possible to tell configure where to put the final OpenAxiom 
  executables.  By default, when you just type in configure like above,
  it will configure the system with prefix /usr/local.  You can instead
  say where you want it to be installed, let's say /banana/space.  You
  would then have typed

     ../open-axiom-1.2.0/configure --prefix=/banana/space

  This is recommended, especially if you already have a different software, 
  not OpenAxiom, the executable filename of which is also called `axiom'.
  That way, you don't confuse OpenAxiom's command `axiom', with any other
  program that you may have on your system.  Most users usually have only
  one software with a given name on their machines.  If you plan to 
  have many software sharing the same executable name, please make sure
  that you install them in distinct directories so that they don't conflict.

 2.c. Make the system

  Just type
       make
  or
       make 2>&1 | tee build.log
  if you would like to inspect the build messages later on -- but most
  users probably don't.

 2.d.  Have some coffee

 2.e.  Have more coffee

  It can take from 30min to 2 hours to build, depending on the
  compute power of the build machine.

3. Installing OpenAxiom   
   --------------------

 Once the build (step 2.) has gone successfully, you may optionally try
 to regress-test the system -- it can take hours.

3.a. [optional]

       make check 2>&1 | tee tests.log

3.b. The system is ready to install

 If you configured the system to install in a place that needs special
 privilege, e.g. /usr/local that requires administrator write, please
 make sure that you've gained the adequate privileges.  Then, type:

      make install

3.c. The system is ready for use

 After step 3.b., your should have a script called `open-axiom', in
 /usr/local/bin or /banana/space/bin or /whichever/prefix/you/used/bin,
 ready for use.

Building on Linux

Lisp and noweb prerequisites
If any of GCL or noweb is missing from the environment environment where you're building, then you need to either separately install them, or download the dependency tarball
open-axiom-1.1.x-dep.tar.bz2

Please, notice that GCL and noweb are needed only to build OpenAxiom?. If you plan to build OpenAxiom? often, then it probably is a good idea to separately build and install those tools once for all.

If you already have GCL and noweb installed, please go to step 2.
a. Download the dependency tarball open-axiom-1.1.x-dep.tar.bz2
b. Decompress the dependency tarball
tar jxfv open-axiom-1.1.x-dep.tar.bz2

That should decompress the dependency tarball in a directory named open-axiom-1.1.x. Rename it to open-axiom-1.2.0, e.g.:
mv open-axiom-1.1.x open-axiom-1.2.0
Building OpenAxiom?
It is assumed you have already downloaded open-axiom source tarball, e.g. open-axiom-1.2.0.tar.bz2.

Note: If you don't have GCL or noweb in the build environment, please make sure that you have either followed the instructions in step 1., or have separately installed them before proceeding.
a. Decompress the OpenAxiom? source tarball
tar jfxv open-axiom-1.2.0.tar.bz2
b. Configure OpenAxiom?
It is highly recommended that you build OpenAxiom? in a directory different from the one that contains the sources. For example, you may create a directory sibling to open-axiom-1.2.0 and build the system from there:
mkdir build-oa cd build-oa ../open-axiom-1.2.0/configure

It is possible to tell configure where to put the final OpenAxiom? executables. By default, when you just type in configure like above, it will configure the system with prefix /usr/local. You can instead say where you want it to be installed, let's say /banana/space. You would then have typed
../open-axiom-1.2.0/configure --prefix=/banana/space

This is recommended, especially if you already have a different software, not OpenAxiom?, the executable filename of which is also called `axiom'. That way, you don't confuse OpenAxiom?'s command `axiom', with any other program that you may have on your system. Most users usually have only one software with a given name on their machines. If you plan to have many software sharing the same executable name, please make sure that you install them in distinct directories so that they don't conflict.
c. Make the system
Just type make or make 2>&1 | tee build.log if you would like to inspect the build messages later on -- but most users probably don't.
d. Have some coffee
e. Have more coffee
It can take from 30min to 2 hours to build, depending on the compute power of the build machine.

Installing OpenAxiom? --------------------
Once the build (step 2.) has gone successfully, you may optionally try to regress-test the system -- it can take hours.
a. [optional]?
make check 2>&1 | tee tests.log
b. The system is ready to install
If you configured the system to install in a place that needs special privilege, e.g. /usr/local that requires administrator write, please make sure that you've gained the adequate privileges. Then, type:
make install
c. The system is ready for use
After step 3.b., your should have a script called `open-axiom', in /usr/local/bin or /banana/space/bin or /whichever/prefix/you/used/bin, ready for use.

Building on Windows

For how to prepare an MSYS/MinGW? system to build OpenAxiom? on Windows see: BuildOnWindows?

Download the source from the repository at:

svn co https://open-axiom.svn.sf.net/svnroot/open-axiom/trunk oa.trunk

The source is the same as one used to build on Unix or GNU/Linux.

Once you got it, please look at oa.trunk/INSTALL for requirements.

The native Windows binary is here

http://downloads.sourceforge.net/open-axiom/OpenAxiom-1.1.0.exe?modtime=1204184285&big_mirror=0

You can build it with just MSYS/MinGW?, as you would build it on a unix/linux platform

./configure && make && make install