CONFIG(<host>, <host>|<target>) { # Do <host> stuff } else { # Do <target> stuff }
Might work, if you know the <host> or <target> mkspecs. However, for general purpose we can introduce variables which contain these. QMAKE_HOST_SPEC=<host> QMAKE_TARGET_SPEC=<target1> <target2> for example.. -- .marius > -----Original Message----- > From: development-bounces+marius.storm-olsen=nokia.com@qt- > project.org [mailto:development-bounces+marius.storm- > olsen=nokia....@qt-project.org] On Behalf Of Knoll Lars (Nokia-MP/Oslo) > Sent: Tuesday, January 03, 2012 9:21 AM > To: Hansen Kent (Nokia-MP/Oslo); development@qt-project.org > Subject: Re: [Development] V8's location > > On 1/3/12 2:49 PM, "ext Kent Hansen" <kent.han...@nokia.com> wrote: > > >Den 01. jan. 2012 20:59, skrev ext simon.hausm...@nokia.com: > >> Whoever is going to do the work may first have to add support for host > >>builds in modules outside qtbase, in order to support v8 snapshots. > >> > >> Simon > >> > > > >Hmm, I was getting ready to create a JIRA task ("Add support for host > >builds in modules outside qtbase"), but then I noticed that > >"linguist/lrelease" is still present in the part of the configure script > >that handles the host-or-target mkspec selection: > > > > > >*tools/bootstrap*|*tools/moc*|*tools/rcc*|*tools/uic*|*linguist/lrelease > *) > > > >SPEC=$QMAKESPEC ;; > > > >but lrelease lives in the qttools module now. So how is it built as a > >host tool when cross-compiling? Is it hard-coded somewhere else or is > >there already a general solution in place (too much New Year's optimism)? > > Not sure how it works currently. But in general it'd be good if we can fix > this once and for all by adding proper cross compilation support to > qmake/configure. Something where you can specify host vs target in the > .pro file. > > Cheers, > Lars > > > > >qtbase/mkspecs/features/qt_module_config.prf does > >"qtPrepareTool(QMAKE_LRELEASE, lrelease)" and some more stuff, does it > >still belong there? > > > >Kent > >_______________________________________________ > >Development mailing list > >Development@qt-project.org > >http://lists.qt-project.org/mailman/listinfo/development > > _______________________________________________ > Development mailing list > Development@qt-project.org > http://lists.qt-project.org/mailman/listinfo/development _______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development