All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: about staging
Date: Fri, 30 Oct 2009 17:43:40 +0100	[thread overview]
Message-ID: <hcf53t$4jp$1@ger.gmane.org> (raw)
In-Reply-To: <ac9c93b10910300040v779f8446k31de3dfc2b2fe298@mail.gmail.com>

On 30-10-09 08:40, Frans Meulenbroeks wrote:
> Hi,
>
> Yesterday I ended up in a discussion on staging in #oe (ok, ok, I
> mainly caused the discussion :-) )
> Also based upon that I looked at various recipes on how people
> implement staging.
>
> There does not seem to be really standard way.
> Some recipes copy from ${S} which ihmo is not desirable; i think it
> should be a file that is exported by the application).
> Others use other mechanisms.
>
> For my own recipe I ended up with something like:
>
> do_stage() {
>          install -d ${STAGING_INCDIR}
>          install -d ${STAGING_INCDIR}/${PN}
>          install -m 0644 ${D}/${includedir}/${PN}/*.h ${STAGING_INCDIR}/${PN}
> }
>
> as that seems the best. ${D} contans the exported/installed files from
> the application. Those files are the ones the application wants to
> make externally available and those should end up in staging. Not
> something from ${S}.

Is ${D} garanteed to be present at staging time? I don't think we have a 
current hard rule for that.

regards,

Koen




  reply	other threads:[~2009-10-30 16:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-30  7:40 about staging Frans Meulenbroeks
2009-10-30 16:43 ` Koen Kooi [this message]
2009-10-30 17:32   ` Frans Meulenbroeks
2009-10-31  7:39     ` Denys Dmytriyenko
2009-10-31 10:43       ` 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='hcf53t$4jp$1@ger.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.