To avoid multiple versions of libraries A and B being loaded when opening your main application, it’s best to organize them as separate Simulink projects and use project references in all dependent libraries (C, D, E) and the main app. This way, all components refer to the same instance of A and B, avoiding duplication and version mismatches.
Here’s a suggested structure:
- Create individual projects for A and B, each with its own .prj file.
- In libraries C, D, E, and the main application, add A and B as referenced projects (via Project > New Reference).
- Avoid maintaining local copies of A and B inside device libraries to prevent conflicts.
If you're using Git, you can manage A and B as submodules, which helps lock their versions and keep them consistent across teams and branches. Just clone them into a fixed location and point your references accordingly.
This setup keeps your architecture clean, ensures version consistency across all libraries, and prevents the IDE from opening multiple versions of the same library.
Hope this helps!
