Dockerfile: use latest Simics packages to be compatible with Simics 7#293
Dockerfile: use latest Simics packages to be compatible with Simics 7#293Wenzel merged 1 commit intointel:mainfrom
Conversation
Wenzel
changed the title
There was a problem hiding this comment.
Pull request overview
Updates the Docker-based example project creation to use the most recent Simics add-on package versions, aiming to improve compatibility with newer Simics releases.
Changes:
- Switches QSP-x86 (2096), QSP-CPU (8112), and Crypto Engine (1030) project package selections from pinned versions to
-latestin theispm projects --createcommand.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| 1000-${PUBLIC_SIMICS_PACKAGE_VERSION_1000} \ | ||
| 2096-6.0.73 \ | ||
| 8112-6.0.21 \ | ||
| 1030-6.0.7 \ | ||
| 2096-latest \ | ||
| 8112-latest \ | ||
| 1030-latest \ | ||
| 31337-latest --ignore-existing-files --non-interactive |
There was a problem hiding this comment.
Using -latest for these packages makes the Docker image build non-reproducible (the resolved versions can change over time) and can become incompatible with the pinned Simics Base 1000-${PUBLIC_SIMICS_PACKAGE_VERSION_1000} default (currently 6.0.185). Consider parameterizing these addon package versions (with default values) or pinning them to versions known to work with the selected base version, so docker build -t tsffs . remains stable.
No description provided.