Due to internal changes in the build process, the workflow described below will not work in releases newer than R2015b. For more recent MATLAB releases, the recommended way to share a model with code generation capabilities, while concealing its contents, is to use Protected Models:
------------------------------------------------------------------------------------
You can build your model without the source code of the S-function as follows:
A) Steps to follow for S-function creator
The user who created the model which contains the subsystem that defines the S-Function performs the following steps:
1. Generate the S-function for the subsystem in the original model as mentioned in the documentation.
2. Look under the mask of the generated S-function block and drag only the green colored block into your model to replace the original subsystem. Additionally, you can also remove the mask for this block by selecting "Edit Mask" from the context menu then clicking on the "Unmask" button.
** If you instead want to generate an S-function for the entire model, build the model (Ctrl-B) using S-function target (rtwsfcn.tlc) and ensure that it has the required inport and outport blocks; then replace the original model with the resulting block.
3. Build the original model (which should now contain the "green" S-function block) to generate the OBJ file for this S-function block. Note that this OBJ file is different from the one that would have also been generated in Step 1.
4. Finally, make sure to include the following files when distributing the model:
- sfunctionname.mexw64
- sfunctionname_sf.h
- sfunctionname_sfcn_rtw/sfunctionname_sf.h
- sfunctionname_sfcn_rtw/sfunctionname_mid.h
- sfunctionname_sfcn_rtw/sfunctionname_sid.h
- sfunctionname_sfcn_rtw/sfunctionname_sf_private.h
- sfunctionname_sfcn_rtw/sfunctionname_sf_types.h
- sfunctionname_sfcn_rtw/sfunctionname.mk
- sfunctionname_sfcn_rtw/rt_defines.h % for R2013b and newer
- modelname_target_rtw/sfunctionname_sf.obj
- modelname.slx
B) Steps to follow for S-function user
At the receiver’s end, once you have these files, follow the steps below:
1. Retain the directory structure of the files that were shipped to you
2. If you integrate the S-function into a new model, the OBJ-File should be placed in the newmodelname_target_rtw folder
3. For Release R2013b and newer, you also need to add sfunctionname_sf.obj to Configuration Parameters>Code Generation>Custom Code>Libraries
4. Build your model
Limitations:
If your S-function depends on other modules, this method may fail. You may have to manually add the dependent modules to the S-function by using the following command:
set_param('Sfunction_blockpath','SFunctionModules','file1 file2 file3')
Where 'Sfunction_blockpath' is the path of the Sfunction block, and 'file1', 'file2' etc are the names of the dependent files.
Attached to this solution is a ZIP-archive containing examples for the steps in A and B.
Best Answer