FAQ 298: Best Practice for Handling S-Functions, Libraries and Additional Source Code

Question

I have organized my S-Function MEX-files, source files and header files in separate folders. When using an S-Function in a model I would like to add the respective source paths to the build process. How can I do that?
My custom code references object files or libraries. How can I use these libraries?

Answer

Tags
Date 2013-08-01
Software Type Implementation Software
Product ConfigurationDesk, RTI (Real-Time Interface)
Information Type Frequently Asked Questions
Information Category Working with
dSPACE Release 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, Prior to 2013-A
Keywords additional paths, S-Function source files, user makefile, USR.MK file, rtwmakecfg.m, libraries, user makefile, USR-MK file, Custom Code Page, Simulink Coder®, Real-Time Workshop®

Drive innovation forward. Always on the pulse of technology development.

Subscribe to our expert knowledge. Learn from our successful project examples. Keep up to date on simulation and validation. Subscribe to/manage dSPACE direct and aerospace & defense now.

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.