Build project without the -mcpu option

The -mcpu selection may, in some scenarios, interfere with other toolchain options. For example, building certified libraries requires a specific compliant toolchain configuration. The newest device types may not be supported by a legacy compiler, even if the core architecture is.

In these cases, it possible to build the project without implicitly providing the target derivative specific option (-mcpu) on the command line.

You can set this option under the Global options of the Project  Properties  C/C++ Build  Settings  Tool Settings. When the Do not use -mcpu option on command line option is enabled, the IDE does not put the -mcpu option into the build command.

Note, bypassing the -mcpu option leads to a failed build or other unexpected results in general. It is up to the user to manually supply additional configuration data, such as core architecture (-mtc), based on its target goal.

By default, the IDE sets the language provider based on the CPU type selection. When you enable the Do not use -mcpu option option, the IDE chooses the language provider according to the TriCore core architecture option (-mtc). This does not affect the build process or the product, but it may cause built-in toolchain symbols being incorrectly decorated in the source code editor if mismatched.

See the mapping table below.