Build Node (Project Properties)

The following options are available in the Build node:

Target

Determines the experimental or microcontroller target. The choices available here depend on the ASCET products you have installed: The ASCET base system provides the PC target and the Prototyping target, ASCET‑RP adds the experimental targets, ASCET‑SE adds the ANSI-C target, the EHOOKS target and various microcontroller targets, depending on the selections made during ASCET‑SE installation.

Note
To use the RTPRO-PC target, you must also use an external INTECRIO V4.7.2 or lower as hardware configurator; see Selecting an External Hardware Configurator.

Edit Target Settings

This link opens the ASCET options window in the appropriate <target>\Build subnode of the Targets node. Use the <target> hierarchy to set target-specific options.

Code Generator

Determines what kind of arithmetic is used in the generated code. Available options are:

Physical Experiment (floating-point arithmetic)
Quantized Physical Experiment (quantized floating point arithmetic)
Implementation Experiment (fixed-point arithmetic)
For ASCET‑SE targets, the following options are available:
Object Based Controller Implementation
Object Based Controller Physical

Edit Code Generation Settings

This link opens the Experiment Code node (for experimental targets and the PC and Prototyping targets) or Production Code node (for microcontroller targets, the ANSI-C target, and the EHOOKS target).

Compiler

Determines the compiler used to generate the code for the project. The list offers all compilers that can be used with the selected target.

The ASCET base system provides connections to the Closed following compilers.

Note
Only the MinGW GNU compiler is provided with ASCET.

Edit Compiler Settings

This link opens the ASCET options window. In that window, use the appropriate subnode of the Compiler node to set the compiler path.

Note
For the EHOOKS target, no compiler can be selected. However, you can edit some options in the EHOOKS subnode of the Compiler node in the ASCET options window.

Operating System

Determines the operating system of the current target. The available selections depend on the selected target.

Operating System	Target
Operating System	PC, Prototyping	ES910, RTPRO-PC	ANSI-C	microcontroller targets
GENERIC	x
RTA-OSEK V5.0		x		x
GENERIC-OSEK			x	x
RTE-AUTOSAR 4.0.2			x
RTE-AUTOSAR 4.0.3			x
RTE-AUTOSAR 4.2.2			x
RTE-AUTOSAR 4.3.0			x
RTE-AUTOSAR 4.3.1			x

Note
To work with RTPRO-PC, you must also use an external INTECRIO V4.7.2 or lower as hardware configurator; see Selecting an External Hardware Configurator.

Edit OS Configuration

This link opens the OS Configuration node of the ASCET options window.

Note
For the EHOOKS target, no operating system can be selected. However, you can edit some options in the OS Configuration node.

Generate Dependency Files

Switches the generation of make files containing the dependencies of all generated header files on (activated) or off (deactivated, default). Header files included by the user via #include statements are not taken into account. A make file is created for each generated *.c file.

Header/C Code Structure

Controls the header and C code file generation when you file out generated code. The C code and header structure created during code generation is not affected by this option.

The following selections are available:

Component

A separate header file is created for each class and each module in the project. If a module contains a class, the header information of the class is inserted in the module header file.

If a class is included in several modules of the project, its header information is inserted in all module header files.

A separate C code file is created for each component.

Project

A single header file is created for the entire project; its name is derived from the project. This file contains all information from the modules and classes in the project; it is included in all *.c files created for the components.

A separate C code file is created for each component.

Project Header

and Source

A single header file is created for the entire project. This file contains all information from the modules and classes in the project.

A single C code file is created for all generated components. External C code and header code of C components is written to separate files, to avoid interference with the generated code.

The names of the C file and the header file are derived from the project name.

Project Header

and Source+External C Code

A single header file is created for the entire project. This file contains all information from the modules and classes in the project, and also external header code.

A single C code file is created for all generated components. In addition, it contains any external C code from C components.

The names of the C file and the header file are derived from the project name.

Note
Unless "Header/C Code Structure" is set to Project Header and Source+External C Code, headers and C code files of external C code classes and of the OS component are not affected by this option (exception: use header global is activated for an external C code class).

Banner Templates for C Files

A semicolon-separated list of banner templates that are placed at the beginning of each generated *.c file. The file names may contain the following macros:

%ASCET%	product installation directory
%DATA%	data directory
%TARGETROOT%	target root directory (%ASCET%\target)
%P_TARGET%	target directory (e.g., %ASCET%\target\trg_ansi)

For a list of macros that can be used in the banner template file, see Banners in the Generated Code.

Banner Templates for H Files

A semicolon-separated list of banner templates that are placed at the beginning of each generated *.h file. The macros in the banner file names and in the banner files are the same as for the C banners.

Configure Code Generation Messages

This link opens the CodeGen message Configuration window. In that window, you can configure the messages from code generation and build process. For a detailed description, see Configuring Messages in the CodeGen Message Configuration Window.