Build configurations

This section describes the default build configurations generated for each project type supported by the project creation wizard.

S32V234 Cortex-A53 APEX2 Linux projects

The following table lists all build configurations available for projects with the APEX2 image cognition processor support.

Table 1. Default build configurations for S32V234 Cortex-A53 APEX2 Linux projects
Configuration	Description
A53	This configuration is intended for building a host-side application on a Linux target. This build configuration uses the ARM Linux 64-bit Target Binary Toolchain and the source files from the A53_gen and A53_src folders. These files are placeholders for user code.
APU	This configuration is intended to build the APEX2 code, resolve the process description, and produce the final ACF outputs needed for the host-side execution. This build configuration uses the Standard S32DS toolchain for APU targets.
TEST_A53	This version of the A53 configuration is intended for use during the development and testing stages and uses the source files from the A53_test folder generated by the Visual Graph Tools.
EMU	This configuration is intended for building a host-side application to be run in the emulation mode. This build configuration uses the APEX2 development libraries to emulate the behaviour of the APEX2 image cognition processor on the source code level. The library consists of two parts: APU-C language syntax library brings the vector types and instructions present in APU-C to standard C/C++. ACF emulation library emulates the ACF kernel, graph and process functionality. To learn more about the APEX2 emulation library, refer to the APEX-2 emulation library user guide located in the <install_path>/S32DS/software/VSDK_S32V2_RTM_1_3_0/s32v234_sdk/docs/apex folder. This build configuration uses the MinGW compiler for Windows and GCC 4.9.3 for Linux. Rebuild the APEX2 libraries to use them with a different version of GCC.
TEST_EMU	This version of the EMU configuration is intended for use during the development and testing stages and uses the source files from the A53_test folder generated by the Visual Graph Tools.

Note: The following dependencies exist between the above configurations:

The A53 configuration creates the final output artifact and depends on the APU build configuration output.
The APU configuration uses output from the ACF builder.
The ACF builder uses graphs directory as the source directory.

S32V234 Cortex-A53 ISP Linux projects

The following table lists all build configurations available for projects with the ISP coprocessor support.

Table 2. Default build configurations for S32V234 Cortex-A53 ISP Linux projects
Configuration	Description
A53	This configuration is intended for building an application to be executed on embedded Linux.
ISP	This build configuration uses the Standard S32DS toolchain for ISP to support Vision Sequencer (VSEQ).

Note: The “A53” configuration creates the final output artifact and depends on the “ISP” build configuration output.

S32V234 Cortex-A53 APEX2&ISP Linux projects

The following table lists all build configurations available for projects supporting both APEX2 and ISP.

Table 3. Default build configurations for S32V234 Cortex-A53 APEX2&ISP Linux projects
Configuration	Description
A53	See above.
APU	See above.
ISP	See above.
TEST_A53	See above.

Note: The information about build configuration dependencies can be found on the References tab of the project properties (Project properties > C/C++ General > Path and Symbols > References).