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: Wed, 26 Aug 2009 10:12:19 +1200 [thread overview]
Message-ID: <4A9461C3.2000406@4d-electronics.co.nz> (raw)
In-Reply-To: <4A93A9E3.7090605@epfl.ch>
[-- Attachment #1: Type: text/plain, Size: 1020 bytes --]
> I have had no problem with boost and with Qt4, I have been able to
> achieve similar results without the toolchain file, only by using a
> qt.conf file as Zecke had suggested to me.
I'm using boost-1.39 and found i needed to set Boost_COMPILER or it
wouldn't find libraries. (Oh how I hate bjam, but thats another story...)
Setting Qt environment data in cmake.bbclass may seem a bit out of
place. When you consider that cmake is distributed with scripts for
configuring/detecting Qt it doesn't seem too bad.
It is definitly tidier than generating a qt.conf in every recipe. Adding
all the Qt info in EXTRA_OECMAKE is doing the same work twice.
> Although the toolchain file is the preferred value according to the
> cmake documentation, it has not been necessary to me.
The effect of a toolchain file is the same as that of defining lots of
options in EXTRA_OECMAKE.
personally, I think it is cleaner. The ability to use it outside of
openembedded is really useful to me also.
~Matt
[-- Attachment #2: matthew.vcf --]
[-- Type: text/x-vcard, Size: 319 bytes --]
begin:vcard
fn:Matthew Dombroski
n:Dombroski;Matthew
org:4D Electronics Limited
adr:Sydenham;;54 Wordsworth St;Christchurch;;8013;New Zealand
email;internet:mdombroski@4d-electronics.co.nz
tel;work:(643) 982 1113
tel;cell:0211321773
x-mozilla-html:FALSE
url:www.4d-electronics.co.nz
version:2.1
end:vcard
next prev parent reply other threads:[~2009-08-25 22:30 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 [this message]
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
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=4A9461C3.2000406@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