All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Trevor Woerner <twoerner@gmail.com>
Cc: Yocto discussion list <yocto@yoctoproject.org>
Subject: Re: Recipe availability through eSDK (cppzmq)
Date: Fri, 04 May 2018 15:27:31 +1200	[thread overview]
Message-ID: <5208830.mbzL3EqpBH@peggleto-mobl.ger.corp.intel.com> (raw)
In-Reply-To: <CAHUNapQTzyyQf4_x82uy30Ww2ThUYnzjr8tQeCCYto9bgmOV3w@mail.gmail.com>

Hi Trevor,

On Friday, 4 May 2018 3:26:18 PM NZST Trevor Woerner wrote:
> On Wed, May 2, 2018 at 5:19 PM, Paul Eggleton <paul.eggleton@linux.intel.com
> > wrote:
> > 1) If you want the cppzmq development files to be available *within* the
> > eSDK
> > (so you can write code to use them using the eSDK), even if they are not
> > brought in by way of the image containing a package from the cppzmq
> > recipe,
> > you can install them into the eSDK by running this within the eSDK
> > environment:
> >
> > devtool sdk-install -s cppzmq
> >
> 
> Is sdk-install new? It doesn't show up when I run "devtool help"

It's only available within the eSDK - you won't see it if you run devtool next 
to the build system.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre




  reply	other threads:[~2018-05-04  3:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-30 19:10 Recipe availability through eSDK (cppzmq) Martin Siegumfeldt
2018-05-01 14:06 ` Andrea Galbusera
2018-05-01 18:49   ` Martin Siegumfeldt
2018-05-02  7:52     ` Martin Siegumfeldt
2018-05-02  8:33       ` Andrea Galbusera
2018-05-02 12:33         ` Martin Siegumfeldt
2018-05-02 14:22           ` Andrea Galbusera
2018-05-02 21:19         ` Paul Eggleton
2018-05-04  3:26           ` Trevor Woerner
2018-05-04  3:27             ` Paul Eggleton [this message]
2018-05-02  8:00     ` Andrea Galbusera

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=5208830.mbzL3EqpBH@peggleto-mobl.ger.corp.intel.com \
    --to=paul.eggleton@linux.intel.com \
    --cc=twoerner@gmail.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.