On Monday 30 March 2015 15:49:48 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 ;)
Yeah, there are loads of distros out there (Debian/Ubuntu are major players),
but ...
If things were sooo simple, then a Makefile could be supplied and simply make
and run. Many of the plugins are distributed this way!
Configure is there for a purpose. Does not mean one must cater to every distro-
unique feature, but configure scripts do test OS versions, features, etc., to
enable transportability. So this QT_SELECT maybe does belong there.
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@email-addr-hidden
http://lists.linuxaudio.org/listinfo/linux-audio-user
Received 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