Although it's not the answer I liked to here I already expected something like 
that. And yes I agree, there are many libraries behaving exactly like this. And 
thinking about having the possibility to set  the prefix, it's obvious that 
there normally isn't a need for that.

However I just wonder (since I am rather new to linux development) what is the 
best practice for that. Should one creating a special directory for every 
library that is built so that there are only the prerequisites of the library 
that is built?

Best Regards and thanks

Heiko

-----Ursprüngliche Nachricht-----
Von: [email protected] 
[mailto:[email protected]] Im 
Auftrag von Thiago Macieira
Gesendet: Montag, 5. Oktober 2015 16:46
An: [email protected]
Betreff: Re: [Interest] Recompiling qt

On Monday 05 October 2015 11:33:40 Boettger, Heiko wrote:
> Thank you for the help, this actually only works if the headers where 
> not already installed in the system directories. I always need to 
> perform something like:
> 
> make uninstall
> make clean
> make
> make install
> 
> What I'm looking for is a central place where the include directories 
> are defined. I was told that the definition of the include path is 
> deeply nested inside the qt build files and it's not easy to fix the 
> include path order. To be more precise I want to make sure that the 
> include directories from the current build are always looked up first.

There's no such option. It all depends in the order they get added to the 
INCLUDEPATH variable in qmake, which means the order depends on the .*.pro and 
*.pri files themselves, what they include, what other libraries they try to 
pull in, etc.

Conclusion: don't. Do not build a module when that module is already installed 
in the same prefix as one of your dependencies. This applies to more than just 
Qt and is a good rule of thumb for everything.
--
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center

_______________________________________________
Interest mailing list
[email protected]
http://lists.qt-project.org/mailman/listinfo/interest
_______________________________________________
Interest mailing list
[email protected]
http://lists.qt-project.org/mailman/listinfo/interest

Reply via email to