On 03/30/2015 04:10 PM, Dale Kazakore Powell wrote:
> On 30/03/15 21:49, Rui Nuno Capela wrote:
>> On 03/30/2015 03:44 PM, Rui Nuno Capela wrote:
>>>>
>>>> OK. One must set (export) a QT_SELECT=4 or such before running
>>>> ./configure.
>>>> Since qmake never needed such an environment variable or argument
>>>> before, I do
>>>> consider this a bug. An example is that the ./configure here did not
>>>> set that
>>>> variable or supply an argument based on choices made by its qt choice
>>>> argment.
>>>> No one knew one needed it and the ./configure --help said that qt4 was
>>>> default.
>>>>
>>>> So Rui, please implement (and the default qt4) in the configure.
>>>
>>> excuse me :)
>>>
>>> qtchooser, and thus the QT_SELECT switch, is probably a debian exclusive
>>> thing, meaning that it's specific to some debian packaging policy,
>>> organization and whatever--it is NOT a Qt thing and might not apply to
>>> other distros or environments so easily, mainly because there's no
>>> qtchooser package installed nor even available.
>>
>> might be mistaken however ;)
>>
>> byee
>
> Definitely seems to be part of Qt.
>
> https://qt.gitorious.org/qt/qtchooser/source/ae5eeef85c9a818bfa6a3e03511e3935e9abe01f:
>
> http://qt-project.org/search?search=qtchooser
>
so i was mistaken when sadd qtchooser is not a qt thing. my bad ;)
but the rest of the excuse still applies:
the onus of the desired/current QT_SELECT setting should be left to the
user and not hard-coded on a configure script, at least for the time being.
byee
-- rncbc aka. Rui Nuno Capela _______________________________________________ Linux-audio-user mailing list Linux-audio-user@email-addr-hidden http://lists.linuxaudio.org/listinfo/linux-audio-userReceived on Mon Mar 30 20:15:03 2015
This archive was generated by hypermail 2.1.8 : Mon Mar 30 2015 - 20:15:03 EEST