this problem seems to occur if symbolic links for source directories are used... changing of

QString QmakeProFileNode::sourceDir() const

{ return m_projectDir; }

to

QString QmakeProFileNode::sourceDir() const

{ return QDir(m_projectDir).canonicalPath(); }

should resolve this... hopefully....;)

cheers
Jan



Am 23.03.2016 um 17:42 schrieb Jan Krause:
Hi all,

since QTC 3.6 the internal parsing of qmake function shadowed(path) (@see http://doc.qt.io/qt-5/qmake-function-reference.html) seems to be wrong... especially if DESTDIR depends on the result -> the execution path of the current run-configuration of QTC is wrong... but qmake makes it right (@see messages in the example...)

here a snippet of an example pro file:
------------------------------------------------
APP_PATH = $$shadowed($$PWD)/build


BIN_PATH = $$APP_PATH/bin

DESTDIR = $$BIN_PATH
message (BIN_PATH: $$BIN_PATH)
------------------------------------------------------------

I created a bugreport (https://bugreports.qt.io/browse/QTCREATORBUG-15897) ... but maybe there are other reasons... and I'm wrong....

Any ideas?

Cheers
Jan



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

Reply via email to