search

ARM-software / CMSIS_5

CMSIS Version 5 Development Repository
http://arm-software.github.io/CMSIS_5/index.html
Apache License 2.0
1.33k stars 1.08k forks source link

Finding currently used packs programmatically #1347

Open mumble-myopia opened 3 years ago

mumble-myopia commented 3 years ago

This may be the wrong place (seems initially to be more about building your own packs), in which case sorry, but I have been pointed here by ARM support. When we release a binary, we need to record the version numbers of the various packs that went into it (so we can reliably reproduce it later). I can't see that CMSIS-Build is really the answer but certainly others must have come across this issue.

Can anyone suggest a reliable way of achieving this please?

JonatanAntoni commented 3 years ago

Hi @mumble-myopia,

Yes, this question doesn't really fit here. The answer depends on the build environment you are using.

If you are using CMSIS-Build you may raise this question at https://github.com/Open-CMSIS-Pack/devtools. There are already similar discussions going on, like involving some sort of lock file.

For other build environments you'd need to get in touch with the tool vendor's support.

Cheers, Jonatan

mumble-myopia commented 3 years ago

thanks for that - will repost there (including details of our build env - good point). Basically we use Keil uVision, Sourcetree/Git under Windoze.

rkeil62 commented 3 years ago

The button Details in this MDK dialog gives you the report you are looking for: https://www.keil.com/support/man/docs/uv4/uv4_ca_rtemanager.htm

see also here: https://www.keil.com/support/man/docs/uv4/uv4_dg_rte.htm