User forums > Help

Dependency Checking & chaning of .h files.

<< < (4/5) > >>

rickg22:
Thank you, but we'd appreciate it if the screenshots were legible the next time :lol:

Anyway, try to enable the "Full Commandline" logging in the compiler advanced options. Also, the compiler log can be copy / pasted with right-click.

grv575:
Just reading through this, it sounds like the dependency checker checks .c .cpp etc files for #includes and ensures recompilation if any of them have changed.

But is this recursive?  If a header not directly #included in a .c .cpp file but (#included in an #included header), then does it catch this or no?

mandrav:
As said before, of course it's recursive. But the compiler include dirs for the project must be setup correctly so that it can really locate the files...

I 've told it before: set the project include dirs correctly and it 'll work. The dependency checker does not follow global include dirs...

grv575:
OK, but say I don't set the include dir for each file I include, but I add them to the project.  Will the recursive #include checking look here as well (I assume yes but just to be sure)?

mandrav:

--- Quote from: grv575 on October 16, 2005, 01:28:58 am ---OK, but say I don't set the include dir for each file I include, but I add them to the project. Will the recursive #include checking look here as well (I assume yes but just to be sure)?


--- End quote ---

I 'll say it in a different way: dependency-checking is reliable and works as long as your project compiles without errors about missing #includes.
In other words:  if the compiler can find your files, C::B can too. The only difference is that C::B will not search in dirs defined in the global compiler options.

I hope it's clear enough now.

Navigation

[0] Message Index

[#] Next page

[*] Previous page