User`s guide

3 Code Generation and the Build Process
3-34
• USER_SRCS — Additional user sources, such as files needed by S-functions.
For example, suppose you have an S-function called
my_sfcn.c,whichis
built with
sfcn_lib1.c,andsfcn_lib2.c.(library routines for use with
many S-functions). You can build
my_sfcn.c using:
mex my_sfcn.c sfcn_lib1.c sfcn_lib2.c
In this case, the make command for the Real-Time Workshop should be
specified as:
make_rtw USER_SRCS="sfcn_lib1.c sfcn_lib2.c"
YoucanavoidusingUSER_SRCS by specifying
set_param('block','SFunctionModules','sfcn_lib1 sfcn_lib2')
See “Using S-Functions with the Real-Time Workshop” in Chapter 3 of
Writing S-Functions.
•
USER_INCLUDES — Additional include paths for example suppose you have
two include paths (
c:\appl\inc and c:\support\inc) that are required for
the
sfcn_lib1.c and sfcn_lib2.c files in the above example. The make
command would be specified as:
make_rtw USER_SRCS="sfcn_lib1.c sfcn_lib2.c"
USER_INCLUDES="−Ic:\appl\inc −Ic:\support\inc"
grt_msvc.tmf
The Real-Time Workshop provides a generic real-time template makefile
(
grt_msvc.tmf) to create a Microsoft Visual C/C++ project makefile called
model.mak for Windows 95, Windows 98, and Windows NT. grt_msvc.tmf is
designed to be used with
nmake, which is bundled with MicroSoft’s Visual C/
C++.
You can supply the following options to
grt_msvc.tmf via arguments to the
make command, make_rtw:
•
OPTS — User-specific options, for example,
make_rtw OPTS="/D MYDEFINE=1"
• USER_SRCS — Additional user sources, such as files needed by S-functions.
For example, suppose you have an S-function called
my_sfcn.c,whichis