The building is performed on a set of fetched and selected components and will produce a result set in a build destination catalog. Several build options exits and what can be build options are dependant on what has been fetched for the components that are currently in the selection.
This sections describes building without any assumptions on what you want to do. For tailored scenarios you can go directly to these
The build can be done in four different ways:
For details see Page: Create Build Structure And Compile
The components that you plan to build has to be already fetched and selected.
The way you plan to build has to match what has been fetched for the components.
To be able to compile Java and C#, IFS Base Functionality (Fndbas) must be included in the build or already built to the destination.
Normally all components should be included. You can
use Select All, Unselect All, Filter to speed up selection. Use click,
shift-click, or ctrl-click to make your selection.
If you select Filter the components to be built will be filtered
according to the loaded Customer Configuration File.
Normally all build options should be included. You can use Select All, Unselect All to speed up selection. Select manually the options that should be included.
English (US) will always be included, and cannot be excluded, except when building from LNG_Components. English (US) means that [component]_*-en.trs and [component]_*.lng files will be built into build destination. The Client column for each included language can be selected. When not selected, the specific language will not be generated for client runtime although the translations will be installed to the <build_home>. You can use Select All, Unselect All, Filter to speed up selection. Select the languages that should be included. If you select Filter the languages to be included and the Client language will be filtered according to the loaded Customer Configuration File.
If the script build.cmd is not available in the included components (fndbas/build) nor in the build destination (<build_home>\build) the selections will be disabled and values ignored in the build process.
ConfigBuilder will start the script that will in turn start the compilation scripts. If the compilations scripts are not available in build destination after the build, the script will prompt a message about missing script(s).
IFS Configuration Builder will now check that all component dependencies are fulfilled.
The structure created by the build operation in <build_home> e.g. <workspace>\build_home is described in Folder Structure for Builds.
How to perform compilations of sources manually is described in How to Compile Source Code