Build configurations
Build configuration is a list of files which will be built among all the files included in a particular project.
Once created, every project has one - default - build configuration that includes all the files of this project:
Whoever, you may create several build configurations of one project so as to build different sets of files.
Why would you need to have several built configurations?
One simple example.
The software you develop is a project of several 4gl programs. You want to change one of these programs to update the functionality of your software.
Instead of duplicating your project in order to change one single source file - v0.4gl, - you
- create a new version of the necessary file - v1.4gl,
- create a new build configuration - test_v1,
- in default build configuration, you add v0.4gl and exclude v1.4gl,
- in text_v1 build configuration, you add v1.4gl and exclude v0.4gl.
After this, when you build the default build configuration, you will see how your software behaves with the original version of the program.
And when you build the test_v1 build configuration, you will see how your software behaves with the new version of the program.
Adding and removing build configurations
You can view, select, add, and remove the existing build configurations in the properties of your project:
To create a new build configuration, please follow these steps.
Step 2. In this tab, press Add... to create a new build configuration.
You will get the New Build Configuration window with the suggested name for your new configuration - config:
Step 6. After you press OK, your new configuration is selected and you can edit it and build the project.
All the non-default build configurations, are listed in the .fglproject file of the project:
...
<item id="com.querix.fgl.core.buildconfigurations">
<buildConfiguration active="true" name="test_radio"/>
</item>
...
To remove a non-default build configuration, please follow these steps.
Step 3. This selected build configuration is deleted.
Adding and excluding files from the build configuration
You can add and exclude files from non-default build configurations according to your development needs.
Thus, there are three state a file can have as regards any non-default build configuration:
- <default> - the file existed when the configuration was created;
- [addition] - the file was absent when the configuration was created and was added to it later; and
- [excluded] - the file existed when the configuration was created and was excluded from it later.
All the files added or excluded from the non-default build configuration, are listed in the .fgltarget file of the program:
...
<buildConfiguration name="test_radio">
<additions>
<sources type="fgl">
<file location="radio_v1.4gl"/>
</sources>
</additions>
<exclusions>
<sources type="fgl">
<file outputLocation="" location="radio_v0.4gl"/>
</sources>
</exclusions>
</buildConfiguration>
...
Adding files to the build configuration
To add an existing file to a build configuration, please follow these steps.
Step 2. In the opened window, select the
file and check out Add to build configuration <configuration name> only.
You can also create a totally new file and add it the non-default configuration:
Step 1. Create a new source file as described here (Steps 1-2).
Excluding files from the build configuration
How to exclude a file from a build configuration depends on whether this build configuration is a default or non-default one.
There are two ways to exclude a file that exists in both default and non-default build configurations:
-
in the properties of this file:
-
by selecting Delete in the file's context menu (or pressing Delete on your keyboard) and checking out Remove (exclude) build configuration <configuration name> only:
To exclude a file that exists only in a non-default build configuration, select Delete in its context menu or press Delete on your keyboard. In the opened message window, press Yes:
Do not check out the checkbox, Also delete source file <> from the file system.
If you do, you will lose this file because it will be deleted.
All the excluded files can be brought back to the build configuration.
To do this, select Unexclude in the context menu of the file:
