All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Joseph Andrew de la Peña" <jdelapena@lexmark.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Wildcard in RDEPENDS when exporting perl modules to SDK
Date: Mon, 29 Sep 2014 08:09:33 +0800	[thread overview]
Message-ID: <CAJrRHk58ivpRq3GD8XbNp9YOCdivLhCK_36=p16RgHqR3ZO2GA@mail.gmail.com> (raw)
In-Reply-To: <5194477.G6vUEZEebf@peggleto-mobl5.ger.corp.intel.com>

[-- Attachment #1: Type: text/plain, Size: 1084 bytes --]

Good day Paul,

I would like to ask why you specifically noted the TOOLCHAIN_TARGET_TASK
and not the TOOLCHAIN_HOST_TASK?
Why are you inclined to putting it into the target sysroot and not the host
sysroot? Or plainly what are the guidelines on where to put the unit to
that toolchain task?

Thanks,
Joseph

On Fri, Sep 26, 2014 at 5:02 PM, Paul Eggleton <
paul.eggleton@linux.intel.com> wrote:

> Hi Joseph,
>
> On Friday 26 September 2014 13:37:29 Joseph Andrew de la Peña wrote:
> > I would like to ask how to include all perl modules into nativesdk? I see
> > that all RDEPENDS for perl has a prefix of ${PN}-module-perl-*. How can I
> > include all perl modules into the nativesdk host package group? Is there
> a
> > wild card that can be used?
>
> There isn't, but you can just add nativesdk-perl-modules to your SDK (via
> appending to TOOLCHAIN_TARGET_TASK) to accomplish the same thing - it's a
> meta-package that will bring in all of the core modules.
>
> Cheers,
> Paul
>
> --
>
> Paul Eggleton
> Intel Open Source Technology Centre
>

[-- Attachment #2: Type: text/html, Size: 1577 bytes --]

  reply	other threads:[~2014-09-29  0:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-26  5:37 Wildcard in RDEPENDS when exporting perl modules to SDK Joseph Andrew de la Peña
2014-09-26  9:02 ` Paul Eggleton
2014-09-29  0:09   ` Joseph Andrew de la Peña [this message]
2014-09-29  8:39     ` Paul Eggleton
2014-09-29  8:55       ` Joseph Andrew de la Peña

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='CAJrRHk58ivpRq3GD8XbNp9YOCdivLhCK_36=p16RgHqR3ZO2GA@mail.gmail.com' \
    --to=jdelapena@lexmark.com \
    --cc=paul.eggleton@linux.intel.com \
    --cc=yocto@yoctoproject.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.