The following requires that you are familiar with CVS - if not then look at Cyclic's pages on CVS or the excellent information provided by Pascal.Molli.
On Unix you MUST have the following GNU tools installed in order to continue. Check that you have the following programs with the correct version number:
Makefile.in's which are used by autoconfMakefile's which are
used by makeCVS allows you to use the very latest version of Amaya - as soon as a fix or a new feature is commited to the CVS repository then you can update your working version and you will have it right away.
The purpose of "releases" is to say that now we believe that the code is stable with a well defined set of features. Until now, we have been giving out distribution files every time we announced a release. This will not change, but you can use the CVS repository in exactly the same way - often with much less overhead than dealing with a distribution package.
Starting from release 2.1, every release is marked in the CVS repository
using tags, so that it is possible to retrieve a complete release using the
CVS -r option (note that -r is "sticky"). Check out
the online CVS log walker for
the current set of release tags.
To be able to compile Amaya, you will need to check out not only Amaya, but also libwww, from the W3C CVS server.
Anonymous checkout is read-only access which allows you to get the latest edits and to provide patches to be integrated into the code base. The instructions should work for both Unix and Windows. A couple of notes:
Admin/Preferences/WinCVS in WinCVSStart by login as follows:
% cvs -d :pserver:anonymous@dev.w3.org:/sources/public login
after which you type "anonymous" as password.
To get the latest version from the CVS repository, run this command:
% cvs -d :pserver:anonymous@dev.w3.org:/sources/public -z3 checkout Amaya
libwww is an evolving piece of code. We use the Amaya tag to
identify the current version being used by the Amaya team. To download this
version, run this command:
% cvs -d :pserver:anonymous@dev.w3.org:/sources/public -z3 checkout -rAmaya libwww
If you want to try the bleeding edge libwww, just remove the Amaya tag as follows:
% cvs -d :pserver:anonymous@dev.w3.org:/sources/public -z3 checkout libwww
After which you will get all the code coming at you. Now you are ready to getting boot strapped.
If you want to get a specific release using CVS tags then you can do this by using the the CVS "-r" option, for example
% cvs -d :pserver:anonymous@dev.w3.org:/sources/public -z3 -r Release-2-1 checkout Amaya
Check the CVS log walker for the current set of release tags. If you at some point want to revert to the latest untagged version then you should use the following command:
% cd Amaya % cvs -z3 update -A
The big advantage of using CVS is that you easily can keep your version of the code base up to date with the latest edits and changes committed to CVS.
Once you have checked out the amaya and libwww CVS trees (not a specific revision), you can get any updates committed to the tree by using the cvs update command like this
% cd libwww % cvs -z3 update -d % cd ../Amaya % cvs -z3 update -d % cd ..
It is important that you use the "-d" flag so that you get new directories as well as updated files. Now you MUST repeat the compilation bootstrapping procedure.
When compiling directly from the CVS repository there are a few steps you have to go through which are already done if compiling from a distribution package. Follow these three steps:
On both Windows and Unix you can generate the *.h files and the *.def files by running a Perl script provided by Eric Prud'hommeaux. Never mind that it gives a few warnings when it runs - they are all OK. It requires that you have a recent version of Perl on your machine. Run the script like this (note the explicit use of the perl interpreter):
% cd libwww % perl config/winConfigure.pl
Windows people are now done and can jump directly to the instructions for how to compile Amaya. On Unix, you need two additional steps.
Now generate the make files as follows - don't worry about the warnings produced by autoconf:
% aclocal; autoheader; automake; autoconf
Now you MUST run the configure script as described in the next section on installation instructions. If for some reason you have trouble running the configure script then try and run this command instead
% make distclean; aclocal; autoheader; automake; autoconf
It'l be done automatically when you'll compile Amaya.
Remember to subscribe to the <www-amaya@w3.org> mailing list (archives) for information of new features as well as discussions of problems and ideas.
Congratulations - you are now ready to configure and compile Amaya!