Re: [PATCH 39/39] Update the buildsystem for KConfig finding Qt

2015-10-16 Thread Thiago Macieira
On Friday 16 October 2015 06:12:41 Stefan Lippers-Hollmann wrote: > > + @set -e; $(kecho) " CHECK qt"; \ > > + qtver=`qmake -query QT_VERSION` || { \ > > + echo >&2 "*"; \ > > + echo >&2 "* qmake failed."; \ > > + echo >&2 "*"; \ > > + exit 1; \ > > +

Re: [PATCH 39/39] Update the buildsystem for KConfig finding Qt

2015-10-16 Thread Michal Marek
On 2015-10-16 06:12, Stefan Lippers-Hollmann wrote: > Hi > > On 2015-09-22, Thiago Macieira wrote: >> The buildsystem will now only search for Qt 4 and Qt 5. Support for Qt 2 >> and 3 was dropped in the previous commits (Qt 3 was EOL'ed in 2010 or >> so...). >> >> For Qt 5, to be future-proof

Re: [PATCH 39/39] Update the buildsystem for KConfig finding Qt

2015-10-16 Thread Michal Marek
On 2015-10-16 06:12, Stefan Lippers-Hollmann wrote: > Hi > > On 2015-09-22, Thiago Macieira wrote: >> The buildsystem will now only search for Qt 4 and Qt 5. Support for Qt 2 >> and 3 was dropped in the previous commits (Qt 3 was EOL'ed in 2010 or >> so...). >> >> For Qt 5, to be future-proof

Re: [PATCH 39/39] Update the buildsystem for KConfig finding Qt

2015-10-16 Thread Thiago Macieira
On Friday 16 October 2015 06:12:41 Stefan Lippers-Hollmann wrote: > > + @set -e; $(kecho) " CHECK qt"; \ > > + qtver=`qmake -query QT_VERSION` || { \ > > + echo >&2 "*"; \ > > + echo >&2 "* qmake failed."; \ > > + echo >&2 "*"; \ > > + exit 1; \ > > +

Re: [PATCH 39/39] Update the buildsystem for KConfig finding Qt

2015-10-15 Thread Stefan Lippers-Hollmann
Hi On 2015-10-16, Stefan Lippers-Hollmann wrote: > On 2015-09-22, Thiago Macieira wrote: [...] > + QT_SELECT=5 qmake -query QT_VERSION >/dev/null 2>&1 && export > QT_SELECT=5 ||: ; \ Apparently this fails if qmake isn't guarded by qtchooser, but the following should work (although I'm still

Re: [PATCH 39/39] Update the buildsystem for KConfig finding Qt

2015-10-15 Thread Stefan Lippers-Hollmann
Hi On 2015-09-22, Thiago Macieira wrote: > The buildsystem will now only search for Qt 4 and Qt 5. Support for Qt 2 > and 3 was dropped in the previous commits (Qt 3 was EOL'ed in 2010 or > so...). > > For Qt 5, to be future-proof with the future direction notice appearing > in the 5.5 release,

Re: [PATCH 39/39] Update the buildsystem for KConfig finding Qt

2015-10-15 Thread Stefan Lippers-Hollmann
Hi On 2015-09-22, Thiago Macieira wrote: > The buildsystem will now only search for Qt 4 and Qt 5. Support for Qt 2 > and 3 was dropped in the previous commits (Qt 3 was EOL'ed in 2010 or > so...). > > For Qt 5, to be future-proof with the future direction notice appearing > in the 5.5 release,

Re: [PATCH 39/39] Update the buildsystem for KConfig finding Qt

2015-10-15 Thread Stefan Lippers-Hollmann
Hi On 2015-10-16, Stefan Lippers-Hollmann wrote: > On 2015-09-22, Thiago Macieira wrote: [...] > + QT_SELECT=5 qmake -query QT_VERSION >/dev/null 2>&1 && export > QT_SELECT=5 ||: ; \ Apparently this fails if qmake isn't guarded by qtchooser, but the following should work (although I'm still

[PATCH 39/39] Update the buildsystem for KConfig finding Qt

2015-09-22 Thread Thiago Macieira
The buildsystem will now only search for Qt 4 and Qt 5. Support for Qt 2 and 3 was dropped in the previous commits (Qt 3 was EOL'ed in 2010 or so...). For Qt 5, to be future-proof with the future direction notice appearing in the 5.5 release, C++11 support is automatically enabled.

[PATCH 39/39] Update the buildsystem for KConfig finding Qt

2015-09-22 Thread Thiago Macieira
The buildsystem will now only search for Qt 4 and Qt 5. Support for Qt 2 and 3 was dropped in the previous commits (Qt 3 was EOL'ed in 2010 or so...). For Qt 5, to be future-proof with the future direction notice appearing in the 5.5 release, C++11 support is automatically enabled.