Build Setup Dialog

Help index

Building via the CVS Repository

The standard procedure (at exept) is to use the CVS repository for building deployable products. This is usually done by:
  1. creating a fresh working directory on a machine
  2. 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.
  3. 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.

Building without Repository (Local 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.

Choosing a Compiler

Under unix/linux, the standard gnu compiler (gcc) is used for building.

On windows, you have the choice of:


Copyright © eXept Software AG, all rights reserved


Doc $Revision: 1.3 $ $Date: 2012/03/01 13:05:08 $