MATLAB: Is it possible to include “defines” in the rtwmakecfg.m file in Real-Time Workshop 7.1 (R2008a)

simulink coder

I am using a custom template make file (TMF) in order to add a "define" parameter. A snippet of the custom makefile is provided below:

 CPP_REQ_DEFINES = -DMODEL=$(MODEL) -DRT -DNUMST=$(NUMST) \
                   -DTID01EQ=$(TID01EQ) -DNCSTATES=$(NCSTATES) \
                   -DMT=$(MULTITASKING) -DHAVESTDIO -DXPCMSVISUALC \
                   -DXPCCALLCONV=__cdecl  -DUSE_RTMODEL -DERT_CORE \
                   -DLEGACY_CODE_NOT_UNICODE_COMPLIANT

I added the last line to make some of the legacy code compile properly for xPC target. I would like to avoid using our own files in place of default MATLAB files because this practice takes us away from any updates that are made in future MATLAB releases, and the "rtwmakecfg.m" file seems to be the perfect place to put "defines" that only affect a certain S-function.

Best Answer

It is not possible to specify "defines" in the rtwmakecfg.m file.

To work around the issue, add defines to buildInfo in the PostCodeGenCommand as shown below:

set_param(model,'PostCodeGenCommand','addDefines(buildInfo,{''-DLEGACY_CODE_NOT_UNICODE_COMPLIANT'' ''-DMY_DEFINE=1''},''OPTS'');')

The defines must be put in the group 'OPTS', which is the last argument to addDefines.

For more information on using the PostCodeGenCommand, refer to the documentation titled "Programming a Post Code Generation Command" in the Help Documentation (for R2008a) linked below:

web([docroot,'/toolbox/rtw/ug/bqobjt8.html#bqobjzq'])

This section describes how to use the PostCodeGenCommand, as well as points to the list of functions available for manipulating buildInfo, which is the source of information put into the generated makefile.

Related Solutions

MATLAB: How to define separate includes for legacy and non-legacy code when generating code

The best approach to this workflow is to create a custom target file which includes a set of rtwoptions allowing the separate specification of standard includes and legacy code includes. This can then be linked to a custom TMF variable which can be used appropriately in the code. You can find a general summary of this workflow in our documentation using the link below:

http://www.mathworks.com/help/releases/R2015b/rtw/ug/customizing-system-target-files.html#f6351

A summary of the steps which need to be taken are shown below:

1) Define an element in the 'rtwoptions' file to capture the location of the directory

rtwoptions(2).prompt         = 'Custom Legacy Code Directory';
rtwoptions(2).type           = 'Edit';
rtwoptions(2).enable         = 'on';  
rtwoptions(2).default        =  'C:\LegacyCodeInc';   
rtwoptions(2).popupstrings  = '';
rtwoptions(2).tlcvariable   = 'CustomLegacyCodeDir';
rtwoptions(2).tooltip       = '';
rtwoptions(2).callback      = '';
rtwoptions(2).opencallback  = '';
rtwoptions(2).closecallback = '';
rtwoptions(2).makevariable  = 'CUSTOM_LEGACY_CODE_DIR';

2) Modify your TMF in order to expand the CUSTOM_LEGACY_CODE_DIR makevariable

# Additional file include paths
|>START_EXPAND_INCLUDES<|
MATLAB_INCLUDES = $(MATLAB_INCLUDES);|>EXPAND_DIR_NAME<||>END_EXPAND_INCLUDES<|
ADD_LEGACY_INCLUDES = |>CUSTOM_LEGACY_CODE_DIR<|;
INCLUDE = .;$(RELATIVE_PATH_TO_ANCHOR);$(MATLAB_INCLUDES); $(ADD_LEGACY_INCLUDES); $(INCLUDE)
!if "$(SHARED_SRC_DIR)" != ""
INCLUDE = $(INCLUDE);$(SHARED_SRC_DIR)
!endif

After expansion, the code above will appear as the following

# Additional file include paths
MATLAB_INCLUDES = $(MATLAB_INCLUDES);$(START_DIR)\bouncing_ball02302873_legacy_include_rtw
MATLAB_INCLUDES = $(MATLAB_INCLUDES);$(START_DIR)
MATLAB_INCLUDES = $(MATLAB_INCLUDES);$(MATLAB_ROOT)\toolbox\physmod\mech\c
MATLAB_INCLUDES = $(MATLAB_INCLUDES);$(MATLAB_ROOT)\toolbox\physmod\common\foundation\core\c
ADD_LEGACY_INCLUDES = C:\LegacyCodeInc;
INCLUDE = .;$(RELATIVE_PATH_TO_ANCHOR);$(MATLAB_INCLUDES); $(ADD_LEGACY_INCLUDES); $(INCLUDE)
!if "$(SHARED_SRC_DIR)" != ""
INCLUDE = $(INCLUDE);$(SHARED_SRC_DIR)
!endif

MATLAB: How to modify the build information for mex code generation with the codegen function

Codegen('mex') does not support custom toolchains, as noted in the documentation at the following link:

https://www.mathworks.com/help/coder/ug/use-the-custom-toolchain.html

Compiler settings are inherited from the "mex -setup" command.

Instead, you can use the Post-Code-generation command to pass a custom Build Information Object to the "codegen" command.

For example, you could add a link flag with the following function:

function setbuildargs(buildInfo)
     linkFlags = {'-lpthread'};
     buildInfo.addLinkFlags(linkFlags);
     cfg = coder.config('mex');
end

That function can then be used to pass the build information object via the PostCodeGenCommand:

>> cfg.PostCodeGenCommand = 'setbuildargs(buildInfo)';

More information and further examples can be found in the documentation at the following link:

https://www.mathworks.com/help/coder/ug/customizing-the-post-code-generation-build-process.html

Best Answer

Related Solutions

MATLAB: How to define separate includes for legacy and non-legacy code when generating code

MATLAB: How to modify the build information for mex code generation with the codegen function

Related Question