You are encouraged to read this document entirely before starting to play with the Buildtool package, as it contains several things you need to know beforehand.
Remember that you can get the latest Buildtool version, read the manual online and get free support from the official website:
COPYINGfile for more details on this topic.
If you have trouble during the process, the section SYSTEM SPECIFIC NOTES contains some tips that may help you.
This is the simplest use of this script, which will work most of the times. Although there are many user-configurable options that you can look at using the -h command-line switch. Probably, the most used flag is -p, which specifies the installation prefix. The script will also create several makefiles, ready to be parsed by make(1).
Generated makefiles should work with any make(1) flavour, as they do not use any kind of advanced features. Environment variables will not affect this step. If they contain incorrect values, you will need to set them in the environment and execute the configuration script again.
$ make install
And that's all! If you used a non-standard prefix you will want to setup your path accordingly. No other change is required in your environment, as Buildtool remembers where it was installed and calls its modules with full paths.
The first thing you must do to provide a good bug report is to take a log of all the process you did. To achieve this you can use the script(1) command; this utility starts a subshell where you can run commands (as you usually do), but all output is redirected to a log file.
As a summary, you should do something like this (note that output is removed for simplicity):
$ script build.log Script started, output file is build.log $ uname -a $ make cleandir $ ./configure -p /tmp/debug $ make $ make install $ exit Script done, output file is build.log
Once this is done, send me the
file, at the following email:
If you can add additional information to this log (that you think
can be useful to us), please do so.
When you are asked to select which packages you want to install, select (aside from the defaults): bzip2, cygutils, less, make and gcc.
$ buildtool -h
If you are an end-user, who only needs to use Buildtool to configure,
build and install third party programs, you will not need to learn
Start by reading the
file included in any Buildtoolized package.
All further instructions are included there, as well as some
If you are a developer interested in using Buildtool in your own
programs, you will need to learn and understand several concepts.
manpage provides a good starting point.
page contains all information available.
To start the testing process, launch the following command from the directory where you built Buildtool:
$ make test
Remember that you will probably need less than 10 minutes to read the file and do all the tests. But you will be helping us a lot by providing porting related information.
http://buildtool.sourceforge.net/mlists.htmlfor a list of available lists.