All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: how to populate sysroot with dev packages.
Date: Tue, 12 Nov 2013 16:19:32 +0000	[thread overview]
Message-ID: <1384273172.6460.13.camel@ted> (raw)
In-Reply-To: <CAKS01oniO3YHFg2CAarKKaXfkSXnkEhy_JCwZNobQGqcNdM=cw@mail.gmail.com>

On Tue, 2013-11-12 at 16:36 +0100, Anup Kini wrote:
> Hi All,
> 
> I am trying to build package-B which needs a few files from package-A-dev
> How do i deploy/install package-A-dev in sysroot such that when i build
> package-B it can access those files.
> 
> I know that i can install dev-pkgs in the image but i would like to know
> how to deploy them in the sysroot.

The act of building A should put its output into the sysroot. You'd
therefore just need a DEPENDS = "A" in recipe B.

Cheers,

Richard




  reply	other threads:[~2013-11-12 16:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-12 15:36 how to populate sysroot with dev packages Anup Kini
2013-11-12 16:19 ` Richard Purdie [this message]
2013-11-12 17:36   ` Anup Kini
2013-11-12 21:56     ` Nicolas Dechesne
2013-11-12 23:07       ` Anup Kini

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=1384273172.6460.13.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --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.