• Getting Started

Types of Target Environments Supported By Simulink Coder

Applications of Supported Target Environments

Simulink and Stateflow Model

MATLAB Code with Simulink Model

What Is the V-Model?

Types of Simulation and Prototyping in the V-Model

Types of In-the-Loop Testing in the V-Model

Mapping of Code Generation Goals to the V-Model

Get Familiar with the Functional Design of the Model

View the Top Model

View the Subsystems

Get Familiar with the Simulation Testing Environment

Check the Model for Adverse Conditions and Simulation Settings

Configure the Model for Code Generation

Save Your Model Configuration as a MATLAB Function

Check the Model for Adverse Conditions and Code Generation Settings

Generate Code for the Model

Review the Generated Code

Generate an Executable

Enable Data Objects for Generated Code

Get Familiar with Effects of Simulation on Data Typing

Include External C Functions in a Model

Create a Block That Calls a C Function

Validate External Code in the Simulink Environment

Validate C Code as Part of a Model

Call a C Function from Generated Code

Key Points

Learn More

• User's Guide

• Reference

• Blocks

• Functions

updateFilePathsAndExtensions

updateFileSeparator

• Build Process

• Desktop IDEs and Desktop Targets

• Project Documentation

• Rapid Simulation

• System Target File Callback Interface

• Target Language Compiler and Function Library

Examples

• Release Notes

updateFilePathsAndExtensions - Update files in model build information with missing paths and file extensions

Syntax

updateFilePathsAndExtensions(buildinfo, extensions)

extensions is optional.

Arguments

buildinfo: Build information returned by RTW.BuildInfo.
extensions (optional): A cell array of character arrays that specifies the extensions (file types) of files for which to search and include in the update processing. By default, the function searches for files with a .c extension. The function checks files and updates paths and extensions based on the order in which you list the extensions in the cell array. For example, if you specify {'.c' '.cpp'} and a folder contains myfile.c and myfile.cpp, an instance of myfile would be updated to myfile.c.

Description

Using paths that already exist in the model build information, the updateFilePathsAndExtensions function checks whether any file references in the build information need to be updated with a path or file extension. This function can be particularly useful for

Maintaining build information for a toolchain that requires the use of file extensions
Updating multiple customized instances of build information for a given model

Note If you need to use updateFilePathsAndExtensions, you should call it once, after all files have been added to the build information, to minimize the potential performance impact of the required disk I/O.

Examples

Create the folder path etcproj/etc in your working folder, add files etc.c, test1.c, and test2.c to the folder etc. This example assumes the working folder is w:\work\BuildInfo. From the working folder, update build information myModelBuildInfo with any missing paths or file extensions.

myModelBuildInfo = RTW.BuildInfo;
addSourcePaths(myModelBuildInfo, fullfile(pwd,...
 'etcproj', '/etc'), 'test');
addSourceFiles(myModelBuildInfo, {'etc' 'test1'...
 'test2'}, '', 'test');
before=getSourceFiles(myModelBuildInfo, true, true);
before

before = 

    '\etc'    '\test1'    '\test2'

updateFilePathsAndExtensions(myModelBuildInfo);
after=getSourceFiles(myModelBuildInfo, true, true);
after{:}

ans =

w:\work\BuildInfo\etcproj\etc\etc.c


ans =

w:\work\BuildInfo\etcproj\etc\test1.c


ans =

w:\work\BuildInfo\etcproj\etc\test2.c