Execution only by commands gbssysbuild,
gbssysmake and
gbssysaudit.
Execution is controlled by the subsys.gbs script files in the SubSystem directory
There is a vast amount of EnvVars that are set before execution of subsys.gbs.bat|.sh to be able to
achieve the required functionality. E.g.: Generate for Debug or Release, etc.
More information on the subsys.gbs file, including an example can he found in subsys.gbs.
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
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