• State Not Answered
  • Locked Locked
  • Replies 6 replies
  • Subscribers 21 subscribers
  • Views 2210 views
  • Users 0 members are here
2025 survey

We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.

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

Automatic Dependency Checking

Dave Sudolcan

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.

  • 0

    I am having the same problem. Sometimes I can delete the dependency file, and turn off / on the include depenceny flag and get then regenerated. Often when they are regenerated, some of the files don't get includes added properly. Also after a build some may come or go. If there is a + next to the source file, it does see to work properly. I just don't always get or keep a +.

    As far as build all, the F8 key is not used for a shortcut so feel free to assign it to build all
    ( Edit / Configuration / Shortcut keys / Project:Rebuild all target files )

  • 0 in reply to Robert McNamara

    Thanks for the F8 tip.

    Hopefully someone else will post a tip on how to fix this build problem.

  • 0 in reply to Dave Sudolcan

    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.

  • 0 in reply to Dave Sudolcan

    KEIL's Tech Support suggestion:

    1 = Install current tools from mdk302a.exe (I had been using tools from mdk301a.exe).

    2 = Delete the project's .DEP file.

    3 = Rebuild the project.

    My source file dependencies are working properly once more.

    Thanks KEIL.

    Dave.

  • 0 in reply to Dave Sudolcan

    The problem is still present in 3.02a. I have been running it for a few weeks (maybe 2) and have deleted the .dep file a few times. I would bet it will be back for you when you add a few more files to the project.

  • 0 in reply to Dave Sudolcan

    The problem is still present in 3.02a. I have been running it for a few weeks (maybe 2) and have deleted the .dep file a few times. I would bet it will be back for you when you add a few more files to the project.