Description

Archiving Object-files to Libraries

The glb extensions are used to build libraries from object files.
For each library to be built there must be a glb-file in the source-directory, specifying the files to be included in the library.
The name of the library will be equal to the prefix of the glb-file, suffixed with the proper extension.
    (e.q.: total.glb → total.lib)
'glb' Stands for GBS librarian

Specifying a file to be of the glb type tells GBS that the output files will be eligible for the -L statement while linking.
Description of the glb files can be found here.

Linking Object-files and Libraries to Executables

The .glk extensions are used to build executables from object files and libraries.
For each executable to be built there must be a glk-file in the source-directory, specifying the files/libraries of the link.
The name of the executable will be equal to the prefix of the glk-file, suffixed with the proper extension.
    (e.q.: total.glk → total.exe)
'glk' Stands for GBS linker

Specifying a file to be of the glk type tells GBS that -L statement will cause searching for libraries as generated by glb.
Description of the glk files can be found here.

Testing Executables

The .glt extensions are used to test executables.
For each executable to be tested there must be a glt-file in the source-directory, specifying the executable and its parameters.
The output of the test (the log) will go to the build-directory. The name of the logfile will be equal to the prefix of the glt-file, suffixed with .log.
    (e.q.: total.glt → total.log)
'glt' Stands for GBS link test

Specifying a file to be of the GLT type tells GBS that there may be special GLT directives in the GLT file.
GLT directives must be specified at the top of the file, prefixed with '^',
followed by the executable-spec on a single line,
followed by the parameters, each on a single line.

GLT directives

• ^timeout=seconds
  The default is 60 seconds.
  Note that at timeout the program being tested will be killed and output buffers will not be flushed.
  It is the programmer's responsibility to set something like autoflush for STDOUT and STDERR in the test program.

• In addition to the build-line selection, Build exclusion can also be achieved via the .builds keyword in the glt file