Oberon ||
Compiler & Tools ||
Library ||
Module Index ||
Search Engine
Ulm's Oberon System:
obbuild
NAME
obbuild - build a static Oberon executable
SYNOPSIS
obbuild
[-a
auth]
{-b
basedir}
[-l
loglevel]
[-o
output]
{module}
DESCRIPTION
obbuild takes the given list of modules as core,
adds the required runtime modules, loads the transitive closure
of it using obload, and combines the results to one
statically linked executable.
Please note that before any modules can be loaded, their
sources must have been uploaded to the compiler database (CDB)
using, for example, obci. Compilation options
are to be stored together with the sources during the upload
process to the database.
Following options are supported:
- -a auth
-
specifies a file containing a persistent object of type
Shards.Lid that is to be used for authorization.
By default, the authority file of the standard installation
of cdbd is taken.
- -b basedir
-
defines the base path of the compiler data base (CDB). Default is
/pub/cdb/oberon.
Note that any number of base paths may be given. Multiple base
paths are combined through TranslucentNames, i.e. results
are written into the last base path, and base paths specified later
on the command line take precedence over those given earlier.
- -i intensity
-
allows to set the intensity level for Storage.Intensity
(see Storage) of the obload process.
- -l loglevel
-
requests log information as generated via CompilerLogs to
be displayed. This is mainly useful to follow the recursive process
of building. A log level of 0 (default) suppresses any logs. Larger
log levels cause more output to generated.
- -o output
-
asks the generated executable to be stored into output.
SEE ALSO
- obci
-
check-in Oberon sources into the compiler database (CDB)
- obload
-
load results from the CDB or generate them
Edited by: borchert, last change: 2005/02/05, revision: 1.2, converted to HTML: 2005/02/05
Oberon ||
Compiler & Tools ||
Library ||
Module Index ||
Search Engine