On 6 June 2013 03:04, Paul Eggleton <paul.eggle...@linux.intel.com> wrote: > On Wednesday 05 June 2013 17:57:32 Paul Eggleton wrote: >> On Wednesday 05 June 2013 09:46:49 Saul Wold wrote: >> > On 06/05/2013 02:30 AM, Martin Jansa wrote: >> > > On Wed, Jun 05, 2013 at 07:01:50PM +1000, Jonathan Liu wrote: >> > >> qconfig.pri was not being loaded by qmake properly. This means Qt >> > >> qmake projects are unable to query QT_ARCH, QT_VERSION and other >> > >> variables defined in qconfig.pri. >> > >> >> > >> Export OE_QMAKE_QT_CONFIG, setting it to the location of qconfig.pri >> > >> so that it can be located by qmake. >> > > >> > > There is such patch already: >> > > http://lists.openembedded.org/pipermail/openembedded-core/2013-May/07831 >> > > 4. >> > > html >> > >> > Got lost in my queue, adding it for the next MUT. >> >> FWIW I am still concerned by the assertion in the commit message about it >> causing undesirable behaviour. I'd want that checked out and the note >> removed before we look at merging this. > > (I mean undesirable behaviour on rebuild after applying this patch; I should > mention I'm testing this at the moment.)
Please test it in combination with the patch I just submitted which fixes QMAKE_QT_CONFIG being overwritten with empty value from .qmake.cache. I needed it to build Qt Creator. You can do a basic test as follows: bitbake -c devshell fotowall mkdir test cd test echo 'message(Qt Version: $$QT_VERSION)' > test.pro qmake2 test.pro Regards, Jonathan _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
