From: Tom Rini <tom_rini@mentor.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH]Removing Legacy staging from genboot native recipe
Date: Fri, 13 Aug 2010 13:23:25 -0700 [thread overview]
Message-ID: <4C65A9BD.9010105@mentor.com> (raw)
In-Reply-To: <i43kf7$942$1@dough.gmane.org>
Koen Kooi wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 13-08-10 14:25, Frans Meulenbroeks wrote:
>> 2010/8/13 Paul Menzel <paulepanter@users.sourceforge.net>:
>>> Am Freitag, den 13.08.2010, 17:17 +0600 schrieb noor_ahsan@mentor.com:
>
>>>> +NATIVE_INSTALL_WORKS = "1"
>>> I am really a noob, but is not that for “normal”, i.e. no *-native,
>>> recipes indicating no explicit native recipe is needed?
>> Afaik this is not needed.
>
> If your -native recipe has something different than 'make install' in
> do_install, it needs NATIVE_INSTALL_WORKS = "1" but only if you use
> BBCLASSEXTEND to make it native.
Sounds like a tip for
http://wiki.openembedded.org/index.php/Legacy_staging (which Noor and
some other folks here have been looking at). Thanks? :)
--
Tom Rini
Mentor Graphics Corporation
next prev parent reply other threads:[~2010-08-13 20:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-13 11:17 [PATCH]Removing Legacy staging from genboot native recipe noor_ahsan
2010-08-13 12:03 ` Paul Menzel
2010-08-13 12:25 ` Frans Meulenbroeks
2010-08-13 14:22 ` Koen Kooi
2010-08-13 20:23 ` Tom Rini [this message]
2010-08-14 8:41 ` Frans Meulenbroeks
2010-08-14 15:39 ` Khem Raj
-- strict thread matches above, loose matches on Subject: below --
2010-08-13 5:39 noor_ahsan
2010-08-13 6:29 ` Frans Meulenbroeks
2010-08-13 6:53 ` Ahsan, Noor
2010-08-13 8:07 ` Paul Menzel
2010-08-13 9:01 ` Ahsan, Noor
2010-08-13 9:18 ` Paul Menzel
2010-08-13 14:36 ` Khem Raj
2010-08-13 20:24 ` Tom Rini
2010-08-14 8:58 ` Frans Meulenbroeks
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=4C65A9BD.9010105@mentor.com \
--to=tom_rini@mentor.com \
--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.