C Function

Integrate and call external C/C++ code from a Simulink model

expand all in page
  • C Function block

Libraries:
Simulink / User-Defined Functions

Description

The C Function block integrates and calls external C/C++ code from a Simulink® model. Use this block to define external code and customize the integration of your code by preprocessing or postprocessing the data. In addition, you can specify customized code for simulation and C code generation. You can conditionally call functions defined in your code, and you can also call multiple functions in one block. Using this block, you can initialize persistent data and pass it to an external function.

The C Function block supports initializing persistent data and calling external functions from the block dialog box. Persistent data can include an object of a C++ class defined in your custom code. See Interface with C++ Classes Using C Function Block. The block supports only initializing and terminating persistent data. The block does not support updating the data during simulation. To model a dynamic system with continuous states, use an S-Function block. To learn more about S-functions, see What Is an S-Function?

Note

C99 is the standard version of C language supported for custom C code integration into Simulink.

Specify Custom Code

Starting in R2024a, the block provides you with a range of options to specify custom C/C++ code for the block.

  • You can specify the custom code locally in the block, so you can integrate a code component that is fully contained in a single block. For example, to integrate a custom filter defined using C/C++ code into your model, specify the custom code locally using this option. The block then behaves like the specified filter.

    For versions R2026a and later:

    • When you debug a C Function block with locally specified custom code, the local custom code runs in a separate process outside of MATLAB®, known as out-of-process simulation, regardless of the simulation mode of the model containing the block. This mode is safer because the custom code is built into a separate executable. As a result, any problems with the custom code do not cause MATLAB to crash. For more information about debugging custom C/C++ code, see Debug Custom C/C++ Code.

    • When you simulate a model containing a C Function block with locally specified custom code:

      • In normal mode, the local custom code simulates in out-of-process simulation.

      • In accelerator mode, the local custom code is built into a dynamic library and simulates in the same process as MATLAB, known as in-process simulation. This mode is faster than the out-of-process simulation, but any problems with the custom code might cause MATLAB to crash.

    Previously, both debugging and simulation of locally specified custom code occurred in out-of-process simulation, regardless of simulation mode of the model containing the C Function block.

  • You can share the custom code with other blocks in a model or across multiple models. To share the custom code across multiple models you must define the custom code in the Configuration Parameters dialog box of a Simulink library model. Then, use the code in a block within the library and fetch that block from that library in other models.

For more information, see Configure custom code settings.

Report Run-time Errors and Warnings in Simulink

In custom C code that you specify in the C Function block , use the slError and slWarning functions to report run-time errors and warnings, respectively. An error terminates the simulation and must be resolved before simulation continues. A warning indicates a potential issue with the code but does not terminate the simulation.

Both slError and slWarning functions support different data type format specifiers (for example, %d for integer, %f for float) that are similar to C.

Examples :

  • slError("Error message");

  • slError("Input %f should be non-negative", x);

  • slWarning("Warning message");

  • slWarning("Input %d should be non-zero", y);

The following code executes at the start of the simulation. It uses the slError function to issue an error message if the data store fails to initialize at the start of simulation.

C Function block uses slError to report an error message at the start of simulation.

Specify Row-Major and Column-Major Array Layouts in Custom Code

Use the slSetRowMajor and slSetColumnMajor functions to specify row-major and column-major array layouts, respectively. Specify these functions in the Simulation Target pane of the Configuration Parameters dialog box. To access the Configuration Parameters dialog box from the C Function block dialog box, set the Configure custom code settingsGear icon parameter to Use Configuration Parameters Custom Code.

For a row-major layout, the row elements of a matrix are stored contiguously in memory. Similarly, for a column-major layout, the column elements of a matrix are stored contiguously in memory. For more information, see Row-Major and Column-Major Array Layouts (MATLAB Coder).

When you set the Configure custom code settingsGear icon parameter to Use Configuration Parameters Custom Code , the block can use both row-major and column-major configurations for both simulation and code generation.

When you set the Configure custom code settingsGear icon parameter to Use Block Custom Code, the block uses row-major for simulation and column-major for code generation.

Function prototypes:

  • void slSetRowMajor(const char* functionName)

  • void slSetColumnMajor(const char* functionName)

functionName must be a string literal and fully qualified.

For example, consider the following code: 

namespace NS1 {
	class ACLASS{
		public:
			void foo_row();
	};
	namespace NS2{
		void foo_col(double*, double*);
	}
}

For a fully qualified function name.

  • If the function is inside a namespace, all the nested namespaces should be included in the function name string. Based on the above code, for the column-major function, foo_col, use slSetColumnMajor("NS1::NS2::foo_col") in the configuration parameters custom code.

  • For all class members, the class name along with any nested namespaces should be included in the function name string. Based on the above code, for the row-major function foo_row, use slSetRowMajor("NS1::ACLASS::foo_row") in the configuration parameters custom code.

For a C Function block that uses classes, if the constructor takes majority, the majority must be specified in the Start code.

Examples

Integrate External C++ Code Using Class with Custom Constructor in Simulink

Integrate External C++ Code Using Class with Custom Constructor in Simulink

How to integrate external C++ code using class with custom constructor in Simulink.

Use Simulink Strings Inside C Function Block to Model Scrolling Display

Use Simulink Strings Inside C Function Block to Model Scrolling Display

How to use Simulink Strings for C Function block.

Start and Terminate Actions Within a C Function Block

Start and Terminate Actions Within a C Function Block

Use the C Function block to integrate legacy C functions that have start and terminate actions.

Call Legacy Lookup Table Functions Using C Function Block

Call Legacy Lookup Table Functions Using C Function Block

Use the C Function block to call legacy C functions that implement N-dimensional table lookups.

Modify States of a C Function Block Using Persistent Symbols

Modify States of a C Function Block Using Persistent Symbols

Define an initial persistent value to cache in the block.

Call C++ Class Methods Using C-Style Wrapper Function from C Function Block

Call C++ Class Methods Using C-Style Wrapper Function from C Function Block

Use the C Function block to call C++ class methods using a C-style wrapper function.

Call C++ Class Methods Directly from a C Function Block

Call C++ Class Methods Directly from a C Function Block

Call C++ Class Methods Directly From a C Function Block.

Limitations

Limitations apply when using these Simulink features with the C Function block.

General Limitations

These are general limitations applicable to all Simulink versions.

  • Starting in R2025a, code coverage is supported.

    For versions prior to R2025a, Simulink Coverage™ is not supported. Only execution coverage of the C Function block is measured.

  • Simulink Design Verifier™

    Simulink Design Verifier does not generate test cases for coverage objectives inside the C Function block. The limitations that apply to C/C++ S-functions also apply to C/C++ code in a C Function block. In particular, calls to external or library functions are replaced by stubs for analysis. For more information on these limitations, see Simulink Design Verifier Limitations and Considerations for S-Functions and C/C++ Code (Simulink Design Verifier).

  • Simulink Code Inspector™

    Simulink Code Inspector does not inspect the code generated from the C Function block.

  • C Function block that uses local custom code is not supported inside a Dataflow Subsystem (DSP System Toolbox).

C and C++ Language Limitations

These limitations apply to C and C++ code that you specify in a C Function block in versions R2025b and earlier. These limitations also apply to versions R2026a and later under these block settings:

Note

These limitations do not apply to the C /C++ code that you specify in a C Function block for versions R2026a and later under its default settings. The default settings occur when the Configure custom code settingsGear icon parameter is set to Use Block Custom Code and the Parse block code (enable for backward compatibility) parameter is not selected.

C Library Functions

When the C Function block meets the above mentioned limitation conditions, the block supports only these C Math Library functions.

absacosasinatanatan2ceil
coscoshexpfabsfloorfmod
labsldexploglog10powsin
sinhsqrttantanh  

When you call these functions, double precision applies unless all the input arguments are explicitly single precision. When a type mismatch occurs, a cast of the input arguments to the expected type replaces the original arguments. For example, if you call the sin function with an integer argument, a cast of the input argument to a floating-point number of type double replaces the original argument.

You can call these string library functions inside the C function block when using versions R2025a and later.

strlenstrncpystrncatstrcmpstrncmpstrstr

For more information, see Use Simulink Strings Inside C Function Block to Model Scrolling Display.

To call other C library functions, create and call an external wrapper function that calls the C library function.

abs, fabs, and labs Functions

Interpretation of the abs, fabs, and labs functions in C Function block goes beyond the standard C version to include integer and floating-point arguments:

  • If x is an integer, the standard C function abs applies to x, or abs(x).

  • If x is a double, the standard C function labs applies to x, or labs(x).

  • If x is a single, the standard C function fabs applies to x, or fabs(x).

Code Replacement Library (CRL) Based on Type

The call to the function should call the correct CRL based on the type of data passed into the function. If no CRL is specified, the call to the function should call to type-specific library. The CRL for C99 generates a type-specific function. For example:

Type passed inCode generation call
sin(doubleIn)sin(doubleIn)
sin(floatIn)sinf(floatIn)

You can call printf, memcpy and memset functions in the C Function block when using versions R2023a and later.

C++ Language Limitations

  • Local static variables using the static keyword are not supported. To cache values across time steps, define a symbol as Persistent in the Symbols table of the block dialog box.

  • Taking the address of a Constant symbol is not supported.

  • Directly calling C library functions other than the C Math library functions listed under the C Library Functions is not supported. To call other C library functions, create and call a wrapper function that calls the C library function.

Ports

Input

expand all

The number of input ports is determined by the number of symbols with Input or InputOutput scope defined in the Symbols table in the block parameters dialog box. Each input port label is the same as the name of the Input or InputOutput symbol unless you change it by editing the Label field in the Symbols table of the block dialog box.

Data Types: single | double | int8 | int16 | int32 | int64 | uint8 | uint16 | uint32 | uint64 | string | Boolean | enumerated | bus | fixedpoint

Output

expand all

The number of output ports is determined by the number of symbols with Output or InputOutput scope defined in the Symbols table in the block parameters dialog box. Each output port label is the same as the name of the Output or InputOutput symbol unless you change it by editing the Label field in the Symbols table of the block dialog box.

Data Types: single | double | int8 | int16 | int32 | int64 | uint8 | uint16 | uint32 | uint64 | string | Boolean | enumerated | bus | fixedpoint

Parameters

expand all

Parameters common to both Simulation and Code Generation tabs.

Use the Configure custom code settingsGear icon parameter to choose whether to specify the custom code in the block locally or in the Configuration Parameters dialog box. Click the arrow next to the Gear icon icon to select an option:

  • Use Block Custom Code

    This option is available for versions R2024a and later. Use this option to specify the custom code locally in the C Function block. This is the default settings. This option enables the Simulation Custom Code and the Code Generation Custom Code parameters in the Simulation section and the Code generation section, respectively.

    Starting in R2025a, code coverage is supported for locally specified custom code. To use code coverage, you must have Simulink Coverage license.

  • Use Configuration Parameters Custom Code

    Use this option to specify the custom code in the Simulation Target pane of the model Configuration Parameters dialog box. For more information, see Model Configuration Parameters: Simulation Target.

Programmatic Use

Block Parameter: CustomCodeSettingLocation
Type: character vector
Value:'BlockSettings' | 'ModelConfigurationParameters'
Default: 'BlockSettings'

Symbols and symbol properties used in the C code, specified as a table. You must enter the following attributes of each symbol in the table:

  • Name — Symbol name in the code.

    If the symbol represents a C++ class object, the Name field serves as a call to the class constructor:

    ObjectName(Argument1,Argument2,...)

  • Scope — Scope of the symbol. These scopes are available:

    • Input — Input to the block.

    • Output — Output to the block.

    • InputOutput — Both input and output to the block.

      Use the InputOutput scope to map an input passed by a pointer in your C code. Ports created using an InputOutput scope have the same name for input and output ports. InputOutput scope enables buffer reuse for input and output ports. Buffer reuse may optimize memory use and improve code simulation and code generation efficiency, depending on the signal size and the block layout. Limitations include:

      • An InputOutput symbol cannot be used in Start, Initialize Conditions, or Terminate.

      • InputOutput symbols do not support the void* data type.

      • InputOutput symbols do not support size() expressions.

    • Parameter — Block parameter that appears on the block parameter mask. The parameter name is defined by the Label of the symbol.

    • Persistent — Persistent block data, which retains its value from one time step to the next during simulation.

      You can define a void pointer using the Persistent scope. A void pointer is a pointer that can store any type of data that you create or allocate.

      You can instantiate an object of a C++ class defined in your custom code by defining a symbol with Persistent scope and using Class: ClassName as the Type for the symbol. See Interface with C++ Classes Using C Function Block.

    • Constant — Constant value, defined using value-size or numeric expressions.

  • Label — Label of the symbol. For a symbol with Input, InputOutput, or Output scope, the label appears as the port name on the block. For a symbol with Parameter scope, the label appears on the block parameter mask. If the scope is Constant, the label is the constant expression. You cannot define a label for Persistent scope symbols.

  • Type — Data type of the symbol. Select a data type from the drop-down list or specify a custom data type.

    Note

    Starting in R2025a, the block supports Simulink strings types for Input, Output, InputOutput and Persistent scopes.

    C++ class types defined in your custom code are supported, as are Simulink.Bus, Simulink Enum, and Simulink.AliasType types. Enter the Type as shown in this table.

    Custom typeSpecification in Type field
    C++ classClass: C++ClassName
    Simulink.BusBus: BusTypeName
    Simulink.EnumEnum: EnumTypeName
    Simulink.AliasTypeAliasTypeName

  • Size — Size of the symbol data. You can use a size expression to define the size of an output or use -1 to inherit size.

  • Port — Port index of the symbol. For an Input, InputOutput, or Output symbol, Port specifies the port index on the block of the port or ports corresponding to the symbol. For a Parameter symbol, Port specifies the order that the symbol appears in the block parameter mask.

Programmatic Use

Block Parameter: SymbolSpec
Type: SymbolSpec object
Value: SymbolSpec object
Default: Empty array of Symbol objects

Sample period, specified in seconds. See Types of Sample Time and Specify Sample Time. If the block defines persistent symbols, you cannot specify a continuous sample time.

Programmatic Use

Block Parameter: SampleTime
Type: character vector | string scalar
Default: "-1"

Select this option if the same custom code can be locally specified in multiple C Function blocks within a model without the blocks interfering with each other. For example, if you use a mathematical counter that contains internal states, multiple instances of the code can interfere with each other.

When you select this option, these modeling scenarios are supported:

  • Specify custom code locally in a C Function block and use the block within a For Each subsystem.

  • Specify custom code locally in a C Function block that uses continuous sample time.

  • Generate code for multiple instances of the same custom code, where each instance of the code is specified locally in a C Function block within a model.

Dependencies

To enable this parameter, set the Configure custom code settings Gear icon parameter to Use Block Custom Code. The expand the Advanced settings section.

Programmatic Use

Block Parameter: CustomCodeIsMultiInstantiable
Type: character vector | string scalar
Default: 'off'

Since R2026a

The block can generate C/C++ code containing type definitions that is required for simulation.

When this parameter is cleared, the block does not generate type definitions for the imported bus, enumerated and alias types required for simulation. The available header files already supply simulation-compatible type definitions for these imported types.

Select this parameter if you do not have a header file available with simulation-compatible type definitions for the imported enumerated, bus, or alias types. With this parameter selected, the block generates type definitions for these imported types during simulation.

Dependencies

To enable this parameter, set the Configure custom code settings Gear icon parameter to Use Block Custom Code. Then expand the Advanced settings section.

Programmatic Use

Block Parameter: SimGenImportedTypeDefs
Type: character vector | string scalar
Default: 'off'

Since R2026a

When this parameter is cleared, the block generates type definitions for exported bus, enumerated, and alias types to enable simulation.

Select this parameter if the included header files already contain type definitions for the bus, enumerated, and alias types to be exported.

Dependencies

To enable this parameter, set the Configure custom code settings Gear icon parameter to Use Block Custom Code. Then, expand the Advanced settings section.

Programmatic Use

Block Parameter: SimDisableGenExportedTypeDefs
Type: character vector | string scalar
Default: 'off'

Since R2026a

For versions R2025b and earlier, the block would parse all custom code you specified. However, the parser provided limited support for the C++ language, which restricted the C++ code you could integrate. The limitations are listed in C and C++ Language Limitations and Limitations.

Starting in R2026a, by default, the block does not parse the C/C++ code you specify locally in the block. You can specify C++ code without limitations. However, if you specify the code in the Configuration Parameters dialog box, the block still parses the code, and the limitations apply.

Select this parameter only when necessary, for example, to maintain backward compatibility, when changing from versions R2025b and earlier to versions R2026a and later. When you select this parameter, Simulink parses the C/C++ code specified locally in the block to detect error conditions and provide diagnostics.

Dependencies

To enable this parameter, set the Configure custom code settingsGear icon parameter to Use Block Custom Code. Then, expand the Advanced settings section.

Programmatic Use

Block Parameter: ParseBlockCode
Type: character vector | string scalar
Default: 'off'

Simulation

Output code that the block executes at each time step during simulation, specified as a character vector or string scalar. For example, use this parameter to call a function from external C code, make modifications to the results, and perform operations to pass the results to other blocks.

Programmatic Use

Block Parameter: OutputCode
Type: character vector or string scalar
Value: "" | C/C++ code
Default: ""

Initialization code that the block executes one time at the start of simulation. For example, use this parameter to initialize persistent symbols.

Programmatic Use

Block Parameter: StartCode
Type: character vector | string scalar
Value: "" | C/C++ code
Default: ""

Reinitialization code for the block to execute when enabling a subsystem or model in which the block is placed. The code executes one time at the start of simulation. If the block is inside a subsystem or a model that contains an Enable block with the States when enabling parameter set to reset, the code also executes each time the subsystem or model switches from disabled to enabled. See Using Enabled Subsystems. You can use this code, for example, to set an initial output value or reset the value of a persistent variable.

Programmatic Use

Block Parameter: InitializeConditionsCode
Type: character vector | string scalar
Value: "" | C/C++ code
Default: ""

Termination code that the block executes one time at the end of simulation. For example, use this code to free the memory cached on persistent symbols specified as void pointers.

Programmatic Use

Block Parameter: TerminateCode
Type: character vector | string scalar
Value: "" | C/C++ code
Default: ""

Locally specify header files for custom code. This parameter is in the Simulation Custom Code tab.

Dependencies

To enable this parameter, set the Configure custom code settingsGear icon parameter to Use Block Custom Code.

Programmatic Use

Block Parameter: SimCustomHeaderFile
Type: character vector | string scalar
Value: header file names or #include statements
Default: ""

Locally specify source files for the custom code. This parameter is in the Simulation Custom Code tab.

Dependencies

To enable this parameter, set the Configure custom code settingsGear icon parameter to Use Block Custom Code.

Programmatic Use

Block Parameter: SimCustomSourceFile
Type: character vector | string scalar
Value: any file name
Default: ""

Locally specify a list of static or shared libraries. This parameter is in the Simulation Custom Code section.

Dependencies

To enable this parameter, set the Configure custom code settingsGear icon parameter to Use Block Custom Code.

Programmatic Use

Block Parameter: SimCustomLibraries
Type: character vector | string scalar
Value: any library file name
Default: ""

Locally specify directories containing header and source files for custom code. This parameter is available in the Simulation Custom Code section.

Dependencies

To enable this parameter, set the Configure custom code settingsGear icon parameter to Use Block Custom Code.

Programmatic Use

Block Parameter:SimCustomSearchDirectory
Type: character vector | string scalar
Value: any folder path
Default: ""

Locally specify preprocessor macro definition to be added to the compiler command line. This parameter is available in the Simulation Custom Code section, in the Advanced tab.

Dependencies

To enable this parameter, set the Configure custom code settings Gear icon parameter to Use Block Custom Code.

Programmatic Use

Block Parameter: SimCustomDefines
Type: character vector
Value: preprocessor macro definition
Default: ''

Locally specify additional flags to be added to the compiler command line. This parameter is available in the Simulation Custom Code section, in the Advanced tab.

Dependencies

To enable this parameter, set the Configure custom code settings Gear icon parameter to Use Block Custom Code.

Programmatic Use

Block Parameter: SimCustomCompilerFlags
Type: character vector
Value: compiler flags
Default: ''

Locally specify additional flags to be added to the linker command line. This parameter is available in the Simulation Custom Code section, in the Advanced tab.

Dependencies

To enable this parameter, set the Configure custom code settings Gear icon parameter to Use Block Custom Code.

Programmatic Use

Block Parameter: SimCustomLinkerFlags
Type: character vector
Value: linker flags
Default: ''

Note

If a model has custom code, after the model is updated or run, the slprj folder may be locked due to the loaded custom code simulation executable file. You cannot delete the folder when it is locked. To unload the executable file and unlock the slprj folder, use the clear mex command. See clear.

Code generation

Parameters on the Code generation tab require a Simulink Coder™ or Embedded Coder® license.

Specify whether to use same or different codes for simulation and code generation. By default, this option is selected and the block uses the same code for simulation and code generation. Clear this option to use different code for simulation and code generation.

Programmatic Use

Block Parameter: CodegenUsesSimCustomCode
Type: character vector | string scalar
Default: 'on'

Specify whether to allow parsing for code generation code. By default, this option is selected and the block embeds your code in the generated code without parsing. Clearing this option enables the block to analyze the code and report any errors.

When you use different code for simulation and code generation, this parameter uses its default settings.

Dependencies

For versions R2026a and later, you can only disable this option when both these parameters are selected.

Before R2026a: You can disable this option when the Use same code as simulation parameter is selected regardless of the selection for the Configure custom code settingsGear icon parameter.

Programmatic Use

Block Parameter: GenerateCodeAsIs
Type: character vector | string scalar
Default: 'on'

Output code that the block executes at each time step during code generation. For example, use this parameter to call a function from external C /C++ code, make modifications to the results, and perform operations to pass the results to other blocks.

Programmatic Use

Block Parameter: CodegenOutputCode
Type: character vector or string scalar
Value: "" | C/C++ code
Default: ""

Initialization code that the block executes one time at the start of code generation. For example, use this parameter to initialize persistent symbols.

Programmatic Use

Block Parameter: CodegenStartCode
Type: character vector | string scalar
Value: "" | C/C++ code
Default: ""

Reinitialization code for the block to execute when enabling a subsystem or model in which the block is placed. The code executes one time at the start of code generation. If the block is inside a subsystem or in a model that contains an Enable block with the States when enabling parameter set to reset, the code also executes each time the subsystem or model switches from disabled to enabled. See Using Enabled Subsystems. You can use this code, for example, to set an initial output value or reset the value of a persistent variable.

Programmatic Use

Block Parameter: CodegenInitializeConditionsCode
Type: character vector | string scalar
Value: "" | C/C++ code
Default: ""

Termination code that the block executes one time at the end of code generation, specified as a character vector or string scalar. For example, use this code to free the memory cached on persistent symbols specified as void pointers.

Programmatic Use

Block Parameter: CodegenTerminateCode
Type: character vector | string scalar
Value: "" | C/C++ code
Default: ""

Locally specify header files for custom code. This parameter is in the Code Generation Custom Code section.

Dependencies

To enable this parameter, set the Configure custom code settings Gear icon parameter to Use Block Custom Code.

Programmatic Use

Block Parameter: CustomHeaderFile
Type: character vector | string scalar
Value: header file names or #include statements
Default: ""

Locally specify source files for the custom code. This parameter is in the Code Generation Custom Code section.

Dependencies

To enable this parameter, set the Configure custom code settings Gear icon parameter to Use Block Custom Code.

Programmatic Use

Block Parameter: CustomSourceFile
Type: character vector | string scalar
Value: any file name
Default: ""

Locally specify a list of static or shared libraries. This parameter is in the Code Generation Custom Code section.

Dependencies

To enable this parameter, set the Configure custom code settings Gear icon parameter to Use Block Custom Code.

Programmatic Use

Block Parameter:CustomLibraries
Type: character vector | string scalar
Value: any library file name
Default: ""

Locally specify Directories that contain header and source files for custom code. This parameter is in the Code Generation Custom Code section.

Dependencies

To enable this parameter, set the Configure custom code settings Gear icon parameter to Use Block Custom Code.

Programmatic Use

Block Parameter:CustomSearchDirectory
Type: character vector | string scalar
Value: any folder path
Default: ""

Locally specify preprocessor macro definition to be added the compiler command line. This parameter is in the Code Generation Custom Code section, in the Advanced tab.

Dependencies

To enable this parameter, set the Configure custom code settings Gear icon parameter to Use Block Custom Code.

Programmatic Use

Block Parameter: CustomDefines
Type: character vector
Value: preprocessor macro definition
Default: ''

Add additional flags to compiler command line. This parameter is in the Code Generation Custom Code section, in the Advanced tab.

Dependencies

To enable this parameter, set the Configure custom code settings Gear icon parameter to Use Block Custom Code.

Programmatic Use

Block Parameter: CustomCompilerFlags
Type: character vector
Value: compiler flags
Default: ''

Add additional flags to linker command line. This parameter is in the Code Generation Custom Code section, in the Advanced tab.

Dependencies

To enable this parameter, set the Configure custom code settings Gear icon parameter to Use Block Custom Code.

Programmatic Use

Block Parameter: CustomLinkerFlags
Type: character vector
Value: linker flags
Default: ''

Note

If a model has custom code, after the model is updated or run, the slprj folder may be locked due to the loaded custom code simulation executable file. You cannot delete the folder when it is locked. To unload the executable file and unlock the slprj folder, use the clear mex command. See clear.

Block Characteristics

Data Types

Booleana | busa | doublea | enumerateda | fixed pointa | integera | singlea | stringa

Direct Feedthrough

no

Multidimensional Signals

yes

Variable-Size Signals

no

Zero-Crossing Detection

no

a Actual data type or capability support depends on block implementation.

Tips

If the imported types are defined under C++ namespaces, use any of these options:

  • Generate type alias header which contains type alias corresponding to the type signatures from the imported header file using the SimulinkTypeAliasHeader argument of the Simulink.importExternalCTypes function. Then, specify the generated header file in the Headers section of the Simulation Custom Code tab. For more information, see SimulinkTypeAliasHeader. Reimport types with unique type names using UseFullyQualifiedName argument of the Simulink.importExternalCTypes function. For example, you can use this argument when you want to import the same type defined under different namespaces. For more information, see UseFullyQualifiedName

  • Import types from the headers to Architectural Data section of a Simulink data dictionary using DataDictionarySection argument of the Simulink.importExternalCTypes function. When you import the types, their corresponding namespaces are automatically synchronized. However, you cannot import two types of the same name under one namespace. For more information, see DataDictionarySection.

Extended Capabilities

expand all

Version History

Introduced in R2020a

expand all

See Also

Blocks

Objects

Functions

Topics