On Tue, Nov 10, 2015 at 7:12 AM, Sune Vuorela <s...@vuorela.dk> wrote:
> On Tuesday 10 November 2015 01:25:24 Rohan Garg wrote:
>> > Ah, it uses qmake to know where the Qt plugins are possibly (ie, qmake -
>> > query)? In that case yes, it is a good idea to set it up.
>> Yep, exactly.
> Isn't there a cmake variable that tells where qmake is, so we don't have to
> try to maek that up our selves ?
There is, it's cmake property LOCATION on the Qt5::qmake target.
So if that isn't used that'd be a bug and QT_SELECT would only workaround it.
In particular in ECM we have ECMQueryQmake which is meant to help with
querying path variables out of qmake. That bugger is using the
LOCATION property unless the target is missing altogether.
So yeah, figuring out where qmake is called from PATH and fixing that
to use Qt5::qmake LOCATION would be best here.