Handle the external reference in the DLL generation TLC files

16 次查看（过去 30 天）
grapevine
grapevine 2013-1-3
Hello everyone,
I would like to have your opinions about how to solve this issue :
I made some libraries, which involve in several blocks, these ones are basically some sfunctions, which make calls to several external libraries (.lib file).
These libraries are going to be used by other folks to create some simulink models, which will be "transformed' in a DLL, by using Real-Time Workshop (former Simulink Coder) to perform several tests on a external device.
In order to compile the simulink model I have to link the external library used by the block of the library, by adding the name of the library to the compiling instructions of RTW I usually did that with this instruction
set_param(gcs,'CustomLibrary','P3_System_2.lib'
My advisor asks me to simplify the use of the libraries to the other team. He would like when someone adds a block to a model, the external library that is used by the block, will be automatically add to the options of Real-Time Workshop. My solution was to add this instruction
set_param(gcs,'CustomLibrary','P3_System_2.lib'
to the CopyFcn Callback of the block.
But that's not good enough for my purpose, because it's not the optimal solution for the maintenance of the blocks
So I started to study how Real-Time workshop works
I found these references
http://dali.feld.cvut.cz/ucebna/matlab/pdf_doc/rtw/tlc_ref.pdf
http://www.weizmann.ac.il/matlab/toolbox/rtw/rtw_ug/rtw_gs2b.html
http://dali.feld.cvut.cz/ucebna/matlab/pdf_doc/rtw/rtw_ug.pdf
I understood the DLL generation performed by RTW is essentially controlling by three files that are system target file, template makefile and make command.
So inspiring by this example
http://200.126.14.82/web/help/toolbox/rtw/tlc_ref/cp_tut10.html
http://www.weizmann.ac.il/matlab/toolbox/rtw/tlc_ref/cp_fcnl9.html
I thought to modify the .tlc file (used to specify the system language target) by including in the code the libraries that are requested for the compilation of the model. So I thought to add on the top of the code this instruction
%include "P310_System_2.lib"
I didn't test yet this solution, because I'm not at laboratory and I didn't have the RTW license on my PC
So I would like to have your opinions about this solution, if this one could work, or I'm out-of-way and I should change approach
Every suggestions are welcome
thanks for reading and happy new year of course :)

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

采纳的回答

Kaustubha Govind
Kaustubha Govind 2013-1-3
Are these blocks all S-functions? If yes, the right way to do this is to create a rtwmakecfg.m file and place it in the same folder as the S-function MEX-files. Adding your .lib files to makeInfo.linkLibsObjs will ensure that any model that uses your blocks will link against the required libraries.
  4 个评论
显示 2更早的评论
Kaustubha Govind
Kaustubha Govind 2013-1-4
grapevine: Glad you were able to solve the issue! Regarding the library path not getting resolved - note that the compiling of C code is not actually done by MATLAB itself - MATLAB simply calls into a C-compiler (typically the one selected using "mex -setup") to compile the generated code. The C compiler knows nothing about the MATLAB path. The right way to inform the C compiler about library paths is to either set the complete path using makeInfo.linkLibsObjs, or use makeInfo.library different fields to specify the library name, path, etc.

请先登录，再进行评论。

更多回答（0 个）

类别

在 Help Center 和 File Exchange 中查找有关 Simulink Coder 的更多信息

标签

产品

Community Treasure Hunt

Find the treasures in MATLAB Central and discover how the community can help you!

Start Hunting!

Translated by