Codegeneration of a harness model with multiple referenced models using a library block/chart with exported functions causes build error function is already defined

Question

Karel Viaene 2022-2-28

0
链接

此问题的直接链接

https://ww2.mathworks.cn/matlabcentral/answers/1660340-codegeneration-of-a-harness-model-with-multiple-referenced-models-using-a-library-block-chart-with-e

编辑： Infinite_king 2024-3-28

Screenshot 2022-02-28 155939.jpg

Hello,

I have a model which contains 2 different referenced models. Both models refer to a library block/chart which has a graphical function on its top level. The graphical function is exported ('Export chart level functions'), but not globally visible.

When generating code with GRT, codegeneration is succesfull, but the build fails. It mentions the exported function is already defined in the other model, which is true.

I would have expected because both models are in a harness, it would assign unique names to the exported functions, like it actually did to the header and source files. (ALM_Chk and ALM_Col).

How can I make sure there is a unique name generated for the exported functions in each referenced model to avoid a conflict during buildig?

Thank you in advance!

Kr,

Brecht

0 个评论
显示 -2更早的评论隐藏 -2更早的评论

请先登录，再进行评论。

请先登录，再回答此问题。

Answer 1

Infinite_king 2024-3-26

编辑：Infinite_king 2024-3-28

Hi Karel Viaene,

I understand that your model is referencing 2 other models which uses the same library block. When attempting to generate the executable, the code is successfully generated but the project fails to build.

I suggest you follow the troubleshooting steps below:

Verify if the model is properly configured for code generation.
Review the limitations of code generation for referenced models at, https://www.mathworks.com/help/rtw/ug/code-generation-limitations-for-model-reference.html
Check the code generation parameters in the configuration. You can access the code generation settings through the 'C Code' tab.
Create 2 subsystems from which you can reference the models.
If the issue persists, consider contacting MathWorks technical support at https://www.mathworks.com/support/contact_us.html