GBS Logo HOME Generic Build Support (GBS) - User Manual
Handling SubSystems & Steps Bottom Doc. Button

Description Bottom Doc. Button Top Document Button Down Section Button Blank

SubSystems Bottom Doc. Button Top Document Button Down Section Button Blank Down Chapter Button Blank

GBS recognises a number of SubSystem types that can be either Full GBS or Non-Full GBS.
In general:

MSVS SubSystem

You should create/copy your main project of solution file directly in the 'app' directory.
You will already have a subsys.gbs.bat file appropriate for MSVS, with lots of comments.
Run 'gbsedit subsys.gbs' to change to the wanted functionality.

make SubSystem

You should create/copy your 'make' code tree directly in the 'app' directory.
Your main 'make' file should be either in the SubSystem directory or the 'app' directory.
You will already have a subsys.gbs.bat|.sh file appropriate for 'make', with lots of comments.
Run 'gbsedit subsys.gbs' to change to the wanted functionality.

Other SubSystem

You should create/copy your code tree directly in the 'app' directory.
You will already have a generic subsys.gbs.bat|.sh file, with lots of comments.
Run 'gbsedit subsys.gbs' to change to the wanted functionality.

Steps Bottom Doc. Button Top Document Button Blank Blank Blank Up Chapter Button

By default SubSystems are handled (gen, make, audit) in Alphabetical order.
With the definition of Steps in steps.gbs this order can be changed.
It is also possible to make selections of SubSystems optional in various ways.
It is also possible to define non-SubSystem steps, called 'Commands' that will allow you to execute commands to e.g.:
Copy end-results to a specific directory outside then GBS tree, run Doxygen on the whole GBS tree, etc

More information in steps.gbs.
subsystems.html