**** BEGIN LOGGING AT Thu Jul 28 02:59:58 2016
Jul 28 03:30:22 <pwebster> @bluelightning: Found the first clue to the problem. The recipe uses the ${WORKDIR} variable extensively wherever a source directory is used, ie in OE_CMAKESOURCEPATH, in a do_configure_prepend and even in the arguments passed to cmake. Is there a better variable to use that will be updated when EXTERNALSRC is set for the recipe or do I need to implement some kind of local "if EXTERNALSRCE is set then..." check?
Jul 28 03:32:57 <bluelightning> pwebster: it should really be using ${S}
Jul 28 03:33:34 <bluelightning> then it should work fine with externalsrc
Jul 28 03:41:15 <pwebster> yep, thanks, was just about to say that I found the solution :D
Jul 28 03:46:18 <pwebster> WORKDIR was used because it was referred to a lot in different examples of recipe writing, not explicitly in the things we are doing in the recipe, but the assumption was it was what should be used. And it worked, until I needed to build from an external source.
Jul 28 03:47:08 <pwebster> Thanks again for your help
Jul 28 09:08:28 <mckoan> good morning
Jul 28 09:11:44 <CTtpollard> morning mckoan
Jul 28 12:06:39 <sveinse> No kidding about test-dependencies.sh taking a lot of time.. 9 hrs to be exact...
Jul 28 12:07:06 <sveinse> But I think maybe the script went haywire... It tried to bitbake every word in my comments
Jul 28 12:12:31 <mathieu_la> Hi, I'm getting the taskhash mismatch error with meta-raspberrypi, I just updated to a new revisionn.
Jul 28 12:12:50 <mathieu_la> going back to commit 6564e126aea0ac42a129595c79218ba69f8095eb works
Jul 28 14:12:04 <mathieu_la> possibly stupid question : I have some image recipe on my meta-folder depending on some machine image. Now I would like to port the project to a new machine, do I need to include the first machine layer? or is there a way to blacklist those recipes?
Jul 28 14:44:44 <boucman_work> mathieu_la: there is a way of specifying that a recipe is only valid on certain MACHINE, but i'm not sure what it is...
Jul 28 14:45:02 <rburton> COMPATIBLE_(MACHINE/HOST)
Jul 28 14:45:07 <boucman_work> thx
Jul 28 14:46:20 <RP> kergoth: did you see the delete variable syntax patch ?
Jul 28 14:55:19 <mathieu_la> cool, thanks
Jul 28 15:03:14 <HyP3r> Hey all, I'm working with http://developer.toradex.com/knowledge-base/board-support-package/openembedded-(core) in combination with a toradex vf61 board, now I want to add to my kernel a wireless driver
Jul 28 15:03:34 <HyP3r> In my case this module: https://www.bluegiga.com/en-US/products/wf111-wifi-module/
Jul 28 15:03:41 <HyP3r> Whats the correct way to do this?
Jul 28 15:05:27 <HyP3r> Inside my Yocto folder structure I have the folder oe-core/build/out-glibc/work-shared/colibri-vf/kernel-source which seems to be the kernel directory
Jul 28 15:05:55 <HyP3r> This driver I have found allows me to patch an exisiting kernel source, but I think this is not the correct way
Jul 28 15:06:07 <boucman_work> HyP3r: is the kernel driver supported by toradex's kernel (i.e you just need to change an option)
Jul 28 15:06:12 <boucman_work> is it an external module ?
Jul 28 15:06:15 <boucman_work> is it a patch ?
Jul 28 15:06:50 <boucman_work> HyP3r: yocto can apply patches to kernels, but the patch needs to be for the same version of the kernel, did you check that ?
Jul 28 15:06:51 <HyP3r> boucman_work: I'm able to compile it as module extern, and I'm able to patch an existing kernel
Jul 28 15:07:21 <HyP3r> In my strategy was this the next step: checkig if compatible
Jul 28 15:07:26 <HyP3r> I don't know how to find that out
Jul 28 15:07:39 <HyP3r> my kernel has 4.1.15
Jul 28 15:07:55 <boucman_work> maybe check here : http://www.yoctoproject.org/docs/2.1/kernel-dev/kernel-dev.html#incorporating-out-of-tree-modules
Jul 28 15:18:41 <HyP3r> boucman_work: but in this case the driver would be compiled as external kernel module, is that correct?
Jul 28 15:20:26 <HyP3r> What if I want to patch the kernel with that driver? So I can bind the driver into the kernel
Jul 28 15:21:12 <boucman_work> you can patch a kernel with a bbappend like any other recipe
Jul 28 15:21:28 <boucman_work> http://www.yoctoproject.org/docs/2.1/kernel-dev/kernel-dev.html#applying-patches
Jul 28 15:39:52 <RP> armpit: I just fixed up the meta-qt4 branches with the fixes FWIW
Jul 28 15:44:10 <armpit> RP, thanks
Jul 28 15:47:42 <Technicus> Hello, I am trying to figure out how to recompile the yocto kernel following this: < https://www.yoctoproject.org/sites/default/files/elc2013-kernel-lab.pdf >.  I am trying to add this module: < http://modules.libres.ch/browse/linux/v3.1/i386/snd-virmidi/ >.  Am I following the right path by following this lab?
Jul 28 16:57:08 <bryn_> hi
Jul 28 17:25:02 <dmiess> Hi. I'm trying to write a recipe which will incorperate artifacts from a few other recipies. For instance, I want to be able to package a kernel which was produced from a previous recipe. How do I get access to these files?
Jul 28 17:25:19 <dmiess> All the files I need are in the RPM that was created by the kernel build
Jul 28 17:57:40 <khem> dmiess: usually recipe is a unit which is best to provide the final packaging content that it wants to expose to packager
Jul 28 17:57:57 <khem> dmiess: whats your motivation to write such a recipe ?
Jul 28 17:58:13 <khem> which seems to be a semi meta recipe
Jul 28 17:58:20 <khem> when it comes to packaging
Jul 28 17:59:32 <dmiess> I have a tool which is used for flashing the firmware onto a board. My thought was that I would write a recipe which would collect a kernel, dtb, u-boot and initramfs and then package them together with this tool + libraries
Jul 28 18:00:48 <dmiess> In the end I'm hoping to create a zip file which contains all these components
Jul 28 18:02:26 <khem> there already are tools like that in yocto
Jul 28 18:02:38 <khem> please try to use those
Jul 28 18:03:11 <dmiess> What are the names of these tools?
Jul 28 18:10:35 <moto-timo> http://www.yoctoproject.org/docs/2.1/mega-manual/mega-manual.html
Jul 28 18:10:48 <moto-timo> look at 5.8 Creating Partitioned Images
Jul 28 18:13:44 <dmiess> I'm not sure this is what I'm looking for. Ultimately I just want to take a zip file, extract it, add this kernel and related files into the directory structure and create a new zip file. I don't want to be creating any kind of partition table
Jul 28 18:15:24 <rburton> what you're describing is how to create an image, but without the final "make a disk image" bit
Jul 28 18:15:37 <rburton> which conveniently is trivial as thats exactly what an initramfs is
Jul 28 18:16:05 <seebs> Yeah, if you take the instructions for building a disk image containing a particular set of things, but at the end sub in "zip" for "mkfs" or whatever...
Jul 28 18:18:07 <dmiess> So in that case my recipe would just start with inherting core-image-minimal and each piece I need would be defined as a package?
Jul 28 18:18:49 <dmiess> or core-image-base I guess?
Jul 28 18:39:39 <dmiess> Is there an example anywhere of an "empty" image which doesn't pull in anything?
Jul 28 19:05:18 <dmiess> I think I have an empty image set up. Right now I'm testing it by trying to include a kernel and nothing else but I'm getting the error: "Can't install kernel-image-3.14.28-1.0-r0@imx6dlsabresd: no package provides /bin/sh"
Jul 28 19:05:44 <dmiess> Since I'm just creating a zip file I really don't want to have to install a shell though, is there a way around this?
Jul 28 19:59:59 <Technicus> In this lab < https://www.yoctoproject.org/sites/default/files/kernel-lab-1.4.pdf > it is using poky-dylan-9.0.0, can I use poky-krogoth-15.0.0?
Jul 28 20:14:35 <RP> kergoth: around?
Jul 28 20:52:39 <denix> can I force copying objects from file:// based SSTATE_MIRROR the same way as http:// based ones, instead of symlinking them?
Jul 28 21:47:39 <RP> denix: probably not without changing the fetcher
Jul 28 21:48:26 <RP> Technicus: there have been a lot of changes since then.  think there should be a more recent version of the kernel lab for later versions of the project
Jul 28 21:49:08 <Technicus> RP: I have not been able to find one.  I am quite new to compiling Yocto, or Kernels even.
Jul 28 21:49:37 <denix> RP: thanks
Jul 28 21:54:19 <RP> Technicus: https://www.yoctoproject.org/training/kernel-lab the 2.1 version would be krogoth
Jul 28 21:57:43 <Technicus> Awesome!!!
**** ENDING LOGGING AT Fri Jul 29 02:59:58 2016