**** BEGIN LOGGING AT Fri Jun 20 03:00:00 2014
Jun 20 04:59:36 <jags> I have built yocto for imx6sl_evk board, but i am not able to find uboot and kernel source code inside it. Where is should be?
Jun 20 04:59:46 <jags> i have built daisy branch.
Jun 20 07:40:36 <mckoan> good morning
Jun 20 10:25:40 <gatis> Hello, I was wondering if there is a way to see the "final assembled recipe"? The way it would look after all foo.bb foo.bbappend are put together.
Jun 20 11:21:12 <gatis> or how can i see every command executed when baking a recipe? It seems to stay forever in "do_fetch" so i would like to see where it gets stuck
Jun 20 11:24:59 <ndec> gatis: bitbake generates script for each task based on each recipe. then running a task is just executing the script.
Jun 20 11:25:03 <ndec> the scripts are shell or python
Jun 20 11:25:20 <ndec> you can look at these scripts in the 'temp' folder in each component WORKDIR
Jun 20 11:27:23 <gatis> ndec, cool, thanks for the explanation, will take a look at the scripts
Jun 20 15:31:54 <jmleo> Hi all !
Jun 20 15:32:38 <jmleo> I am developing a new board, using Yocto, and I am wondering how to automate a build. My main problem is how to create a bblayers.conf
Jun 20 15:32:42 <jmleo> I do a repo init
Jun 20 15:32:43 <jmleo> repo sync
Jun 20 15:33:04 <jmleo> and after that I have to source a setup environment
Jun 20 15:33:26 <jmleo> which creates a build directory and then I have to create a conf/bblayers.conf file
Jun 20 15:34:04 <jmleo> what is the recommended way ? Create a meta which contains this file, and when sourcing, it copies the file ?
Jun 20 15:34:13 <fray> file should be created when you do the oe-init-build-env script.. configure it once and you should be ok
Jun 20 15:34:38 <fray> yes.. create a script or modify it in a similar way as the oe-init-build-env to copy your default preconfigured
Jun 20 15:35:09 <jmleo> fray, the question is how to distribute it after, for the team, when they do a repo init and repo sync, they source the oe-init-build-env and that's all, no need to modify bblayers
Jun 20 15:35:41 <fray> yes, you want to create a custom version.. there may already be hooked in there to pull a special version.. you'll have to trace it
Jun 20 15:36:51 <jmleo> ok, thx that's clear
Jun 20 18:09:23 <volker-> let's say your company has one base-system (user management, basic network config etc) and creates two products out of it. Do you create 1.) two distros based on the same image or 2) two images based on one distro?
Jun 20 18:09:47 <Crofton> I would go with 2
Jun 20 18:10:01 <fray> both are reasonable, but I agree go with two..
Jun 20 18:10:06 <fray> configure one distro and multilib imges
Jun 20 18:10:22 <Crofton> well, unless 1 works better for your specific case :)
Jun 20 18:13:12 <volker-> I think the benefit with 2) is that you can run bitbake with 'bitbake <image1> <image2>'. I havent seen an option running "bitbake <distro1-image1> <distro2-image2>"
Jun 20 18:13:43 <volker-> I think I did the mistake adding the packages to the distro in the past, but that should be a smaller fix to move them to the image configuration
Jun 20 18:16:08 <Crofton> changes to distro.conf are likely to force long rebuilds
Jun 20 18:16:23 <Crofton> and ahrd to share build output across images when distro changes
Jun 20 18:16:48 <volker-> no official release yet, so that part doesn't matter at the moment
Jun 20 18:17:15 <volker-> and the build system builds everything from scratch anyway
Jun 20 18:21:44 <volker-> Crofton:  I do not see how packages got rebuild. Nothing changes beside moving the IMAGE_INSTALL_append from the distroconf to imageconf. Only the image itself gets re-created (which would have been usually skipped because there where no changes.
Jun 20 18:21:53 <volker-> s/got/get/
Jun 20 21:43:42 <volker-> does anyone using ecryptfs on yocto? There is a package in meta-ivy, I try to use it on x86 at the moment
Jun 21 01:16:17 <zman97211> I'm looking for assistance setting up my layer to apply a kernel configuration fragment to the meta-raspberrypi's kernel. The Yocto dev manual (section 5.6.2) isn't super clear about this.
Jun 21 01:26:02 <zman97211> The recipe providing the kernel in my image is /home/steve/pi/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi_3.12.21.bb
Jun 21 01:27:30 <zman97211> I created in my layer recipes-kernel/linux/linux-raspberrypi_3.12.21.bbappend. It has one line, "SRC_URI += "file://linux-steve.cfg"
Jun 21 01:27:59 <zman97211> My fragment is at recipes-kernel/linux/linux-raspberrypi/linux-steve.cfg
Jun 21 01:28:32 <zman97211> The bbappend file is not parsing. "ERROR: ParseError at /home/steve/pi/meta-steve/recipes-kernel/linux/linux-raspberrypi_3.12.21.bbappend:1: unparsed line: 'SRC_URI += "file://linux-steve.cfg'"
Jun 21 01:28:46 <zman97211> Can anyone help?
Jun 21 01:29:47 <zman97211> I'm obviously doing something incorrectly.
Jun 21 01:31:48 <zman97211> Never mind! I was missing an ending quote.
Jun 21 01:31:59 <zman97211> The parser could provide a better error LOL
Jun 21 01:34:11 <kergoth> agreed
**** ENDING LOGGING AT Sat Jun 21 03:00:00 2014