This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Version Control of MDK v5 Project

"The project file should have been 100% focused on the rules required to perform the similar task of a Makefile. Everything else should have been optional information stored in separate files that doesn't need to be version-controlled and that can be auto-created if missing"

I entirely agree. It seems that Keil have totally broken the Project File arrangement as far as Version control goes.

:-(

And how is it intended that the Pack status should be controlled??

Parents

0 Christopher Seidl

over 10 years ago in reply to Andy Neil

hello Andrew,

that is stored in the <RTE> section of the uvprojx file, for example:

  <RTE>
    <packages>
      <filter>
        <targetInfos/>
      </filter>
      <package name="CMSIS" schemaVersion="1.3" url="http://www.keil.com/pack/" vendor="ARM" version="4.2.0">
        <targetInfos>
          <targetInfo name="ULINK pro" versionMatchMode="fixed"/>
        </targetInfos>
      </package>
      <package name="STM32F1xx_DFP" schemaVersion="1.2" url="http://www.keil.com/pack/" vendor="Keil" version="1.1.0">
        <targetInfos>
          <targetInfo name="ULINK pro"/>
        </targetInfos>
      </package>
    </packages>
...

For the CMSIS Pack, versionMatchMode="fixed" means that the version of the Pack is fixed (in this case to 4.2.0). The STM32F1xx_DFP is set to "use latest" in the GUI and thus it does not get a versionMatchMode entry.

Kind regards,

Christopher

Reply