Hello, I works with µVision v 5.0.5.15, and when I build my ARM project, all files are always rebuild ! I found on the net, that the problem can be the TZ system variable. But in my PC (Windows 7) there is no this variable. I found on the net, that "Create Bath File" on Target/Output menu, should not be selected. It's true for me.
would you have an idea for my problem ?
thank you for your help. Best regards
I meet exact same problem with same µVision version and under Windows 7 as well.
Hello, At the moment, I have not found a solution, and the problem wasted a lot of time ! if you have an idea...
Best Regards
Found Keil released new MDK5.01 by chance. Upgrade with it then the problem solved. Nothing declared in release note however. You may try the same way. Good luck!
Thank you for this information, but my license expired last month ! therefore not possible upgrade.
It happens when the project file is in a directory deeper than the generated obj files. Move the obj and lst folders below the project directory and see what happens.
Hello,
When I put the obj and lst folders, below the project, the problem removed. But when you have several projects on the same code it is always better to separate code and objects for example the archiving.
With previous version of µVision, it did not have this problem !!
Thank you for your help
Best regards
With a tool like CVS, you can have incremental storage of your source changes while using a file .cvsignore to inform which directories and files to ignore - so it will ignore any object files or even full output directories even if inside the source tree.
Another thing is that it isn't uncommon to have multiple copies of the source code, to allow different tests to be performed before deciding if the code should be accepted or not. Each source tree retrieved as a branch from the source code repository. Then it isn't so fun to have the object files above the source tree.
Ok, everyone has their way of working. The problem is a regression of µVision ! and as my license has expired, I have no opportunity to obtain correction.
Yes - of course we are talking about a stupidity/bug if the environment demands that the output files must be in a subdirectory. It should be irrelevant where the output files are, as long as they are in a path that the build environment can reach.
My post was just a comment regarding "archiving".