1. Source Code Licensing
2. Building from a source distribution.
A. Building under *nix, MSYS or CygWin.
B. Building under Windows.
C. Building under MacOSX.
3. Building from the CVS/Subversion tree
1. Source Code Licensing
========================
BuildSys is now being distributed under the GPL 2.0 or greater license.
Source code found under the src/contrib directory does not originate from the
BuildSys project. As such, source code found under this directory does not
fall under the BuildSys project's license. Details about licensing for the
source code under this directory can be found in the project directories and
within the src/contrib/README document.
2. Building from a source distribution.
=======================================
You should have downloaded or otherwise received a file by the name of
buildsys-X.Y.tar.gz or buildsys-X.Y.zip. This file contains all the source
code and build scripts needed to create the buildsys executble.
A. Building under *nix, MSYS or CygWin
--------------------------------------
With any luck a simple
./configure; gmake; gmake install
will work for you. Note that you have to use gmake on systems like
FreeBSD, or else you will get some errors about not being able
to change into the obj directory...
B. Building under Windows
-------------------------
Once you have unziped the source, you should be able to find the file
build/Dev-C++/buildsys.dev
Open this using dev-c++, which can be found at (don't worry, its free)
http://www.bloodshed.net/devcpp.html
You should be then able to simply hit Ctrl-F9, or go to the Execute->Compile
toolbar option to build the buildsys exectuable. (Note: version 5.0 beta or
higher is required to build buildsys)
To build the installer executable, install the Nullsoft installer software
(which is also free), found at
within the unziped folder. Inside this directory is a 'Dev-C++' directory.
Within this directory
C. Building under MacOSX
------------------------
For now, folow the directions in section A. You should end up with a
command line executable. Hopefully eventually someone familiar with
MacOSX shell integration will come along and help build us an installer
and such.
3. Building from the CVS/Subversion tree
========================================
There is only one additional step to building from the cvs/svn repository:
run autoreconf --force --install.
Then you can go on with the usual ./configure;make;make install