Login | Register
My pages Projects Community openCollabNet

Buckminster Downloads

AMTOOL

Download the latest release from the Documents and Files section!
Until it's more stable it's being released as timestamped builds only using the name format tz_yymmdd_hhmm.

How to try it, building itself from the latest versions:

A prerequisite is that you must have a JDK 1.4 or above installed and pointed the JAVA_HOME variable to it.

The entry point is 'amtool.exe' on Win32 and 'amtool' (a Perl script) on Unix. On Win32 it should run with no extra work. On Unix, you need a basic Perl installed; you may have to adjust the 'shebang' line in the amtool script to point correctly. Also, you may have to run 'chmod a+x' on the script.

If you haven't already made a CVS login on tigris.org, you must do so now:

cvs -d :pserver:anoncvs@cvs.tigris.org:/cvs login
(use a blank password)
alternatively, you may want to use your own tigris login instead of 'anoncvs'.

Now you can create a workspace using one of the available configurations. In this sample, we'll use the 'amtool' configuration which is a good mix of source and some precompiled states, so called CSAR's. Currently, other possibilities include 'amtool-allsrc' and 'amtool-bin' which is only source and only precompiled states respectively.

<amtool-install-dir>/amtool mkws cvs:amtool

This command will use defaults and first create a directory called amtool.ws in your current directory, and will then populate it with components. Once it is complete, execute a build in the workspace:

<amtool-install-dir>/amtool build amtool.ws

By default, builds are silent unless a problem occurs. Thus, this sample isn't especially funny to look at. To see more detail, use the -loglevel option, for example like this:

<amtool-install-dir>/amtool build -clean -loglevel info amtool.ws

Some general notes:

All commands have help text, both the amtool command itself and any subcommands - use -h or -?.

To see the configurations, use the 'getcs' command:
amtool getcs cvs:amtool-allsrc

In case of problems, a very verbose log file is generated in $HOME/.amtool.log which will help in after-the-fact problem resolution. Can be configured through <amtool-install-dir>/conf/log4j.xml.