- You are correct that the static library is not needed for simulation because it is already linked into the mexw64 file.
- In order to support code generation, you will need to provide the .lib and the associated header file to your users.
Does legacy code include static libraries?
3 views (last 30 days)
I have some own code in Visual Studio from which I've generated static libraries (*.lib).
Now, I want to use in Simulink. So, I've successfully created an S-Function using the legacy_code tool and declaring my static libraries both as "HostLibFiles" and "TargetLibFiles".
Now, I want to share this S-Function with others, but I have a couple of questions:
- Shall I need to relese also the lib files togheter with the S-Function for simulation purposes? I think that this isn't needed because the *.mexw64 file created already include the libraries, isn't it?
- I think that this is needed in case the user wants to generate code from the S-Function, right?
Many thanks in advanced,