[Development] Behavior change for QMake install targets since 5.9

[Simon Hausmann]

I was under the impression that


    http://code.qt.io/cgit/qt/qtbase.git/tree/qmake/generators/makefile.cpp#n1304


was the code path hit if the entry in foo.files is not a "//real file or target" (as per the comment a little above).


Simon

________________________________
From: Development <development-bounces+simon.hausmann=qt.io at qt-project.org> on behalf of Oswald Buddenhagen <oswald.buddenhagen at qt.io>
Sent: Friday, July 21, 2017 2:49:03 PM
To: development at qt-project.org
Subject: Re: [Development] Behavior change for QMake install targets since 5.9

On Fri, Jul 21, 2017 at 12:17:41PM +0000, Simon Hausmann wrote:
>    It's true that the internal install command does not support wild-cards.
>    We decided that it is the responsibility of the caller to resolve those
>    (qmake).
>
we did? :}
as much as i despise wildcards in source file lists, this behavior is
actually documented for INSTALLS.
compare https://bugreports.qt.io/browse/QTCREATORBUG-17935
(on the upside, qmake is now consistent with qtc :D).

_______________________________________________
Development mailing list
Development at qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/development/attachments/20170721/6ee8a33f/attachment.html>