Just upgraded to the new version 4.72a of MDK-ARM. Now I see this behavior : after changing a single .C module, and pressing F7 (Build), with the previous version only the modified module was compiled (as it seems logical), now, with the 4.72a version, the entire project is rebuilt, which causes some waste of time...
Any thoughts on this ?
TNX
I don't witness the effect. I see it work as expected.
take a look into the following target options: - Option for Target - Output - 'Create Batch File' causes a rebuild - Option for Target - Target - 'Use Cross-Module Optimization' causes a rebuild
Thanks for the suggestion. Unfortunately I have both of those options unchecked... So the culprit must be elsewhere...
Is the date/time of your computer correct? or are the date/time of your source files incorrect?
If you carry out a build (with F7) and then immediately do a second build (with F7), does your project get rebuilt on that second attempt?
I have also tried editing a single file and building with 4.72a and have seen nothing unexpected happening.
Problem solved... the culprit was the fact that I had the checkbox that requests the preprocessor listing checked...
It rests the mystery why it did not cause a full build with the previous version...
But I don't care now... thanks for all the suggestions.
I think this an effect of the law of unintended consequences.
Erik