Stateflow

Specifying Path Names in Custom Code Options

The following information applies to all custom code options that require the entry of a file or directory path.

Entries for the following custom code options can include relative or absolute paths:

• Custom include directory paths
• Custom source files
• Custom libraries
• Custom makefiles

It is not recommended that you use absolute paths for these properties, because you have to manually change them to point to new locations if you move your files and the model. Using relative path names shields you from the complexity of managing the path names as they change.

If the entered files are specified with a relative path, Stateflow searches the following directories for them:

• The current directory
• The model directory (if different from the current directory)
• The list of include directories specified for the Custom include directory paths (see previous option)
• All the directories on MATLAB's search path, excluding the toolbox directories

You can use the forward slash (/) or backward slash (\) as a file separator regardless of whether you are on a UNIX or PC platform. The makefile generator parses these strings and returns the path names with the correct platform-specific file separators.

Paths can also contain $...$ enclosed tokens that are evaluated in the MATLAB workspace. For example, the entry $mydir1$\dir1, where mydir1 is a string variable defined in the MATLAB workspace as 'd:\work\source\module1', declares the directory d:\work\source\module1\dir1 as a custom include path.

Specifying Custom Code Options

Calling Graphical Functions from Custom Code