All of lore.kernel.org
 help / color / mirror / Atom feed
From: Trevor Woerner <twoerner@gmail.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>,
	"openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: Yocto Project Status WW17
Date: Sun, 24 Apr 2016 19:17:08 -0400	[thread overview]
Message-ID: <20160424231708.GA7573@linux-yxv0> (raw)
In-Reply-To: <CAJTo0LYnK-sd+d1bkJN39AhkAN0t+42Nonm38Qyy3BXm1nLYdw@mail.gmail.com>

On Fri 2016-04-22 @ 08:29:19 PM, Burton, Ross wrote:
> On 22 April 2016 at 18:04, Trevor Woerner <twoerner@gmail.com> wrote:
> >
> > Have the eSDK and CROPS projects been announced publicly? Are they
> available
> > for us to "play with"?
> 
> 
> eSDK is the "extensible SDK', or what appears when you do bitbake image -c
> populate_sdk_ext.  This should be in the manual already, the tl;dr is that
> its an SDK you can manipulate after installation.

Thanks for the update.

> CROPS is docker magic to do builds on Windows/Mac.  Todor did a
> presentation at ELC: http:
> //events.linuxfoundation.org/sites/events/files/slides/Todor_Minchev_CROPS_ELC_2016.pdf
> <http://events.linuxfoundation.org/sites/events/files/slides/Todor_Minchev_CROPS_ELC_2016.pdf>

I was *very* excited to learn about CROPS at ELC, which is why I was wondering
if it was available to experiment with somewhere?


WARNING: multiple messages have this Message-ID (diff)
From: Trevor Woerner <twoerner@gmail.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>,
	"openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] Yocto Project Status WW17
Date: Sun, 24 Apr 2016 19:17:08 -0400	[thread overview]
Message-ID: <20160424231708.GA7573@linux-yxv0> (raw)
In-Reply-To: <CAJTo0LYnK-sd+d1bkJN39AhkAN0t+42Nonm38Qyy3BXm1nLYdw@mail.gmail.com>

On Fri 2016-04-22 @ 08:29:19 PM, Burton, Ross wrote:
> On 22 April 2016 at 18:04, Trevor Woerner <twoerner@gmail.com> wrote:
> >
> > Have the eSDK and CROPS projects been announced publicly? Are they
> available
> > for us to "play with"?
> 
> 
> eSDK is the "extensible SDK', or what appears when you do bitbake image -c
> populate_sdk_ext.  This should be in the manual already, the tl;dr is that
> its an SDK you can manipulate after installation.

Thanks for the update.

> CROPS is docker magic to do builds on Windows/Mac.  Todor did a
> presentation at ELC: http:
> //events.linuxfoundation.org/sites/events/files/slides/Todor_Minchev_CROPS_ELC_2016.pdf
> <http://events.linuxfoundation.org/sites/events/files/slides/Todor_Minchev_CROPS_ELC_2016.pdf>

I was *very* excited to learn about CROPS at ELC, which is why I was wondering
if it was available to experiment with somewhere?


  reply	other threads:[~2016-04-24 23:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-22 15:13 Yocto Project Status WW17 Jolley, Stephen K
2016-04-22 17:04 ` Trevor Woerner
2016-04-22 17:04   ` [OE-core] " Trevor Woerner
2016-04-22 19:29   ` Burton, Ross
2016-04-22 19:29     ` [OE-core] " Burton, Ross
2016-04-24 23:17     ` Trevor Woerner [this message]
2016-04-24 23:17       ` Trevor Woerner
2016-04-25  9:25       ` Burton, Ross
2016-04-25  9:25         ` [OE-core] " Burton, Ross

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=20160424231708.GA7573@linux-yxv0 \
    --to=twoerner@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@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.