FAQ 757: How to Avoid or Control the Generation of the tl_defines_*.h File in TargetLink

Question

For most CGUs[1] (code generation unit) TargetLink generates a file named tl_defines_<Subsystem_ID>.h, which seems to contain equal or at least similar content for all CGUs.  

Although the C standard allows multiple equal macro definitions, some compilers (sometimes only with specific compiler settings) might issue an error or warning due to multiple definitions of certain macros in the different tl_defines_*.h files, when integrating/building several CGUs together.

Is it possible to control the generation of these files or combine them and generate it only once for all CGUs?
Or how can I avoid the generation of the tl_defines_*.h files?

 

[1] For details about CGUs see related FAQ 774 Module Ownership, Modules, Code Generation Units, Stub Code

Answer

Tags
Date 2021-12-02
产品 TargetLink
资料信息 常见问答
dSPACE 版本发布 2023-A, 2022-B, 2022-A, 2021-B, 2021-A, 2020-B, 2020-A, 2019-B, 2019-A, 2018-B, 2018-A, 2017-B , 2017-A, 2016-B, 2016-A, 2015-B, 2015-A, 2014-B, 2014-A, 2013-B, 2013-A, 2013-A之前版本

通过 dSPACE时事通讯服务了解最新信息。

通过 dSPACE 时事通讯服务,我们将随时向您通报当前的使用案例、新解决方案和产品以及培训和活动。在此注册,免费订阅。

Enable form call

At this point, an input form from Click Dimensions is integrated. This enables us to process your newsletter subscription. The form is currently hidden due to your privacy settings for our website.

External input form

By activating the input form, you consent to personal data being transmitted to Click Dimensions within the EU, in the USA, Canada or Australia. More on this in our privacy policy.