**** BEGIN LOGGING AT Mon Feb 29 02:59:58 2016 Feb 29 08:03:40 good morning Feb 29 11:28:08 hi Feb 29 11:28:34 who can answer my question Feb 29 11:39:43 "what is the answer to life, the universe and everyhing?" Feb 29 11:39:49 i can. Feb 29 11:39:50 42 Feb 29 11:40:24 ok, it is about how to use bitbake Feb 29 11:40:49 i put file in rootfs folder, how to bitbake it to image, n Feb 29 11:41:21 write a recipe to automate it, put recipe in a layer, have your image recipe install it. Feb 29 11:41:28 now after i bitbake these file is not in image, so maybe what parameter is needed to accomplish it Feb 29 11:41:50 if no recipes, can i acchieve it? Feb 29 11:42:03 the short answer is: no Feb 29 11:43:02 but rootfs is there, just compress it to a image, so i think maybe it is possible Feb 29 11:43:18 just need to find a parameter for bitbake Feb 29 11:43:20 well its only software, everything is possible. Feb 29 11:43:33 but magically stuffing a file into a rootfs has nothing to do with bitbake. Feb 29 11:43:40 bitbake bakes recipes. Feb 29 11:44:38 so what do these rootfs folder do in tmp/../xxx-..-gnueabi/1.0-r0/ Feb 29 11:44:47 if you totally believe that you will not write a recipe, then write a script that does whatever you want. but leave bitbake out of the game then. Feb 29 11:45:34 no, i mean i just need do: bitbake -option core-image-minimal, Feb 29 11:45:50 i repeat - bitbake does *not* work like that. Feb 29 11:45:59 ok, thanks for reply Feb 29 11:56:57 ok, i ask another question Feb 29 11:57:40 (you Feb 29 11:57:56 now i write recipes, and i copy file from recipes folder to rootfs/home/root/, how to do Feb 29 11:58:06 (you'll* probably end up with your own layer and a few recipes, like everyone else) Feb 29 11:58:30 yes, i use own layer and recipes Feb 29 11:59:15 but dont know how to copy a file like 1.bmp to image folder like /home/root/ Feb 29 12:00:06 usually you just put the files in the recipe folder and at it to FILES Feb 29 12:00:08 add* Feb 29 12:00:22 in some cases (conf files for other packages) this won't work Feb 29 12:02:02 yes, i put it in FILES, Feb 29 12:04:37 basically this is waht you want: Feb 29 12:04:38 http://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#packaging-externally-produced-binaries Feb 29 12:05:10 and for the generic recipe infrastructure, use http://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#new-recipe-single-c-file-package-hello-world Feb 29 12:06:31 the problme is i dont need to compile, ur example is after complie and a exceute file put into work folder, then install from work folder to image folder, but i need to install from recipes folder to image folder Feb 29 12:06:46 it is just photo file, Feb 29 12:06:49 1.bmp Feb 29 12:06:58 so dont need to compile, Feb 29 12:07:16 if it can be put into work folder, i think it is fine, Feb 29 12:07:20 zxc678: just do a mental transition from "externally produced binary" to "externally produced image" Feb 29 12:07:27 and then read the link again. Feb 29 12:30:36 ok, I read the link, that is what i want, but i still 2 questions, 1 is FILE_${PN}="file://1.bmp" and 2 is how to write do_install, do_install { install -m 1.bmp ${D}/home/root} is right? Feb 29 12:30:58 these 2 sententse are right or not? Feb 29 12:32:04 FILE_${PN}="file://1.bmp" and do_install { install -m 1.bmp ${D}/home/root} Feb 29 12:32:30 i put 1.bmp in recipes folder Feb 29 12:34:00 FILES, not FILE Feb 29 12:34:42 yes,FILES, Feb 29 12:35:01 besides that "go ahead and find out" Feb 29 12:38:09 what do these FILES_${PN} do? what is difference between FILES and SRC_URL Feb 29 12:38:51 files means what is installed. see: http://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#var-FILES Feb 29 12:39:30 src_uri means where it comes from http://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#var-SRC_URI Feb 29 12:40:13 zxc678: that manual page really maintained very well, and about every noteworthy expression properly hyperlinked to its explanation. i suggest you have a good look at it. Feb 29 13:12:25 hi, I put file in recipes folder, can I write FILE_$[PN]="file://1.bmp", after bitbake error is cannot stat'1.bmp': no such file or directoy so how to write the folder for recipes folder Feb 29 13:13:15 zxc678: No you need to bring the file in via SRC_URI first, and then install it, after which FILES_${PN} will allow you to define the package to put it in. Feb 29 13:13:54 yes, i use FILES_${PN}, not use SRC_URI Feb 29 13:14:33 you have to use both to do what you are trying to do Feb 29 13:15:00 SRC_URI += "file://1.bmp" Feb 29 13:15:13 ok, i will try Feb 29 13:15:24 do_install { install ${S}/1.bmp ... } Feb 29 13:15:49 FILES_${PN} += "//1.bmp" Feb 29 13:17:56 You can use an existing recipe as an example, e.g. http://git.openembedded.org/openembedded-core/tree/meta/recipes-core/sysvinit/sysvinit-inittab_2.88dsf.bb although it does a bit more than just as single file. Feb 29 13:45:18 l: command not found Feb 29 13:45:49 fsl-community-bsp/build/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/lvds/0.1-r0/temp/run.do_install.21674: line 102: instasl Feb 29 13:45:49 l: command not found Feb 29 13:54:46 is anyone else seeing bitbake errors (looks like from cookerdata.py) during parsing? Feb 29 13:54:57 on a recently pulled master Feb 29 13:59:20 is it about sanity checks? Feb 29 13:59:25 in that case re-pull latest master Feb 29 14:00:49 zxc678: "instasll not found" sounds about valid to me. Feb 29 14:09:05 what is instasll, why not install Feb 29 14:09:45 did a directory in git.openembedded.org/poky get renamed recently? from meta-poky-bsp to meta-yocto-bsp? Feb 29 14:10:25 its always been meta-yocto-bsp Feb 29 14:10:56 in poky master-next, meta-yocto is now meta-poky Feb 29 14:11:21 oh it landed in master :) Feb 29 14:11:37 there it is :-) thanks Feb 29 14:22:46 zxc678: you said install, not me. basically, check your recipe for typos. Feb 29 14:49:35 ok, it compile successful and i bitbake core-image-minimal too, but i dont find it in /home/xjh/fsl-community-bsp/build/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/lvds/0.1-r0/ Feb 29 14:50:06 ./home/root Feb 29 14:50:55 so the 1.bmp still not is cp into its folder? Feb 29 14:51:48 if success, 1.bmp should exist in the folder, right? Feb 29 15:24:14 rburton: what's funny is, the only reason i have meta-{poky|yocto}-bsp is because of the dependency of meta-intel :-) has that been resolved yet? Feb 29 15:29:44 I added meta-intel to a no distro setup and it worked Feb 29 15:32:49 tlwoerner: good question Feb 29 15:33:48 looks like gma500_gfx still depends on meta-poky via a bbappend Feb 29 15:33:56 tlwoerner: can you file a bug and cc me please Feb 29 15:41:06 hi Feb 29 15:41:43 i have question ,hope to get answer Feb 29 15:43:53 i create a layer and recipes, compile well, set IMAGE_INSTALL+= Feb 29 15:44:39 rburton: ok Feb 29 15:44:46 "lvds", then bitbake core-image-minimal, no any error Feb 29 15:45:14 ,but dont find file in /home/root Feb 29 15:46:03 so any file can let me know where the file is installed or what error happened Feb 29 15:46:57 i think a log file should tell me, which is it? that is my question Feb 29 15:57:48 sleep Feb 29 16:53:12 hi, all! Feb 29 16:54:30 if I build core-image-x11, my MACHINE_EXTRA_RRECOMMENDS is ignored, so kernel modules are not installed. How can I fix that except for explicitly specifying all kernel-module-* stuff? Feb 29 16:57:36 slapin: using bitbake core-image-x11 -e to see why it's being overwritten Feb 29 17:02:39 rburton: the value is there, but it is not used by core-image-x11 Feb 29 17:03:24 rburton: MACHINE_EXTRA_RRECOMMENDS is proper in environment Feb 29 17:03:52 slapin: packagegroup-machine-base is where that ends up via packagegroup-base Feb 29 17:05:00 which ends up in core-image via CORE_IMAGE_BASE_INSTALL Feb 29 17:05:06 rburton: packagegroup-base is not used, only packagegroup I see is packagegroup-core-x11-base (which doesn't reference packagefroup-base) Feb 29 17:05:16 so it should be present Feb 29 17:05:54 rburton: packagegroup-base is not built when core-image-x11 is built... Feb 29 17:06:05 would be here Feb 29 17:06:09 IMAGE_INSTALL=" packagegroup-core-boot packagegroup-base-extended " Feb 29 17:06:19 -base-extended depends on -base Feb 29 17:07:15 rburton: packagegroup-base is not referenced in task-depends.dot Feb 29 17:07:35 rburton: neither is packagegroup-base-extended Feb 29 17:08:30 works here Feb 29 17:08:54 $ bitbake core-image-x11 Feb 29 17:08:54 Missing or unbuildable dependency chain was: ['core-image-x11', 'packagegroup-base-extended', 'fhsfhdhf'] Feb 29 17:09:01 (lots deleted) Feb 29 17:10:59 rburton: grep packagegroup pn-depends.dot -> https://gist.github.com/5b672e68bb657fe727c6 Feb 29 17:12:55 rburton: HEAD is 390bad905537820f49add855c95d726b5b55c8fa Feb 29 17:13:06 rburton: for openembedded-core Feb 29 17:14:48 rburton: how can I debug this? Feb 29 17:16:55 slapin: double-check what bitbake -e says for a start Feb 29 17:26:33 rburton: https://gist.github.com/anonymous/46b71015b6647970b3a5 Feb 29 17:29:07 rburton: that wone was truncated... Feb 29 17:30:29 rburton: http://ossfans.org/bitbake-e.txt Feb 29 17:31:06 rburton: the value for MACHINE_EXTRA_RRECOMMENDS is ok Feb 29 17:31:26 IMAGE_INSTALL=" systemd-compat-units udev systemd busybox base-passwd shadow" Feb 29 17:31:33 yeah you shouldn't override IMAGE_INSTALL Feb 29 17:33:34 looks like angstrom is breaking that for you Feb 29 17:33:55 rburton: I only do this: https://gist.github.com/7b68ca668d2fb255ed40 in core-image-x11.bbappend Feb 29 17:34:19 rburton: where? Feb 29 17:34:37 # append /home/slapin/OE-aw/sources/meta-angstrom/conf/distro/include/angstrom-core-tweaks.inc:95 Feb 29 17:34:58 assigns to IMAGE_INSTALL so the core-image class can't set the default Feb 29 17:35:09 look at the IMAGE_INSTALL block in your -e output Feb 29 17:37:28 rburton: ah, so I can just add IMAGE_INSTALL += "${MACHINE_EXTRA_RRECOMMENDS}" to .bbappend Feb 29 18:21:04 ouch, koen stop breaking things in Angstrom config files Feb 29 18:22:53 I admit doing a quick scan of meta-angstrom earlier to see if something was messing with core-image, but didn't think to look there Feb 29 18:24:58 rburton, https://github.com/Angstrom-distribution/meta-angstrom/blob/master/conf/distro/include/angstrom-core-tweaks.inc#L95 Feb 29 18:25:20 I see += Feb 29 19:53:02 morning all Feb 29 19:54:34 gm Feb 29 20:20:25 gm all Feb 29 20:20:30 rpi3 wow Feb 29 20:20:34 nice stuff Feb 29 20:21:02 https://www.element14.com/community/community/raspberry-pi Feb 29 20:30:54 khem: ooh Feb 29 20:36:11 hmmmm Feb 29 20:38:25 Crofton|work: yes, and core-image uses ?= Feb 29 20:38:38 (and always has) Feb 29 20:38:40 ah Feb 29 20:38:58 so once you touch it, core-image will not use it? Feb 29 20:46:14 yeah Feb 29 20:46:21 core-image uses IMAGE_INSTALL ?= ... Feb 29 20:46:34 so if you set that explicitly then you override the class Feb 29 20:49:21 which is why users should use CORE_IMAGE_EXTRA_INSTALL and never set IMAGE_INSTALL in local.conf at all, since the latter requires them to use _append, so is error prone Feb 29 20:49:32 explicit hooks are best for such things Feb 29 20:56:42 indeed Feb 29 20:56:52 my local.conf is 50% CORE_IMAGE_EXTRA_INSTALL lines Feb 29 21:03:31 * kergoth wants to see, long term, all bbclasses sourced before all recipe lines. if the recipe doesn't want to override the class, it can use ?=, then where the inherit line is wouldn't matter, and classes wouldn't ever use ?= unless they want *config metadata* to override them, not the recipe, clarifying usage Feb 29 21:04:38 Crofton: bmaptool looks handy, should get wic writing out a map Feb 29 21:04:58 I think rburton or someone has looked at that :) Feb 29 21:05:18 even without he map, it is faster than dd and avoids to writing a mounted card mistake Feb 29 21:05:32 finally, some good comes out of tizen :) :) Feb 29 21:05:38 wic doesn't write at all. maybe you're talking about imagewriter or ddimage? Feb 29 21:06:02 and bmaptool seems to do more than just sanity check, it distinguishes between zeroed areas we need and ones we don't, so it writes fast without ending upw ith a corrupted filesystem Feb 29 21:06:13 I know, but having wic create the bmap file would be handy Feb 29 21:06:13 https://source.tizen.org/documentation/reference/bmaptool/introduction Feb 29 21:06:14 bmap-tools was moderately interesting but you need images with proper sparseness and i mostly write hddimg which isn't very spare at all Feb 29 21:06:27 so i got a usb3 stick for my main testing and said goodbye to delays Feb 29 21:06:36 easily writes 1gb in 10 seconds Feb 29 21:06:50 I also need wic to let me have fine control over partitions Feb 29 21:06:54 i often write 8gb sd card images, and use wks files with the rootfs as large as possible for that size to avoid resizing at runtime Feb 29 21:07:03 which is a case where sparseness *really* helps Feb 29 21:07:48 doesn't wic already give you fine control over partitions, just write a wks the way you want it? Feb 29 21:08:16 I need to revisit this :) Feb 29 22:14:31 is there any particular reason Qt5 libs are not stripped by default? Feb 29 22:28:47 denix: aren't we stripping the binaries as part of the normal packaging logic? Feb 29 22:54:16 bluelightning: doesn't look like it. meta-qt5/jethro here and libQt5* are all huge unstripped, other libs are fine Mar 01 01:23:20 denix: hmm, just did a test here with master and the output binaries appear to be stripped as they should be Mar 01 01:23:45 of course, that's not jethro and perhaps there are other variations from your setup Mar 01 01:25:04 bluelightning: thanks! I'll try to debug it here then, at least you confirmed they should be stripped **** ENDING LOGGING AT Tue Mar 01 02:59:58 2016