Online builds 10-apr-2013
From GlueXWiki
File structure for release area
Simple but cluttered:
-- builds `-- devel |-- aPackage |-- anotherPackage |-- cMsg2et | |-- doc | |-- java | `-- org | `-- jlab | `-- halld | |-- jar | |-- Linux_RHEL6-x86_64-gcc4.8.0 | | |-- bin | | |-- include | | |-- lib | | `-- scripts | `-- src | |-- binsrc | |-- examples | |-- libsrc | | `-- cMsg2et -> . | |-- scripts | `-- test |-- doc |-- jar |-- Linux_RHEL6-x86_64-gcc4.8.0 | |-- bin | |-- include | |-- lib | `-- scripts `-- SCONS
Build System
- Based on SCONS and Python/Perl scripts (by Maurizio, Elliott and Dave L).
- Assumes only one library per package, but allows multiple executables and test programs.
- Builds libsrc,binsrc and installs libsrc,binsrc,scripts into $INSTALL_DIR (default is package directory).
- Copies include files from libsrc into include directory in $INSTALL_DIR.
- Builds test area but only installs it locally (i.e. ignores INSTALL_DIR env var)
- Ignores any other directories in src (e.g. examples dir).
- Include statements MUST be qualified by package name (e.g. #include <cMsg2et/cMsg2et.h>) (thus the soft link in libsrc dir).
File structure for release area
- Below is a proposed release directory structure.
- Release area only writeable from hdsys account, read-only from all other accounts.
- Package directories are what gets checked into SVN.
- Packages can be checked in/out by anyone.
- Anyone can build and install packages locally.
- Only hdsys can release a package.
- Notes:
- Should SCONS dir be under packages? Should it be installed?
-- builds `-- devel |-- doc |-- jar |-- Linux_RHEL6-x86_64-gcc4.8.0 | |-- bin | |-- include | |-- lib | `-- scripts |-- packages | |-- aPackage | |-- anotherPackage | `-- cMsg2et | |-- doc | |-- java | `-- org | `-- jlab | `-- halld | |-- jar | |-- Linux_RHEL6-x86_64-gcc4.8.0 | | |-- bin | | |-- include | | |-- lib | | `-- scripts | `-- src | |-- binsrc | |-- examples | |-- libsrc | | `-- cMsg2et -> . | |-- scripts | `-- test `-- SCONS