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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <4227965.esWC4RuHGt@tjmaciei-mobl4>
Date:	Fri, 16 Oct 2015 08:28:44 -0700
From:	Thiago Macieira <thiago.macieira@...el.com>
To:	Stefan Lippers-Hollmann <s.l-h@....de>
Cc:	linux-kbuild@...r.kernel.org, linux-kernel@...r.kernel.org,
	Michal Marek <mmarek@...e.com>
Subject: Re: [PATCH 39/39] Update the buildsystem for KConfig finding Qt

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; \
> > +     }; \
> 
> [...]
> 
> "qmake -query QT_VERSION" appears to be a little fragile on Debian 
> with both qt4-qmake and qt5-qmake installed, as it reports back 
> "4.8.7" by default. The actual qmake is hiding behind qtchooser
> (/usr/bin/qmake -> qtchooser) and will report different environments
> based on the chosen personality:

Since xconfig still builds with Qt 4, I didn't feel the need to force the 
choice for Qt 5. If your environment is qtchooser, then you can just set 
QT_SELECT=5 before running "make xconfig".

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/