[Qt-interest] Reason for separate INCLUDEPATH and DEPENDPATH in qmake

[Atlant Schmidt]

Jan:

  There's an answer in Reply #4 at the end of this thread:

    http://lists.trolltech.com/qt-interest/2006-03/thread00323-0.html


  Also, perhaps DEPENDPATH may sometime be a *SUPERSET*
  of INCLUDEPATH if you other, non-header-file dependencies?

                           Atlant

-----Original Message-----
From: qt-interest-bounces at trolltech.com [mailto:qt-interest-bounces at trolltech.com] On Behalf Of Jan Kundrát
Sent: Monday, September 13, 2010 11:25
To: qt-interest at trolltech.com
Subject: [Qt-interest] Reason for separate INCLUDEPATH and DEPENDPATH in qmake

Hi,
I just got bitten by a .pro file which did not include all of the
INCLUDEPATH directories in the DEPENDPATH.

I changed the signature of a constructor of one class (last parameter
got removed) and expected the compiler to spit out and error on all
places which were actually calling said constructor. Unfortunately, one
place got undetected, the generated object files even passed through the
linker and I got a nasty segfault at runtime (Gentoo Linux x86, not
using --as-needed linking or qnything special).

So, now I wonder if there is any real use case for having INCLUDEPATH
and DEPENDPATH with different values -- perhaps QMake could somehow warn
if they do not match? Or am I missing something obvious here?

With kind regards,
Jan

--
cd /local/pub && more beer > /dev/mouth


This e-mail and the information, including any attachments, it contains are intended to be a confidential communication only to the person or entity to whom it is addressed and may contain information that is privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please immediately notify the sender and destroy the original message.

Thank you.

Please consider the environment before printing this email.