Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Matthew Dombroski <matthew@4d-electronics.co.nz>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] Add toolchain file generation to cmake bbclass
Date: Thu, 27 Aug 2009 10:38:47 +1200	[thread overview]
Message-ID: <4A95B977.2040408@4d-electronics.co.nz> (raw)
In-Reply-To: <4A95AAD1.4040703@4d-electronics.co.nz>

>
>> I have tried it, and the only thing I now have in the EXTRA_OECMAKE 
>> is QT_QMAKE_EXECUTABLE to be sure that it takes the one from staging 
>> and not the one from my system.
>>
>>> inherit qt4e cmake
>>> EXTRA_OECMAKE += "-DSHARED_LIBS:BOOL=ON -DCMD_LINE:BOOL=ON \
>>>         -DQT_QMAKE_EXECUTABLE=${OE_QMAKE_QMAKE} \
>>>         "
>>>
>>> export QT_CONF_PATH="${WORKDIR}/trunk/qt.conf"
>>>
>>> do_configure_prepend() {
>>>     echo "[Paths]" > $QT_CONF_PATH
>>>     echo "Prefix=${STAGING_DIR}/${HOST_SYS}/usr" >> $QT_CONF_PATH
>>>     echo "Documentation=${docdir}/${QT_DIR_NAME}" >> $QT_CONF_PATH
>>>     echo "Headers=${STAGING_INCDIR}/${QT_DIR_NAME}" >> $QT_CONF_PATH
>>>     echo "Libraries=${STAGING_LIBDIR}" >> $QT_CONF_PATH
>>>     echo "Binaries=${STAGING_BINDIR_NATIVE}" >> $QT_CONF_PATH
>>>     echo "Plugins=${libdir}/${QT_DIR_NAME}/plugins" >> $QT_CONF_PATH
>>>     echo "Data=${datadir}/${QT_DIR_NAME}" >> $QT_CONF_PATH
>>>     echo "Translations=${datadir}/${QT_DIR_NAME}/translations" >> 
>>> $QT_CONF_PATH
>>>     echo "Settings=${sysconfdir}/${QT_DIR_NAME}" >> $QT_CONF_PATH
>>>     echo "Examples=${bindir}/${QT_DIR_NAME}/examples" >> $QT_CONF_PATH
>>>     echo "Demos=${bindir}/${QT_DIR_NAME}/demos" >> $QT_CONF_PATH
>>> }
>>>
> That looks quite good now, maybe it's a good idea to add a 
> generate_qt_conf() to qmake2.bbclass.
> That way it's independent of what build system we're using.

Have tried it, didn't work.
cmake is able to find libs, headers and some executables but a lot of 
stuff is unfound.

~Matt




  reply	other threads:[~2009-08-26 22:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-25  5:35 [PATCH] Add toolchain file generation to cmake bbclass Matthew Dombroski
2009-08-25  9:07 ` Valentin Longchamp
2009-08-25 11:03   ` Holger Hans Peter Freyther
2009-08-25 15:48     ` Valentin Longchamp
2009-08-25 22:12   ` Matthew Dombroski
2009-08-26  6:47     ` Valentin Longchamp
2009-08-26 11:04       ` Valentin Longchamp
2009-08-26 21:36         ` Matthew Dombroski
2009-08-26 22:38           ` Matthew Dombroski [this message]
2009-08-27  4:28             ` Roman I Khimov
2009-08-26 17:21       ` Valentin Longchamp
2009-08-26 17:28         ` [PATCH 1/1] add toolchain file for cmake compilations Valentin Longchamp

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4A95B977.2040408@4d-electronics.co.nz \
    --to=matthew@4d-electronics.co.nz \
    --cc=openembedded-devel@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox