**** BEGIN LOGGING AT Sun Dec 21 03:00:00 2014
Dec 21 19:59:53 <karooga> Hi, anyone around?
Dec 21 20:03:40 <karooga> How do I use a recipe specifically:  http://layers.openembedded.org/layerindex/recipe/28534/
Dec 21 20:05:42 <paulbarker> Have a look at http://www.yoctoproject.org/docs/1.7/mega-manual/mega-manual.html#enabling-your-layer to enable the layer that recipe is in after you've downloaded it
Dec 21 20:06:05 <paulbarker> And http://www.yoctoproject.org/docs/1.7/mega-manual/mega-manual.html#usingpoky-extend-customimage for how to add the generated packages to an image
Dec 21 20:06:26 <paulbarker> That manual covers most of the basics
Dec 21 20:10:11 <karooga> paulbarker: Thanks.
Dec 21 20:11:38 <karooga> paulbarker: I seem to be getting myself tangled when I use multiple layers (multiple repos).  From what I read I understood I just needed to add each of them to my bblayers.conf?
Dec 21 20:12:43 <paulbarker> Yes, add the path to each layer to the BBLAYERS variable in bblayers.conf
Dec 21 20:13:34 <karooga> I'm happy with a single layer, but openembedded-core and meta-openembedded are not playing nicely with my meta-browsers and meta-raspberrypi.
Dec 21 20:14:35 <karooga> It seems like I'm dependency problems I'm getting into, which I thought was the whole idea around having layers in the first place.
Dec 21 20:14:54 <karooga> :-/
Dec 21 20:15:05 <paulbarker> Each layer should list its dependencies in a README file
Dec 21 20:15:54 <paulbarker> meta-browser doesn't look to be very clear though
Dec 21 20:16:04 <karooga> Yes, but if I look at something like meta-openembedded root, I don't see any conf directories.
Dec 21 20:16:17 <paulbarker> it says it depends on meta-openembedded, which can't be right
Dec 21 20:16:33 <paulbarker> meta-openembedded is just a collection of commonly used layers
Dec 21 20:17:09 <paulbarker> it's not actually a layer itself
Dec 21 20:17:32 <karooga> Ah, so I just use meta-openembedded/meta-oe ?
Dec 21 20:17:54 <paulbarker> Possibly, I'm not sure if meta-browser depends on any of the other layers in meta-openembedded as well
Dec 21 20:18:32 <paulbarker> It should be like the meta-raspberrypi README which explicitly says which layers in meta-openembedded it depends on
Dec 21 20:18:32 <karooga> Why do you say meta-browser is not clear?
Dec 21 20:19:21 <paulbarker> meta-browser says:
Dec 21 20:19:21 <paulbarker> URI: git://git.openembedded.org/meta-openembedded
Dec 21 20:19:22 <paulbarker> branch: master
Dec 21 20:19:23 <paulbarker> revision: HEAD
Dec 21 20:19:33 <karooga> There is a readme in the root of meta-browser?  Says it depends on openembedded-core and meta-openembedded.
Dec 21 20:19:35 <paulbarker> whereas, meta-raspberrypi says:URI: git://git.openembedded.org/meta-openembedded
Dec 21 20:19:35 <paulbarker> layers: meta-multimedia
Dec 21 20:19:35 <paulbarker> branch: master
Dec 21 20:19:37 <paulbarker> revision: HEAD
Dec 21 20:19:57 <paulbarker> meta-raspberrypi has 'layers:', meta-browser doesn't
Dec 21 20:20:05 <paulbarker> probably worth reporting as a bug
Dec 21 20:20:26 <karooga> So it doesn't expose any layers?
Dec 21 20:20:46 <paulbarker> no it just doesn't say which particular layers within meta-openembedded that it depends on
Dec 21 20:21:17 <paulbarker> I kinda wish meta-openembedded was named slightly differently, it'd avoid a lot of confusion
Dec 21 20:22:10 <karooga> Ah right.
Dec 21 20:22:44 <karooga> Yeah, that naming had me chasing my tail for a few minutes. :-)
Dec 21 20:23:38 <karooga> How did you arrive at that summary information on layers for each repository?
Dec 21 20:23:52 <paulbarker> you're not the first one
Dec 21 20:24:27 <paulbarker> the URI/branch/layers/revision things I posted? They're in the README files in each layer
Dec 21 20:25:28 <karooga> :-)
Dec 21 20:25:43 <karooga> Lame, ok.
Dec 21 20:26:16 <karooga> But the information in the README doesn't mean that it won't work it just means it doesn't tell you how it's supposed to work?
Dec 21 20:26:35 <karooga> Or what you're suppose to use to get it to work :-)
Dec 21 20:28:01 <paulbarker> I'd start with meta-oe and meta-multimedia layers listed
Dec 21 20:28:54 <paulbarker> I'd also definitely say email the maintainers for meta-browser and ask them to clarify the dependencies in the README
Dec 21 20:29:07 <karooga> I'll do that.
Dec 21 20:29:49 <karooga> I've just run the target for meta-raspberrypi (bitbake rpi-hwup-image) and it's barking about no gnome-settings-daemon.
Dec 21 20:30:12 <karooga> I see that it's under meta-openembedded/meta-gnome
Dec 21 20:30:33 <karooga> So that is one of the layers that is needed in their README?
Dec 21 20:31:11 <karooga> I can add that to my bblayers.conf now?  But is order important?  i.e. before meta-browser?
Dec 21 20:31:29 <paulbarker> order shouldn't matter
Dec 21 20:33:53 <karooga> wow, it ran.
Dec 21 20:34:08 <karooga> No errors!
Dec 21 20:34:11 <karooga> I don't believe.
Dec 21 20:34:25 <paulbarker> that's a good start!
Dec 21 20:34:56 <paulbarker> I'd definitely feed back to meta-browser that their README should be more explicit about the dependencies and to meta-raspberrypi that they may be missing a dependency on meta-gnome
Dec 21 20:35:32 <karooga> So having the layers just means that recipes in the layers "can" be used.  It doesn't mean that they are being used?
Dec 21 20:36:20 <paulbarker> Yes that's right
Dec 21 20:36:30 <karooga> Yeah, let me mail them right now.
Dec 21 20:36:51 <paulbarker> having unnecessary layers may slow down the parsing recipes stage, but it shouldn't affect much else
Dec 21 20:37:15 <paulbarker> most layers are well behaved and don't change anything unless you use a recipe, distro or machine defined in that layer
Dec 21 20:41:38 <karooga> I think both the dependencies are related to meta-browser.
Dec 21 20:42:35 <paulbarker> Did you add chromium to IMAGE_INSTALL when building rpi-hwup-image?
Dec 21 20:42:53 <karooga> Nope not yet.
Dec 21 20:43:02 <karooga> That's to pull in the recipe right?
Dec 21 20:43:34 <paulbarker> Oh hang on, I'm forgetting how things work
Dec 21 20:43:36 <karooga> IMAGE_INSTALL_append_rpi-hwup-image = " chromium"
Dec 21 20:43:40 <karooga> ?
Dec 21 20:44:02 <karooga> I don't know... I'm new to this build process... :-)
Dec 21 20:44:03 <paulbarker> the dependencies probably will be from meta-browser
Dec 21 20:44:34 <paulbarker> I'd just use IMAGE_INSTALL_append = " chromium"
Dec 21 20:44:45 <paulbarker> unless you want to build other images without chromium
Dec 21 20:44:50 <karooga> I tried meta-raspberrypi first and that worked a charm first time :-)
Dec 21 20:45:06 <paulbarker> Ok yea, definitely meta-browser which is adding the dependencies then
Dec 21 20:45:07 <karooga> I did that without chrome, without a gui...
Dec 21 20:45:19 <karooga> Sweet!
Dec 21 20:45:36 <karooga> I was about to recall my email....
Dec 21 20:46:20 <karooga> So I've added the chromium recipe but when I build the rpi-hwup-image it doesn't seem to do anything.
Dec 21 20:47:33 <paulbarker> Using IMAGE_INSTALL_append in local.conf should definitely make a difference
Dec 21 20:47:39 <karooga> I'm running my package_classes as package_deb - but that shouldn't change anything?
Dec 21 20:48:08 <paulbarker> that should be an issue
Dec 21 20:48:36 <karooga> So should it be IMAGE_INSTALL_append = " chromium"
Dec 21 20:49:37 <paulbarker> I think so
Dec 21 20:49:42 <karooga> ahah here we go
Dec 21 20:50:06 <karooga> "Nothing provides libav"
Dec 21 20:52:37 <karooga> Ug... http://paste.ubuntu.com/9591108/
Dec 21 20:53:48 <paulbarker> what branch of openembedded are you using?
Dec 21 20:54:03 <karooga> master AFAIK
Dec 21 20:54:17 <paulbarker> what commit?
Dec 21 20:54:30 <karooga> the docs said I should use the same releases if i have different repos.
Dec 21 20:54:33 <paulbarker> there was a fix a few hours ago
Dec 21 20:54:33 <karooga> Mmm...
Dec 21 20:54:41 <paulbarker> for something kernel related
Dec 21 20:55:00 <karooga> 88528a128fe7c
Dec 21 20:55:07 <karooga> LOL
Dec 21 20:55:10 <karooga> seriously?
Dec 21 20:55:47 <karooga> Let's see...
Dec 21 20:55:48 <paulbarker> yep
Dec 21 20:56:02 <karooga> That will be fantastic if it does fix it.
Dec 21 20:57:08 <karooga> I started the build process on friday and it only finished today :-)
Dec 21 20:57:18 <karooga> well fetch + build.
Dec 21 20:57:49 <paulbarker> I'd expect everything to rebuild if you update oe-core now
Dec 21 20:59:02 <karooga> ah wait, did you mean poky or oe-core?
Dec 21 21:00:00 <paulbarker> Either one, poky is automatically assembled from oe-core, meta-yocto and bitbake
Dec 21 21:01:14 <karooga> Oh, no - am I using this incorrectly then?  I have poky and then under poky I cloned oe-core, meta-raspberry meta-openembedded meta-browser
Dec 21 21:02:09 <paulbarker> you shouldn't have to clone oe-core separately
Dec 21 21:02:24 <paulbarker> but as long as it's not listed in BBLAYERS twice it won't do any harm
Dec 21 21:05:25 <karooga> Mm... I think I might have it twice: http://paste.ubuntu.com/9591191/
Dec 21 21:06:13 <karooga> I shouldn't need the last one,  right? openembedded-core/meta then?
Dec 21 21:13:51 <paulbarker> Yea you have it twice there, drop openembedded-core/meta as you said
Dec 21 21:14:41 <karooga> Cool :-)
Dec 21 21:15:06 <karooga> Gees, it's doing a massive pull on poky
Dec 21 21:16:07 <karooga> How could so much have changed since friday?
Dec 21 21:16:10 <paulbarker> Festive patch rush
Dec 21 21:16:42 <karooga> really?
Dec 21 21:16:43 <paulbarker> http://git.yoctoproject.org/cgit/cgit.cgi/poky/log/
Dec 21 21:17:49 <karooga> The deltas seem small though... ?
Dec 21 21:18:00 <timsche> hi guys, i'm building daisy for raspberrypi using meta-raspberrypi. i also want to build wayland and weston but when i
Dec 21 21:18:17 <timsche> weston fails to build saying no package egl and glesv2 found
Dec 21 21:18:30 <paulbarker> You have to consider dependencies... if one thing changes everything which depends on it usually gets rebuilt
Dec 21 21:18:47 <timsche> aren't egl and glesv2 shipped with the meta-raspberrypi?
Dec 21 21:21:49 <paulbarker> karooga: If you don't need to follow master so closely I'd recommend using the latest release branch which would be 'dizzy'
Dec 21 21:22:53 <paulbarker> You'll see less package churn that way. Changes to gcc, glibc, linux-libc-headers or other bottom-of-the-stack things often cause massive rebuilds
Dec 21 21:23:03 <karooga> Yeah, I considered that, but the docs said one should use the same branches across repos. meta-raspberrypi didn't have a dizzy.
Dec 21 21:24:10 <karooga> ah, I think I know why it's pulling down so much, it's getting all the other branches.  I only pulled master.
Dec 21 21:24:51 <paulbarker> meta-raspberrypi hasn't significantly changed August looking at the commit log
Dec 21 21:25:11 <paulbarker> I'd guess you can use meta-raspberrypi 'master' with everything else 'dizzy'
Dec 21 21:25:24 <karooga> mmm...
Dec 21 21:26:08 <karooga> meta-openembedded doesn't have a dizzy either.
Dec 21 21:26:13 <karooga> I lied.
Dec 21 21:26:18 <karooga> It does.
Dec 21 21:26:54 <karooga> Ok, let me finish the pull and then see...
Dec 21 21:28:45 <karooga> paulbarker: so in theory, have those entries in bblayers.conf and the INSTALL_IMAGE_append of chromium should be enough to get me through then?
Dec 21 21:29:10 <paulbarker> Yea it should be
Dec 21 21:29:59 <paulbarker> I must admit I've not used meta-raspberrypi in almost a year and I've never used meta-browser so I don't know the current state of either of those
Dec 21 21:30:58 <karooga> Seems like there's a little bit of house keeping to do.
Dec 21 21:31:07 <karooga> Perhaps I should consider pushing back.
Dec 21 21:31:35 <paulbarker> There was http://comments.gmane.org/gmane.comp.handhelds.openembedded/66204 on the mailing list a couple of months back
Dec 21 21:31:50 <paulbarker> I don't think it got a solution
Dec 21 21:32:47 <karooga> Yeah, I did actually see that.
Dec 21 21:33:19 <karooga> There is a cryptic comment at the end of the readme for meta-browser saying something about arm6.
Dec 21 21:33:21 <karooga> :-/
Dec 21 21:34:10 <karooga> A few months back I attempted to build chromium, "free style method" with the debian embedded project.
Dec 21 21:34:19 <karooga> That was horrible.
Dec 21 21:35:12 <karooga> Actually just building chromium is quite something, the sources along where GBs and build times took forever!!
Dec 21 21:35:41 <paulbarker> Yea, web browsers are huge. I remember firefox builds back in my Gentoo days :(
Dec 21 21:38:12 <karooga> did firefox run faster?
Dec 21 21:39:17 <paulbarker> haha
Dec 21 21:39:21 <karooga> I've been playing with emerge for the last few weeks with mingw... fun times, big builds!
Dec 21 21:40:33 <karooga> I hope this chromium thing isn't going to make tears for me again.
Dec 21 21:41:02 <karooga> I suspect it will though...
Dec 21 21:41:41 <paulbarker> You're probably best asking on the mailing list and Cc-ing Gary Thomas who last posted about chromium on raspberrypi
Dec 21 21:43:29 <karooga> Well let me run through the process this side, see how far I get...
Dec 21 21:43:52 <karooga> I think this pull is going to out live me tonight... will have to pick up tomorrow.
Dec 21 21:44:05 <karooga> Thanks for your help paulbarker.
Dec 21 21:46:15 <paulbarker> No problem, I'm still debugging patches so I'll be here a while!
Dec 22 01:52:14 <chankit> how does poky cross compile gcc application so it works in yocto?
Dec 22 01:52:26 <chankit> I mean the compiler itself
Dec 22 02:11:58 <behanw> chankit, Are you looking to run gcc on your target?
Dec 22 02:13:29 <behanw> Because gcc is built as a cross compiler by yocto in order to cross build everything else.
Dec 22 02:22:24 <chankit> behanw: yes
Dec 22 02:23:04 <chankit> and I checked gcc's recipes and I couldn't find any flag(s) that specifies cross compiling
Dec 22 02:24:21 <chankit> behanw: actually I want to get llvm+clang to work on yocto but for some reason the yocto system cannot execute the code that my clang compiles
Dec 22 02:25:18 <chankit> so I suspect that there are some cross-compile thingy that I need to sort out and since gcc is a compiler as well...I'm studying gcc's cross compilation case so hopefully I can apply them to clang as well
Dec 22 02:27:31 <chankit> when I mean my clang, I mean the yocto can run clang to compile code but it cannot run the produced binary
**** ENDING LOGGING AT Mon Dec 22 02:59:58 2014