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 <[email protected]> on
behalf of Oswald Buddenhagen <[email protected]>
Sent: Friday, July 21, 2017 2:49:03 PM
To: [email protected]
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
[email protected]
http://lists.qt-project.org/mailman/listinfo/development
_______________________________________________
Development mailing list
[email protected]
http://lists.qt-project.org/mailman/listinfo/development
