Clean, Build, Rebuild, Deploy

Managing Build Configurations

From FGL Project Explorer, you can access the options to manage your build configurations:

• Set active build configuration (from Project context menu);
• Add build configuration (from Project context menu);
• Add exclusions to build configuration (using the Manage Build Configuration Exclusions button at the program’s name);
• Delete build configuration (from Project context menu);
• Edit the configuration in .fgltarget file.

Options available from the Project context menu:

Options available on hovering over the program:

After you click the Edit Program File button, LVSCE will open the .fgltarget file, which will have code describing the exclusions:

 

Return to top

Adding a Build Configuration

Step 1. Right-click your project in the FGL Project Explorer and select the Add Build Configuration option:

Step 2. Name your new configuration and press ENTER:

In the lower-right corner of VS Code’s main window, LVSCE will notify you about successful configuration creation:

 

Return to top

Setting the Build Configuration as Active

Step 1. Call the Project context menu and select Set Active Configuration:

Step 2. LVSCE will show the dialog of configurations choice in the top of VS Code’s main window. In this dialog, select desired configuration:

Your chosen build configuration will be displayed in FGL Project Explorer in the same line with the project name:

 

Return to top

Adding Exclusions to the Build Configuration

Step 1. Hover over the program’s name and find the Manage Build Configuration Exclusions button next to it:

Step 2. Click the button. In the top of VS Code’s main window, LVSCE will offer to pick the configuration to edit:

Step 3. Select the configuration. Next, LVSCE will show the list of program’s files that you can exclude from chosen build configuration, with a search bar on top of it:

Step 4. Fill flags beside the files you want to exclude, or find your files using the search bar and mark them for exclusion:

Step 5. Click the OK button:

Excluded files will have the mark [exclusion] beside their names in FGL Project Explorer:

You can also add exclusions to any configuration without switching from active configuration to the edited one. For example, we are going to exclude a file from newconfig1. We have found the file we need to exclude in FGL Project Explorer, and now we click the Manage Build Configuration Exclusions button:

Then, in dialog in the top of VS Code’s main window, we select the configuration to edit:

Next, we check the file using checkbox, and click OK:

As buildconfig_3 remains the active configuration, FGL Project Explorer will display the [exclusion] mark for 01_04_dt_record.4gl file:

Let’s switch to newconfig1. To do that, we right-click the project and select the Set Active Build Configuration option:

Then, in dialog in the top of VS Code’s main window, we select the newconfig1 build configuration:

After that, newconfig1 is displayed as active beside the project name, and the file 01_08_for_loop.4gl has a mark of exclusion:

 

Return to top

Deleting a Build Configuration

Step 1. Right-click your project in FGL Project Explorer and select the Delete Build Configuration option:

LVSCE will show a search bar and a list of configurations to choose from in the top of VS Code’s main window:

Step 2. Select the configuration(s) to delete, and click OK:

LVSCE will notify you that chosen configuration(s) has (have) been deleted:

 

Return to top

Clean, Build, Rebuild, Deploy Programs

With FGL Project Explorer, you can clean, build, rebuild and deploy your programs:

 

Return to top

Cleaning a Program

Right-click the program and select Clean:

The output files of this program’s build will be purged from the output folder. Files not related to it will stay untouched. The Terminal tab of VS Code will display the progress:

 

Return to top

Building a Program

Right-click the program and select Build:

Non-built program – or the one that has been edited since the latest build – doesn’t have any signs on its icon in FGL Project Explorer. At successful build, the program will receive a green check mark sign; at failed build, it will have a red cross sign. You can see it on the screenshot below, top to bottom: successfully built program, program with build failure, non-built / modified program:

If the program has errors and failed to build, you will also receive the following indicators:

• in FGL Project Explorer, the failed-to-build program will have a number of errors near its name, as well as in Workspace Explorer and Editor;
• the file with errors will be marked with red colour in program resources:



• in Terminal tab of the Panel, LVSCE will display the progress and failed status of the build task, the path to the file that has errors, exact location of the errors, and a tip about how to fix them;
• in the message in lower-right corner of VS Code’s main window, the task will be displayed as failed;
• in the Problems tab of the Panel, you will see short reports about the errors:

From this tab, you can quickly get to the error(s) in code. To do that, click the line with message of the error. VS Code will open the file and highlight the exact line that has that error:

 

Return to top

Building a Program Containing the IMPORT FGL Statement

Building the program containing IMPORT FGL has the following steps:

Step 1. Build the program or library to receive .4o and .4a files that this statement will use.

Step 2. Place the .4a and .4o files into the location where compiler will search for these files. They are:

• Project's output folder;

• Custom locations, specified with FGLLDPATH variable;

• Project’s source folder;

• Project’s root folder (if the project doesn’t use output and source folders).

Output and source folders are indicated in the .fglproject file:

See details about FGL IMPORT algorithms on the following page: Algorithms used by IMPORT FGL.

Step 3. Build the program that has the IMPORT FGL statement.

 

Return to top

Rebuilding a Program

If you made changes after the previous build, you will need to rebuild your program by right-clicking it and selecting the Rebuild option:

The Terminal tab of the Panel will notify you of the progress of the task:

If there are no errors, the program will be successfully rebuilt and will have a green check mark sign on it:

If the program has errors and failed to rebuild, you will also receive the following indicators:

• in FGL Project Explorer, the failed-to-rebuild program will have a number of errors near its name, as well as in Workspace Explorer;
• the file with errors will be marked with red colour in program resources:



• in Terminal tab of the Panel, LVSCE will display the failed status of the rebuild task, the path to the file that has errors, the exact location of the errors, and a tip about how to fix them;
• in the message in lower-right corner of VS Code’s main window, the task will be displayed as failed;
• in the Problems tab of the Panel, you will see short reports about the errors:

From this tab, you can quickly get to the error(s) in code. To do that, click the line with message of the error. VS Code will open the file and highlight the exact line that has that error:

 

Return to top

Deploying a Program

With no errors in the code and a successful build, you can right-click the program again and select Deploy:

That action will deploy the program:

 

Return to top

Deploying to a Custom Folder

Additionally, you can select a custom deployment folder for the program. To do that, proceed as follows:

Step 1. Right-click the program, and select the Set Custom Deployment Folder option:

Step 2. In the dialog that appears, select the folder to deploy the application to, and press ENTER.

 

Return to top

Deploying a Program Containing the IMPORT FGL Statement

.4o and .4a files must be deployed to the application server along with the program that imports them, as these files will be linked dynamically at runtime on application start.

See details about FGL IMPORT algorithms on the following page: Algorithms used by IMPORT FGL.

 

Return to top

Clean, Build, Rebuild, Deploy Projects

FGL Project Explorer also provides the possibility to clean, build, rebuild, deploy entire projects:

 

Return to top

Cleaning a Project

Right-click the project and select Clean Project:

The output files of this project’s build will be purged from the output folder. Files not related to it will stay untouched.

 

Return to top

Building a Project

Right-click the project and select Build Project:

All the programs in the project will be built, the Terminal tab of the Panel will display the progress of the building. Successfully built programs will have green check mark signs on them, the failed-to-build programs will have red cross signs. For example, successfully built project will look like this:

If even one program of the project fails to build, the project’s icon will have a red cross sign as well as the program with build error:

Example of successful project build results in Terminal:

Example of failed project build results:

• the file(s) with errors will be marked with red colour in program resources:



• in Terminal tab of the Panel, LVSCE will display the progress and the failed status of the project build task, the path to the file(s) that has (have) errors, the exact location of the errors, and tips about how to fix them;
• in the message in lower-right corner of VS Code’s main window, the task will be displayed as failed;
• in the Problems tab of the Panel, you will see short reports about the errors:

Click the error, and VS Code will open the file that contains that error and guide you to the exact line with highlighting it:

 

Return to top

Rebuilding a Project

After you’ve made changes to your project, right-click the project and select Rebuild Project:

All the programs in the project will be rebuilt. Successfully rebuilt programs will have green check mark signs on them, the failed-to-rebuild programs will have red cross signs. For example, successfully rebuilt project will look like this:

Also, if even one program of the project fails to rebuild, the project’s icon will have a red cross sign as well:

Example of successful project rebuild results:

Example of failed project rebuild results:

• the file with errors will be marked with red colour in program resources:

• in Terminal tab of the Panel, LVSCE will display the failed status of the project rebuild task, the path to the file(s) that has (have) errors, the exact location of the errors, and a tip about how to fix them;
• in the message in lower-right corner of VS Code’s main window, the task will be displayed as failed;
• in the Problems tab of the Panel, you will see short reports about the errors:

Click the error, and VS Code will open the file that contains that error and guide you to the exact line with highlighting it:

 

Return to top

Deploying a Project

With a successful build, right-click the project and select Deploy Project:

The programs of the selected project will be deployed.

 

Return to top

 

See next: Run