We have several C++ libs that are used in applications and so many dependencies occur.
Example problem: Lets say we have an application AppA that uses libB and libC. libC uses libD. Each lib is a static library project, all libs are grouped in a solution and the dependencies are given to Visual Studio, so all libraries and the application are linked together and build in correct order.
Now I had to add the header path of libB, libC and libD to AppA and the path of libD to libC as AdditionalIncludePath. I think it would be much better, if every library could define its one include path and to use the dependency mechanism to add these paths to the include path of depended projects.
Is there such a mechanism?
I tried to use property sheets, but this would mean, that the dependency has to be defined twice.