What is the best way to distribute a custom simulink library using C++ S-Function blocks to multiple users? Preferably using some form of CI/CD pipeline

I'm looking for a way to distribute a custom simulink library which has multiple C++ S-function blocks to multiple users. Is there a way to automatically build, package the MEX S-function blocks and their masks, and deploy them as a library usable by multiple users.

The pipeline (if possible) would go something like {cpp source code} -> {mex binaries} -> {library of S-function blocks} -> people can use the latest version of this library.

Answer 1

[Mark McBroom]

1. Write a MATLAB script that Uses the mex() function to compile and link source code for each S-function into a mex function ( you could also use the legacy_code tool to do this
2. If you have a fixed list of S-Function blocks, I would recommend just creating the blocks and mask manually. However, you can also script this using the create_system(), add_block() and set_param() functions to automate the creation of your Simulink Library

The above scripts can then be called from a CI system whenever the source code for your s-functions changes.

[Tom Goring]

How are shared libraries usually deployed? Are they just placed on a shared drive which is just updated by the CI system, or is there an inbuilt method of controlling updates etc?

[Mark McBroom]

There is no built-in method for controlling. Some customers place on a shared drive(s) that all users point to. Others commit to CM tool and the have users pull new version when convenient.

[Tom Goring]

Alright, thanks very much!