Load the plugin library also from the automatically generated code

[diegoferigo]

Before separating this repository, the class autogenerated by Simulink Coder was linked together with the library that contains the blocks. This allowed to instantiate the blocks directly, including their headers to the header of the autogenerated class (using the TLC functionalities).

This inclusion would be possible also now, after the split, if the class of the block would expose a parameter with the full header name instead of only the block class name. To do so, however, the block developer should remember to add this new parameter since it would be difficult to do it automatically.

Since we already have the factory working for loading the block library from the Simulink S-Function, I would rather use this approach also from the autogenerated class. In this way there isn't anymore the need to specify the block header since only its interface would suffice.

[traversaro]

Side-note: we may need to revise this in the future if we want to ever support source code FMUs as a target, see:

• https://fmi-standard.org/docs/2.0.1-develop/#_fmu_distribution
• https://github.com/modelica/fmi-standard/issues/419
• https://github.com/modelica/fmi-standard/issues/130 In particular, FMI3 should contain several improvements related to source code FMUs.

However, I agree that this is the best solution at the moment.