You are correct, that is a limitation in our compiler plugin. You can have a look at the Code::Blocks' source code to understand how the dependency is calculated. It is in the folder src\plugins\compilergcc\depslib. Can you find a better way to do it?
So for, I have found "plugins\compilergcc\directcommands.cpp" tends to be the file that calls the depslib functions.
Tim S.
Correct, if I remember correctly, the depslib just scan each file for some pattern like
#include <xxx.h>
or
#include "xxx.h"
And put the xxx.h as the dependency of the current file. It does not use the preprocessor to handle all the sources.