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

__BUILD__

Since uVision does not support

__BUILD__

I need a kind of BUILD-Counter which increments automatically.
The Build should be an array of chars which can be included into the project.
Any idea?

Parents
  • The bad thing about __DATE__ and __TIME__ is that they require the specific file to be always recompiled, or you will get multiple binaries with the same build info.

    About a program to count up the contents of a text file - yes I have such a program, but it takes me some time to move the code from a unix machine to a windows machine, build it, copy the binary to a web server somewhere and then post a link to you.

    As a developer, you should be able to write your own tiny app in 2-3 minutes max.

Reply
  • The bad thing about __DATE__ and __TIME__ is that they require the specific file to be always recompiled, or you will get multiple binaries with the same build info.

    About a program to count up the contents of a text file - yes I have such a program, but it takes me some time to move the code from a unix machine to a windows machine, build it, copy the binary to a web server somewhere and then post a link to you.

    As a developer, you should be able to write your own tiny app in 2-3 minutes max.

Children
  • "The bad (sic) thing about __DATE__ and __TIME__ is that they require the specific file to be always recompiled"

    Yes, of course; but that's easily achieved in uVision - you just check 'always build' in the file options.

    I routinely have a file called "timestamp.c" for exactly this purpose!

    I think you would have to do the same with the Custom Translator?

  • As a developer, you should be able to write your own tiny app in 2-3 minutes max.
    Yes - but - I'm an embedded programmer and don't have any Windows-Compilers. That's why I'm asking for someones help.

  • Interesting - I must have missed that I can force "always build" for a single file. A lot of IDE don't support that, so the user must remember to do a full build, or use a pre-build rule to delete the output file.

    One system I used - I have forgotten which - did always run the pre-build rules before each debugging session, so it always complained that the target binary was old :)