QtForum.org

Hopefully this isn't a dumb question, but I can't find the answer in the Qt docs

I'm trying to use Creator to build an application (App) that uses several libraries (e.g. ALib) that were originally created under a structure that did not use Qt. They have general unix Makefiles, but I have been pretty successful so far in creating a different .pro file for ALib that compiles it just fine, and even stores the resultant .a and header files in a standard location. The source files and headers are in "/Source/ALib" and "/Source/App"

I have a .pro file for App, and have set the Project Settings for App to be dependent on Alib's project as well. Inside App, there is "#include <ALib.h>". Because I have this legacy code organization, part of ALib's install process is to copy ALib.h to a header respository ("/Repo/include"). This repository is in the INCLUDEPATH of the App.pro file, and it builds fine.

My problem is that when I have both App.pro and ALib.pro open, and I have the setting for App that says that it's dependend on ALib, if there is a bug while building in ALib.h, and I click on the error message, it takes me to the "/Repo/include" version, which is a copy of what I'd really want to fix, which is "/Source/ALib/ALib.h".

This of course only happens when I'm trying to build App and it encounters errors related to ALib.h. If I am building ALib, it's fine because the files are self-contained. Is there a way to make it understand the dependencies more deeply and consider the /Source versions of the dependencies? I could likely fix it by manually adding the all the dependencies' /Source directories to the App INCLUDEPATH variable, but I have a LOT of libraries, and it would seem that the whole point of defining a Dependency should include this sort of functionality.

Thanks for any any help to a noob.
Costa