From: Detlef Vollmann <dv@vollmann.ch>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC] get rid of legacy staging
Date: Sat, 24 Jul 2010 17:05:09 +0200 [thread overview]
Message-ID: <4C4B0125.1040304@vollmann.ch> (raw)
In-Reply-To: <AANLkTimG_U4Gsc9LuK6oKDJO2rE=xB7cDQzGf6dsh2GM@mail.gmail.com>
On 07/24/10 16:35, Frans Meulenbroeks wrote:
> 2010/7/24 Martyn Welch <martyn@welchs.me.uk>
>
>> Can anyone point me to any documentation that describes what legacy staging
>> is and roughly what needs to be done to remove it?
>
> There was a post half a year or so ago from Koen, but I can't find it.
> Basically it boils down to removing do_stage from a recipe in which case
> do_install is used to install things in staging
> in some cases do_install need to be modified to deal with peculiarities that
> were done in do_stage
>
> For native recipes NATIVE_INSTALL_WORKS = "1" may need to be added.
That's not really much of an explanation.
Let's take an example. I have two out of tree kernel modules A and B.
B depends on A.
With "legacy" staging, in A_1.0.bb I have a do_install, that copies
the kernel object, and a do_stage, that copies the header file at
a place where B_1.0.bb can find it.
How do I do that with non-"legacy" staging?
Detlef
next prev parent reply other threads:[~2010-07-24 15:04 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-24 9:57 [RFC] get rid of legacy staging Frans Meulenbroeks
2010-07-24 10:46 ` Koen Kooi
2010-07-24 11:35 ` Frans Meulenbroeks
2010-07-24 13:01 ` Martyn Welch
2010-07-24 14:35 ` Frans Meulenbroeks
2010-07-24 15:05 ` Detlef Vollmann [this message]
2010-07-24 15:17 ` Koen Kooi
2010-07-24 15:40 ` Detlef Vollmann
2010-07-26 19:52 ` Tom Rini
2010-07-24 16:08 ` Frans Meulenbroeks
2010-07-24 16:12 ` Chris Larson
2010-07-24 17:22 ` Frans Meulenbroeks
2010-07-24 18:52 ` Khem Raj
2010-07-25 18:32 ` Frans Meulenbroeks
2010-07-26 20:59 ` C Michael Sundius
2010-07-26 21:39 ` Chris Larson
2010-07-27 10:19 ` Frans Meulenbroeks
2010-07-27 10:38 ` Koen Kooi
2010-07-27 10:59 ` Frans Meulenbroeks
2010-07-27 14:26 ` Chris Larson
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=4C4B0125.1040304@vollmann.ch \
--to=dv@vollmann.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.