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

Automatic Dependency Checking

I'm not sure if this is a bug or not, but so far, all the RealView projects I've worked on don't build like I think they should. Specifically, if I change something in a header file that's included in a project C source file and then press F7 to build the project, the C file that included the changed header file does not get compiled. Shouldn't it? Is there some option in the IDE I have to enable to make automatic dependency checking work so that doing a build compiles all C source files that have changed (via a changed included header file)?

Obviously, doing a build all gets around this problem, but there's no hot key like F7 that I can use to do a build all, and I'm so used to just doing a build via F7 that I often end up with an invalid target file downloaded to my board, because the build doesn't build everything that had changed.

Can anyone shed any light on this...?

Thanks,
Dave Sudolcan.

Parents
  • I tried deleting the dependancy file and then closing and opening the uVision IDE with the View - Include File Dependencies checkbox checked and not checked, but it didn't seem to have any effect.

    I also tried editing the dependency file manually (after first backing up my project) since it's an ASCII text file (thank you KEIL!) and the format for include files looked fairly straightforward, well, all but the 8-byte HEX value in parenthesis on those lines, but that made no difference either. And yes, I did see the warning at the top of the file about not modifying this file. When I did my next build that file got overwritten anyway, back to where the include files were not specified properly.

    Can't seem to get around this one. Time to submit it to KEIL as a bug.

    Bummer.

Reply
  • I tried deleting the dependancy file and then closing and opening the uVision IDE with the View - Include File Dependencies checkbox checked and not checked, but it didn't seem to have any effect.

    I also tried editing the dependency file manually (after first backing up my project) since it's an ASCII text file (thank you KEIL!) and the format for include files looked fairly straightforward, well, all but the 8-byte HEX value in parenthesis on those lines, but that made no difference either. And yes, I did see the warning at the top of the file about not modifying this file. When I did my next build that file got overwritten anyway, back to where the include files were not specified properly.

    Can't seem to get around this one. Time to submit it to KEIL as a bug.

    Bummer.

Children