Build Setup Dialog
The standard procedure (at exept) is to use the CVS repository for building
deployable products. This is usually done by:
- creating a fresh working directory on a machine
- checking out (a potentially tagged) repository state there.
This includes both a definite version of the stx base system and a version
of the application to be built. Normally, the application is to be built in a diretory
beside the stx top directory.
- perform a build there.
On windows, this creates a self-installable setup executable (NSS) in the applications
project directory. On unix, an app-package is generated.
Of course, all of this can be automated, as there is no smalltalk image or browser interaction
required. Everything is controlled by makefiles.
The recommended way for automation is via a jenkins or expeccoNET scheduled build.
For a local build, no repository is used. Instead, all files are generated in a
temporary build directory (sources, makefiles and support files).
Then, a normal make-controlled build is executed there.
Under unix/linux, the standard gnu compiler (gcc) is used for building.
On windows, you have the choice of:
- bcc32 - Borland cc
the free borland compiler from the command line tools.
- vc - Visual c (Microsoft)
either the (Micrososft Visual C Express- or full version) or
non-free version. Only the command line tools are needed.
- lcc - lcc
not yet fully supported
- gcc - gnu compiler (Cygwin)
using the Cygwin tool chain (not yet fully supported)
Copyright © eXept Software AG, all rights reserved
Doc $Revision: 1.3 $ $Date: 2012/03/01 13:05:08 $