background
in Eclipse plugin development. The eclipse plugin we are currently working
on does communicate with the containers using the Eclipse docker tooling
api. This is a scaled back version that we hope is doable given current
resources.
BR,
Brian Avery
an Intel employee
On Mon, Mar 27, 2017 at 9:38
with running docker linux programs on the mac other than those caused by
the difference in horsepower between my build server and my laptop.
Thanks,
Brian Avery
an Intel employee
p.s. Andrea, would you mind replying with how you changed the docker run to
make loopback work? I’d like to add it
kernel as
the host.
Thanks for the feedback and if I missed or shortchanged something please
let me know,
-Brian
an intel employee
On Mon, Dec 5, 2016 at 10:42 AM, Khem Raj wrote:
> On Mon, Dec 5, 2016 at 10:04 AM, Brian Avery
> wrote:
> > Please note, this is going out to 3
Please note, this is going out to 3 lists in an attempt to insure that no
one who would be impacted by this change misses it. Implied spam apology
included.
The Yocto Project currently provides a virtual machine image called the
Build Appliance (
https://downloads.yoctoproject.org/releases/yoc
To add more options, there's also a set of CROPS (YP subproject) Docker
containers aimed at supporting a general build environment for YP, one
aimed at the extensible sdk, and several for toaster depending on the
desired version.
poky/oe:
https://hub.docker.com/r/crops/poky/
extensible-sdk:
http
Hi,
This doesn't default to slirp, it just allows it as an option.
In particular, on CROPS containers on Windows 10 and Mac OSX the
hypervisor is *not* a linux kernel. This means that the only way we can run
qemu in the container for testing/debugging is to run it in slirp mode
.since there is n
Yocto includes pseudo which handles the things fakeroot does and a bit more
https://www.yoctoproject.org/tools-resources/projects/pseudo.
-brian
an Intel employee
On Tue, Aug 9, 2016 at 7:27 AM, Jan Lindåker wrote:
>
>
> From: yocto-boun...@yoctoproject.
Hi,
The question about number of machines we currently have from (Armin ?)
made me wonder.
Here's toasters/layer indexes current view of machines.
jethro - 226
krogath - 148
master - 310
I'll go ahead and attach the lists in case anyone is curious and it
took a long sql statement to make them :).
For the update script you also need python-git. Since we are already
using a virtenv, why not add it to requirements :).
yolk lists the following as being available so I fairly arbitrarily
picked 0.3.7 on the assumption it was the "best" of the 0.3 line...
GitPython 1.0.1
GitPython 1.0.0
GitPytho
