From: Valentin Longchamp <valentin.longchamp@epfl.ch>
To: "openembedded-devel@lists.openembedded.org"
<openembedded-devel@lists.openembedded.org>
Subject: [RFC] cmake cross-compilation paths
Date: Fri, 19 Jun 2009 18:10:52 +0200 [thread overview]
Message-ID: <4A3BB88C.5010504@epfl.ch> (raw)
Hello,
I am trying to build cmake based programs that use QT with Openembedded.
The actual support for cmake in OE worked until now that I only had
"simple" dependencies. Now with QT as as dependency, I use the cmake
FindQt4 Module that strongly relies on qmake to find the different QT
cmake variables (try to run ${STAGINGBINDIR}/qmake4 -query).
The problem is that FindQt4 does not find the qmake4 (as I have proposed
to rename it like that in my patch from yesterday) since the
CMAKE_FIND_ROOT_PATH given to the cmake cmd in the classes/cmake.bbclass
only is set to
-DCMAKE_FIND_ROOT_PATH=${STAGING_DIR_HOST}
that does not include ${STAGING_BIN_DIR}. Setting it to
-DCMAKE_FIND_ROOT_PATH=${STAGING_DIR}
makes configure fail (it cannot find the needed header files); and with
-DCMAKE_FIND_ROOT_PATH="${STAGING_DIR_HOST};${STAGING_DIR}"
qmake4 is not found either.
So if someone who knows cmake better than me can tell me how to give two
paths to a cmd -DPATH_NAME=VALUE1 VALUE2 for cmake (and what would be
the equivalent to STAGING_DIR_HOST for ${STAGING_DIR}/i686-linux in my
case) that would help a lot (I am not sure it can be achieved).
All the inputs are greatly appreciated and if you could help me for the
OE var names (especially for the equivalent to ${STAGING_DIR_HOST} that
would point to ${STAGING_DIR}/i686-linux, that would already be a good
start)
Thanks a lot
--
Valentin Longchamp, PhD Student, EPFL-STI-LSRO1
valentin.longchamp@epfl.ch, Phone: +41216937827
http://people.epfl.ch/valentin.longchamp
MEA3485, Station 9, CH-1015 Lausanne
next reply other threads:[~2009-06-19 16:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-19 16:10 Valentin Longchamp [this message]
2009-06-24 5:48 ` [RFC] cmake cross-compilation paths Douglas Royds
2009-06-24 12:19 ` 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=4A3BB88C.5010504@epfl.ch \
--to=valentin.longchamp@epfl.ch \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.