Index of /gled-1.2.3/distribution-tools
Name Last modified Size Description
Parent Directory -
build-config 2004-06-07 15:47 5.6K
wipe-top.sh 2004-06-07 11:26 242
make-top.sh 2004-06-06 15:20 1.4K
build.rc 2004-06-04 18:00 400
edit_build.eses 2003-11-19 14:56 1.2K
build.pl 2003-07-31 09:16 11K
pack.pl 2003-07-25 11:10 1.0K
clean-top.sh 2003-07-24 20:34 202
ParseConfig.pm 2003-07-23 19:50 4.3K
=======================
Gled Distribution Tools
=======================
Files in this directory serve for building distributions of Gled.
1. Preparing the structure
--------------------------
mkdir gled-rel-build # top-level directory for release build
cd gled-rel-build
cp -a <path-to-distribution-tools>/distribution-tools .
Edit distribution-tools/make-top.sh: you need to set the GLED_CVS_TAG
variable to the CVS release tag that you want to build and you can
modify the list of libsets and build/execution environments.
You MUST be in top-directory for the next command!
distribution-tools/make-top.sh
# hit <enter> for CVS password
This command does two things:
1) creates the expected directory structure
2) checks the whole Gled from the CVS and creates source tarballs
After that copy all required/external software tarballs that you want to build
from source into required_software/source, e.g.
cp <my-tarball-repo>/fltk-1.1.4-src.tar.gz required_software/source
Copy binary packages of ROOT to required_software/externally_built.
2. Configuring the builds
-------------------------
All build configuration is done by editing build.rc and build-config file.
In build.rc set the GLED_VERSION. This will be the version propagated
to the build of libsets and exported via toplevel config.h:
#define GLED_VERSION_STRING "<whatever you set GLED_VERSION to>"
build-config is slightly more complex. The most painful thing so far
is that you have to associate binary root distribution with each
specified build.
3. Building
-----------
For each build run
./build.pl --buildname=x86-rh9-gcc3.2 > log.x86-rh9-gcc3.2 2>&1
By defaul the meta-packages (tarballs composed from several tarball
components) are not created. These are better done at the file server
itself, and the command pack.pl does packing for all enumerated builds.
# ssh to fileserver or close to it ...
# cd to build directory
./pack.pl
4. Cleaning-up for deployment to ftp server
-------------------------------------------
./clean-top.sh
# rsync the build directory to ftp server