From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH 2/2] replace sdk -> nativesdk
Date: Wed, 30 Jun 2010 10:49:48 +0200 [thread overview]
Message-ID: <i0f0fc$b11$2@dough.gmane.org> (raw)
In-Reply-To: <AANLkTim86--1-sAePXz04w2xygyDpIPfCzOAw8U0mBKe@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 30-06-10 09:03, Frans Meulenbroeks wrote:
> 2010/6/30 Koen Kooi <k.kooi@student.utwente.nl>:
> Hi,
>
> Martin and I chatted about nativesdk a bit last week and after rereading
> the email thread it seems that 'nativesdk' and 'sdk' should coexist for
> awhile, so have both in BBCLASSEXTENDS?
>
>> Care to share the rationale for this?
>
>> Wrt the BBCLASSEXTEND:
>> if we have
>> BBCLASSEXTEND = "native sdk"
>> should that imply we also get native_sdk (or sdk_native or something
>> like that) (so do they extend each other), or should things like
>> nativesdk be mentioned explicitly?
You misunderstands how bbclass extend works, it just adds an 'inherit
<foo>' for each entry, it doesn't combine entries.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFMKwUsMkyGM64RGpERAiRfAJ9mccFByrea0a7RrKC7n6w903liUQCgqq9f
nQdQZPOsIotHD6ym9FWvYHk=
=qEEI
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-06-30 8:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-30 0:43 Added new cmake version Joao H. Freitas
2010-06-30 0:43 ` [PATCH 1/2] add cmake 2.8.1recipes/cmake/cmake-native_2.8.1.bb Joao H. Freitas
2010-06-30 6:55 ` Koen Kooi
2010-07-01 0:01 ` João Henrique Freitas
2010-06-30 0:43 ` [PATCH 2/2] replace sdk -> nativesdk Joao H. Freitas
2010-06-30 6:54 ` Koen Kooi
2010-06-30 7:03 ` Frans Meulenbroeks
2010-06-30 8:49 ` Koen Kooi [this message]
2010-06-30 7:03 ` Martin Jansa
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='i0f0fc$b11$2@dough.gmane.org' \
--to=k.kooi@student.utwente.nl \
--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.