**** BEGIN LOGGING AT Mon Sep 29 02:59:58 2014
Sep 29 06:41:44 <mckoan> good morning
Sep 29 06:54:41 <Nilesh_> Good morning
Sep 29 07:29:48 <mckoan> hi Nilesh_
Sep 29 08:33:02 <bluelightning> morning all
Sep 29 08:33:08 <Net147> bluelightning: morning
Sep 29 08:33:14 <bluelightning> hi Net147
Sep 29 08:33:51 <Net147> bluelightning: hi bluelightning
Sep 29 08:36:37 <LetoThe2nd> (UMT)
Sep 29 10:09:29 <laberschwall> hi there
Sep 29 10:14:12 <laberschwall> I have a small question for. I am using QT5 meta and a embedded device without OpenGL. After I run a QTQick Hello World application there is a missing libqt5declerative library. So I checked the receipes and found a message that gl or gles must be set to compile this lib. The lib is not found in my open embedded folders after a successful image compile. I read that I can force this opengl and all works fine, but I did not under
Sep 29 10:15:16 <laberschwall> With WinCE the same QT Quick app runs fine, no GL needed.
Sep 29 11:13:28 <Net147> bluelightning: u-boot is contained in my image because the image class is an SD image. is there a way of specifying that u-boot is a part of the image and should be included in the manifest?
Sep 29 11:14:32 <bluelightning> Net147: by "contained in the image" I mean it's a package installed within the filesystem for the image
Sep 29 11:15:50 <bluelightning> Net147: when you create your SD image is that within the build system, or does combining the bootloader to produce the final SD card image happen as an additional step?
Sep 29 11:16:44 <Net147> bluelightning: the image class creates an image file, the partition layout and the boot loader is copied before the first partition. it's all contained in the image class.
Sep 29 11:18:24 <Net147> bluelightning: does it get picked up if IMAGE_DEPENDS has u-boot? like in https://github.com/djwillis/meta-raspberrypi/blob/master/classes/sdcard_image-rpi.bbclass
Sep 29 11:18:32 <bluelightning> no
Sep 29 11:18:51 <bluelightning> AFAIK there is no means of doing this right now, other than to add an additional pseudo-package to the u-boot recipe which contains nothing but enables u-boot to be in the list of packages installed into the image
Sep 29 11:22:35 <Net147> I think it's important to have a mechanism to add licensing information for the boot loader and other packages that are part of the image but not necessarily part of the root filesystem
Sep 29 11:23:08 <bluelightning> Net147: I guess that's what your bug covers then
Sep 29 11:23:26 <Net147> bluelightning: yes
Sep 29 11:24:55 <Net147> bluelightning: I am not sure if the source archiver is affected by the same issue
Sep 29 11:26:18 <bluelightning> someone would need to check, but I think the source archiver operates on the basis of what is built rather than what is contained in a particular image
Sep 29 11:29:37 <Net147> bluelightning: can the archives generated by the source archiver be fed back into the build system for creating images?
Sep 29 12:38:54 <bluelightning> Net147: not directly, no... certainly not without the metadata
Sep 29 12:43:10 <Net147> bluelightning: I am just wondering what is the use for the archiver if it can't be used with the build system to meet license requirements, for example if you distribute a CD for offline builds for meeting licensing requirements.
Sep 29 12:43:48 <bluelightning> Net147: different organisations (and probably jurisdictions) have different ideas about what is required in order to be compliant
Sep 29 12:44:25 <bluelightning> naturally the ultimate would be to just ship your DL_DIR and the metadata
Sep 29 12:44:37 <bluelightning> (although there's no filtering for that...)
Sep 29 12:44:57 <Net147> bluelightning: I think in GPL for example requires the scripts to reproduce the binaries
Sep 29 12:45:31 <Net147> bluelightning: which would includes all the extra flags, patching, packaging that Yocto does
Sep 29 12:45:33 <bluelightning> right, but are those scripts the makefiles? or the recipes? what about the distro config? ...
Sep 29 12:45:57 <Net147> bluelightning: well you can't reproduce the binaries as they are in the image with the source tarballs alone
Sep 29 12:46:01 <Net147> bluelightning: you need the build system
Sep 29 12:46:13 <bluelightning> not necessarily
Sep 29 12:46:53 <bluelightning> if you have the source, all applied patches, and all the commands we used to build them, that should be sufficient (note: not a lawyer, not legal advice, etc.)
Sep 29 12:47:11 <Net147> bluelightning: okay. but the archiver does not include the commands?
Sep 29 12:47:30 <bluelightning> don't know, I haven't dealt much with the archiver
Sep 29 12:48:36 <bluelightning> my advice would be, use the archiver to ship the required source, and then just publish your metadata alongside it
Sep 29 12:48:58 <Net147> bluelightning: I think the best way would just be to run the clean checkout of the build on a different system and do a fetchall if you want do be able to do an offline build and distribute it
Sep 29 12:49:07 <Net147> bluelightning: but of course, no filtering based on LICENSE
Sep 29 13:08:48 <gebreselaisi> hi guys
Sep 29 13:09:00 <gebreselaisi> yocto cannot apply patches that contain images?
Sep 29 13:09:07 <gebreselaisi> it says binary diff not supprted
Sep 29 13:20:33 <bluelightning> gebreselaisi: by default no... you can try setting PATCHTOOL = "patch" within the recipe though
Sep 29 13:20:39 <gebreselaisi> I see
Sep 29 13:20:41 <gebreselaisi> let me try that
Sep 29 13:20:42 <gebreselaisi> thanks
Sep 29 13:22:02 <gebreselaisi> I have patch version 2.7.1
Sep 29 13:22:04 <gebreselaisi> but same error
Sep 29 13:24:48 <bluelightning> gebreselaisi: hmm... what about PATCHTOOL = "git" ?
Sep 29 13:24:49 <gebreselaisi> looking in the output created by bitbake -e I still see PATCHTOOL = quilt
Sep 29 13:25:00 <bluelightning> gebreselaisi: bitbake -e or bitbake -e recipename?
Sep 29 13:25:01 <gebreselaisi> it does not seem to parse my recipe
Sep 29 13:25:06 <gebreselaisi> -e recipename
Sep 29 13:25:42 <gebreselaisi> it sets it based on just poky/meta/conf/bitbake.conf
Sep 29 13:25:46 <bluelightning> when you do bitbake -e | grep ^FILE= is it the same file you are editing?
Sep 29 13:25:52 <gebreselaisi> does not look into my recipe where I set PATCHTOOL = patch
Sep 29 13:26:29 <bluelightning> well, bitbake -e recipename | grep ^FILE=
Sep 29 13:29:25 <gebreselaisi> bluelightning, silly me, I was in th wrong layer doing the changes
Sep 29 13:29:31 <gebreselaisi> it works now
Sep 29 13:29:33 <gebreselaisi> but with git
Sep 29 13:29:34 <gebreselaisi> not patch
Sep 29 13:29:36 <gebreselaisi> thanks a lot
Sep 29 13:29:37 <bluelightning> right
Sep 29 13:29:39 <bluelightning> no worries
Sep 29 13:51:34 <gebreselaisi> so I have a qt dir inside my package
Sep 29 13:51:39 <gebreselaisi> which contians the .pro file
Sep 29 13:51:45 <gebreselaisi> so I try to do a:
Sep 29 13:51:50 <gebreselaisi> do_configure()
Sep 29 13:51:55 <gebreselaisi> in which I cd to that dir
Sep 29 13:52:05 <gebreselaisi> and then : qmake5_base_do_configure
Sep 29 13:52:12 <gebreselaisi> apparently it cd's into that dir
Sep 29 13:52:29 <gebreselaisi> but then it errors out because it searches for a .pro file in ${S}
Sep 29 13:54:17 <gebreselaisi> any idea why it is jumping out of the dir I cd'ed into?
Sep 29 13:55:27 <bluelightning> gebreselaisi: it explicitly looks in ${S}
Sep 29 13:55:58 <bluelightning> gebreselaisi: alternatively you can explicitly specify the profile file(s) to build by setting QMAKE_PROFILES
Sep 29 13:59:09 <gebreselaisi> right
Sep 29 13:59:12 <gebreselaisi> thanks again
Sep 29 20:40:17 <hramrach_> hello
Sep 29 20:40:42 <hramrach_> I am trying to build mb-stroke-applet
Sep 29 20:40:53 <hramrach_> this requires some mbstroke library
Sep 29 20:41:00 <hramrach_> but where is that library?
Sep 29 20:42:07 <hramrach_> http://git.yoctoproject.org/cgit/cgit.cgi/matchbox-stroke/ is the onle repo with stroke in name on http://git.yoctoproject.org/
Sep 29 21:30:40 <ant__> zeddii: ping
Sep 30 00:11:09 <victhor> hi, I'm trying to build with icecream and I get some libraries missing, which means I can't complete the build. http://pastebin.com/fCbpTxQF
Sep 30 00:11:51 <victhor> the build completes without any problems with icecream disabled, so it's a build environment problem for the icecream clients. How do I add those libraries to it?
**** ENDING LOGGING AT Tue Sep 30 02:59:58 2014