Thanks for the heads up Alex! I've added 1.8TB of extra space so we should be set for awhile. Sorry that you weren't able to push. I've also fixed the obvious style problems with the headers on

Rough patch for documentation improvements now that I know how gitsm should work and to help others that might be caught by switching from git:// to gitsm:// URIs. Chris

Hi, I'm trying to push a commit to meta-mono and it's failing due to lack of space, it says, Counting objects: 12, done. Delta compression using up to 2 threads. Compressing objects: 100% (5/5),

HI. We integrating the Qt5 in yocto Dora branch, all dependents plugins are installed and get executed with their libraries expect the qtquickcontrols while building this I am getting following

You use it exactly the way you use git.py - gitsm:// instead of git://. It's basically git fetching plus submodule handling. I personally would rather see it merged into git.py, but I can see the

On May 17, 2014 3:58 PM, "Christopher Larson" <clarson@...> wrote: > > > > On Saturday, May 17, 2014, Chris Morgan <chmorgan@...> wrote: >> >> Hello. >> >> I noticed that git.py doesn't seem to have

See gitsm.py. -- Christopher Larson clarson at kergoth dot com Founder - BitBake, OpenEmbedded, OpenZaurus Maintainer - Tslib Senior Software Engineer, Mentor Graphics

Hello. I noticed that git.py doesn't seem to have support for submodules. I worked around this in my recipe by adding a pre configure step but I was wondering if a patch to add another option to

Hi Beth, Am 2014-05-15 17:32, schrieb Flanagan, Elizabeth: Actually I was running master of Autobuilder. However, somehow Autobuilder checked the branch dora out (its the branch I tried to build,

Hi Beth, Am 2014-05-16 19:11, schrieb Flanagan, Elizabeth: Sounds reasonable, I agree. Note that, I will be in vacation for the next three weeks, hence it will be June until I will be able to

You best course of action here is to keep mimicing the toolchain build sequence changes as you hop major releases similar exercise that external toolchain guys have to do. Its a constant battle.

would be fine.

Ok, so looking at this a bit more and I think we need to look at how we set up the deploydir in PublishArtifacts a bit more. I think what we can do here is pull the functionality that we have

I just tried the meta-sourcery (old CSL) layer and it worked a treat. I only had to add that layer and define a single variable to point to their tools. Next week, I think I'll have a go at adapting

fair enough ... i should be able to test this by end of day. rday -- ======================================================================== Robert P. J. Day

Hi Robert, I just finished building the Yocto image for the Galileo. I used the V1.0.0 BSP: https://downloadcenter.intel.com/Detail_Desc.aspx?DwnldID=23197 The documentation on how to build is also

Whilst I would usually say yes, in this case I'm not sure that would be ideal. The layer index is designed to index individual layers, but the layers within this repository aren't meant to be used

No, nothing has changed. The separation here is probably not as clearly defined as it ought to be. I guess what I'd say is, you shouldn't look at this as a fully worked example of how to structure

possibly a silly question, but what are the dependencies between those three layers? i'm used to seeing layer dependencies listed in a layer's "layer.conf" file. if i look at the meta-iot-devkit

Well, it's true that sstate won't help you solve that problem since the recipe still needs to be buildable (i.e. all dependencies need to be satisfied); sstate is rather the answer to "I want an