• State Not Answered
  • Locked Locked
  • Replies 9 replies
  • Subscribers 15 subscribers
  • Views 2253 views
  • Users 0 members are here
Options
Related
How was your experience today?
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

Andy Neil

See http://www.keil.com/forum/56892/

"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

    uVision creates a Build Log file with the name <project>.build_log.htm. This file lists:

    • The toolchain that has been used during project build
    • The Software Packs (along with version number) that has been used during project build

    For re-creating a project it is important to install the same Compiler Version and Software Packs. Typically this requires:

    • Re-installation of the MDK Core. The version number is indicated in the build_log.htm file with Toolchain: MDK-ARM Professional Version: 5.15.0. You can either safe the complete MDK Core installer or download the exact version from http://www.keil.com/update/rvmdk.asp. It is also possible to specify a Compiler version as explained here: http://www.keil.com/support/man/docs/uv4/uv4_armcompilers.htm
    • Installation of the Software Packs as listed in the build_log.htm file under Software Packages used:
    • . Use the PackInstaller to download the files, directly enter the URL from the build_log.htm or safe these packs from the directory .\Keil_v5\ARM\Pack\.Download.

    We have information about the b>build_log.htm here http://www.keil.com/support/man/docs/uv4/uv4_ca_buildlog.htm

    As I can see right now, this seems to be quite complex to understand. Perhaps because the process is not clearly documented. I believe improving the documentation would do the job, but I am open to listen to suggestions (please post them on this forum).

    Thanks Reinhard

Reply
  • 0

    uVision creates a Build Log file with the name <project>.build_log.htm. This file lists:

    • The toolchain that has been used during project build
    • The Software Packs (along with version number) that has been used during project build

    For re-creating a project it is important to install the same Compiler Version and Software Packs. Typically this requires:

    • Re-installation of the MDK Core. The version number is indicated in the build_log.htm file with Toolchain: MDK-ARM Professional Version: 5.15.0. You can either safe the complete MDK Core installer or download the exact version from http://www.keil.com/update/rvmdk.asp. It is also possible to specify a Compiler version as explained here: http://www.keil.com/support/man/docs/uv4/uv4_armcompilers.htm
    • Installation of the Software Packs as listed in the build_log.htm file under Software Packages used:
    • . Use the PackInstaller to download the files, directly enter the URL from the build_log.htm or safe these packs from the directory .\Keil_v5\ARM\Pack\.Download.

    We have information about the b>build_log.htm here http://www.keil.com/support/man/docs/uv4/uv4_ca_buildlog.htm

    As I can see right now, this seems to be quite complex to understand. Perhaps because the process is not clearly documented. I believe improving the documentation would do the job, but I am open to listen to suggestions (please post them on this forum).

    Thanks Reinhard

Children
No data