06.07.2011, 11:15, "Schimkowitsch Robert" <[email protected]>: > Suppose I have a file "publicheader.h", which is part of a project I am > currently editing. > > In the ".pro" file, I have > HEADERS += publicheader.h > > I also have a COPY of myheader.h in a publics path, so other projects can > easily include it. > Because I also use public files in my own project, my ".pro"-file also > contains the line > INCLUDEPATH += ../../publics > > The compiler now can take its pick: Does it follow the > HEADERS += publicheader.h > or the > INCLUDEPATH += ../../publics > > It will result in the same file (an external tool makes sure the publics > folder is updated), so from a compilation standpoint, it should really work > both ways. > > But when I follow a symbol in Creator, I would rather follow > HEADERS += publicheader.h > than > INCLUDEPATH += ../../publics > > because the first is part of my own project, and writeable whereas the second > is a read-only copy I cannot edit. > > (Before you ask: There are reasons we don't simply include files from other > project folder using relative paths. Using publics, we do not need to have > the whole tree of sources on a local machine in order to build. Instead, we > only need the single project we want, the publics files and a copy of the > object files from the server. Our make process even automates this, so you > can just check out a single project folder, and run make - everything else > will be taken from the compile server).
I have the similar problem. I have a project which builds a shared library and installs headers system-wide on Unix-like systems. System-wide headers are owned by root and cannot be edited by my user, but if these headers are installed Qt Creator always picks system ones, not editable files inside project. -- Regards, Konstantin _______________________________________________ Qt-creator mailing list [email protected] http://lists.qt.nokia.com/mailman/listinfo/qt-creator
