**** BEGIN LOGGING AT Mon Oct 24 02:59:57 2016 Oct 24 06:53:09 what would be the workflow to add my new application using the yocto 1.6 (daisy) build Oct 24 06:53:29 I'm famiiar with devtools, but its not available in daisy Oct 24 06:55:12 titankiller: basically its no different, just a little less automated. its always: have a layer and put your recipe in there. the documentation state from 1.6 concerning that process is here: http://www.yoctoproject.org/docs/1.6/dev-manual/dev-manual.html#new-recipe-writing-a-new-recipe Oct 24 06:55:50 devtools aren't supported in daisy images? Oct 24 06:56:00 titankiller: you might even give the devtool-created recipe file a try, e.g. manually copy it over. probably it makes a good start. Oct 24 06:56:50 redengin: "devtool" sepcifically wasn't around until jethro, IIRC Oct 24 07:00:47 wow, devtool actually looks pretty awesome. does it work as simply as the documentation? Oct 24 07:02:30 redengin: devtool is just some magic around creating local recipes and a layer to hold them, basically. the really cool stuff is in the eSDK: its, in short, a frozen sstate plus all tools needed to create images based on the original one locally. and thats really awesome. Oct 24 07:28:21 good morning Oct 24 07:38:03 when I append packages (IMAGE_INSTALL_append), these packages from where they come? from which repositories? Oct 24 07:41:33 aV_V: the packages listed by IMAGE_INSTALL_append are the recipes you have in the layers Oct 24 07:44:48 mckoan: I mean the external source, which repository? Oct 24 07:45:19 aV_V: that is described in the recipe using SRC_URI Oct 24 07:46:09 mckoan: ty Oct 24 11:25:40 building meta-toolchain-qt5, I will get the sdk needed to cross-compile from my host to target, is that right? Oct 24 11:40:46 aV_V: basically thats what it is supposed to do, right Oct 24 11:47:41 LetoThe2nd: right, then as I will develop Qt programs, my target image would have installed some qt libraries, right? How I install them with bitbake? Oct 24 11:48:42 Or after I build the sdk, and I rebuild my linux image, they will install? Oct 24 11:49:51 aV_V: they have to be included in the image recipe, usually through either a packagegroup or package, in IMAGE_INSTALL Oct 24 11:50:47 ok, then I need to specify it. But first I need to discover what packages I need Oct 24 12:06:27 Hi, i want to virtualise my image that i created for an arm embedded device. I would start at compiling the image vor x86_64. But what where should i go next? can i use docker or nspawn? I want to see how the software behaves when many devices are connected to the network so i want to spawn multiple container that can interact which each other. Unfortunately i dont have any experience what so ever with virtualisation Oct 24 12:08:23 fl0v01: might be simpler to just start multiple qemu instances Oct 24 12:08:38 fl0v01: better just take the software, make it run on real hw and then kick off multiple instances. Oct 24 12:09:18 fl0v01: of course you can also beat it into shape until it runs on qemu or vbox or such, but thats only easy if it does not have any hw dependency. Oct 24 12:10:14 (and then you would need to switch to x86, just stick to qemu-arm) Oct 24 12:10:38 there are some components that have hw dependencies, but i would first leave them out and later try to simulate those. My biggest interest is to see how the network is behaveing Oct 24 12:10:55 ok so ill look into qemu Oct 24 14:53:39 Hi. Do you know how to disable replacing symlinks when I set "MACHINE_FEATURES += read-only-rootfs" ? Oct 24 14:55:09 I have 2 partitions and one of them is system partition - ro and other is rw. I created links from first (e.g. /etc/resolv.conf) to the second but bitbake keeps replacing that with links to tmpfs.. Oct 24 15:08:35 Anybody? Oct 24 15:09:02 Sorry, don't know Oct 24 15:09:14 Does anyboddy know, how to list all packages a recipe produces? Oct 24 15:10:41 @Anticom - you can use "-g" switch and you have packages in one of the generated files.. Oct 24 15:10:50 you can also try bb tool Oct 24 15:13:39 ok. sorry, bb does not help, but NXP guy's suggest this beautiful oneliner: bitbake -g && cat pn-depends.dot | grep -v -e '-native' | grep -v digraph | grep -v -e '-image' | awk '{print $1}' | sort | uniq Oct 24 15:14:33 jesus christ... i now went with `find` in work directory :D Oct 24 15:14:38 worked for me aswell Oct 24 15:15:23 but thanks anyway. I'll bookmark this for later use Oct 24 15:15:42 lewiatan: Also call me stupid but why is replacing symlinks even a thing in a ***read-only***-fs ? Oct 24 15:16:08 lewiatan: bb list and bb search can both cover the packages namespace from the metadata, using the same info that comes out of -g Oct 24 15:16:28 but if you want to list packages *emitted* from a recipe, that can differ, and you'd be best off looking at pkgdata or buildhistory Oct 24 15:16:32 s/recipe/build/ Oct 24 15:16:59 kergoth: hm well since i've just built my image both should be in sync, right? Oct 24 15:18:01 @kergoth: well, you're the expert here :-) Oct 24 15:18:33 Anticom: it isn't about sync, it's about the fact that binary packages aren't emitted if there are no files in them, and some recipes emit binary packages entirely based on runtime (PACKAGES_DYNAMIC) Oct 24 15:18:51 kergoth: ah i see Oct 24 15:18:58 thank you for elaboration Oct 24 15:19:04 that said, they should all be listed in some form between PACKAGES and PACKAGES_DYNAMIC in the recipe, just the latter is a regex pattern, not a list of packages, since we dont knwo what it'll emit until packaging time Oct 24 15:19:37 as it comes to replacing symlinks when "read-only-rootfs": I think the tool somehow checks if symlink points to rw rootfs.. I would like to check how it works but I don't know where to search Oct 24 15:20:31 lewiatan: see fs-perms.txt and also the volatile-binds recipe Oct 24 15:20:54 well, the latter is about bind mounting to tmpfs, not symlinking, so more likely the former is your culprit, or base-files Oct 24 15:21:19 if you're curious about what exactly happens when read-only-rootfs is set, read image.bbclass :) Oct 24 15:21:58 I'd love to have this as audio-book (: Oct 24 15:22:38 Thank you @kergoth Oct 24 15:22:41 Hmm, there's no bb command to just show the packages emitted by a single recipe, exactly. There's bb-contents, but that only works after the recipe has been built,a dn shows both packages and their contents.. there's bb-list/bb-search, but those are about finding provides, i.e. "what packages include bash in their name", not limiting to just a specific recipe Oct 24 15:23:26 I do recall I was going to implement a subcommand to list what a recipe provides, build time and run time, but I don't think I ever got around to it Oct 24 15:23:39 worst case there's bb show -r recipe PACKAGES PACKAGES_DYNAMIC :) Oct 24 15:23:42 kergoth: imo the entire structure of all tools is very confusing. I never really understood why there are like 10 different "utilities" that more or less seem to do similar things Oct 24 15:24:08 well, bb was created because bitbake didn't have any real tools for inspection, other than bitbake -e / bitbake -g Oct 24 15:24:22 nowadays there's bitbake-layers, which provides some of it Oct 24 15:24:35 and then there's layertool and recipetool and what not Oct 24 15:24:46 they have specific purposes Oct 24 15:24:58 sure but why not consolidate them into one tool Oct 24 15:25:21 why would i have to remember all those tools if i could just remember the options for a single tool. IMHO way more convenient Oct 24 15:25:25 you'd clutter up that one tool with a million and one commands or arguments :) Oct 24 15:25:36 -a -f -g -fourty-two-other-options isn't exactly usable either Oct 24 15:25:46 a matter of taste, i guess Oct 24 15:25:47 kergoth: systemctl is kind of like that. I still like it. But that's a matter of personal preference i suppose Oct 24 15:25:52 haha o/ Oct 24 15:25:54 i do think bitbake should get its command-line interface revamped in general Oct 24 15:26:11 I think sub-command based would be the way to go, it already has too many options, some of which are only valid in certain circumstances Oct 24 15:27:22 bb was sort of an experiment with that. i was going to add build/clean commands, and long term see about potential integration with bitbake proper Oct 24 15:27:36 but it hasnt' been a priority, for anybody, i think Oct 24 15:27:37 fair enough :) Oct 24 15:32:38 @kergoth - but still a lot of people use it - it's a good tool Oct 24 15:33:16 aye, it doesn't get much love, but I think it still fills a gap. hopefully we can fill that gap in bitbake proper and make it unnecessary at some point. just a matter of time Oct 24 15:33:18 * kergoth yawns Oct 24 15:33:25 hmm Oct 24 15:33:30 doesn't get much love? :-o Oct 24 15:33:59 bb doesn't, bitbake does, obviously :) Oct 24 15:34:05 bb is certainly loved Oct 24 15:34:18 just like most oe tooling it's word of mouth Oct 24 15:34:24 "oh, you didn't know about this?" Oct 24 15:34:33 * dv__ wonders how often people have confused "krogoth" with "kergoth" ;) Oct 24 15:34:40 heh, true. there are a bunch of those, even within oe-core (scripts/ and scripts/contrib/) Oct 24 15:35:12 but yeah, we definitely need a path to integrating bb with bitbake. Or enhancing bitbake with ideas we've learned from bb, or however you want to phrase it Oct 24 15:44:43 http://www.yoctoproject.org/docs/2.2/ref-manual/ref-manual.html#viewing-package-information-with-oe-pkgdata-util provides some of the functionality of bb Oct 24 15:49:30 oe-pkgdata-util examines build output. the only overlap with bb is the 'contents' sub-command, which just wraps oe-pkgdata-util and tells the user the oe-pkgdata-util command to use Oct 24 15:50:01 that's a very important subcommand at least Oct 24 15:50:20 it's kinda insane to me that oe-pkgdata-util was undocumented for so long :/ Oct 24 15:51:02 agreed Oct 24 15:51:08 very very handy tool Oct 24 15:51:15 i should use it more, actually Oct 24 15:56:42 bitbake-layers has some overlap too. i'll submit more comprehensive documentation for that once a patch gets in. Oct 24 17:51:39 I have read that doing bitbake meta-toolchain-qt5 is legacy method. So what would be the right way with yocto krogoth? Oct 24 18:01:15 so it's bitbake -c populate_sdk imagename Oct 24 18:02:04 what must be imagename: meta-toolchain-qt5 or the system image? Oct 24 18:06:52 a_VV: yes, the system image. also, you may look at the extensible SDK. Oct 24 18:06:55 a_VV: http://www.yoctoproject.org/docs/2.1/sdk-manual/sdk-manual.html#sdk-extensible Oct 24 18:07:24 bitbake -c populate_sdk_ext imagename Oct 24 18:08:01 stephano: then where it's specified that I want the Qt5 sdk? Oct 24 18:08:33 a_VV: in your system image. Oct 24 18:12:10 with SDK_DIR variable? Oct 24 18:15:17 a_VV: here is an example: bitbake -c populate_sdk_ext core-image-minimal outputs the sdk in ${SDK_DIR}. For qt5 you can do the same thing, but with my-image-qt5 as the imagename. Oct 24 18:17:43 stephano: hmmm, I get it. But let's say that I have core-image-base, and want to build Qt5 SDK. Then I need to edit the core-image-base recipe? Oct 24 18:19:16 I already have downloaded meta-qt5 btw Oct 24 18:22:01 a_VV: Create your own image, do not edit core-image-base. (Feel free to base your image off it though) Oct 24 18:22:56 a_VV: check the dev manual: Oct 24 18:22:58 a_VV: http://www.yoctoproject.org/docs/2.1/dev-manual/dev-manual.html#understanding-and-creating-layers Oct 24 18:23:55 I guess that I need to make do_populate_sdk(){} on my recipe Oct 24 18:24:08 ok, I will check that ty Oct 24 21:03:37 Hello - is there a way to clear out old entries from my sstate-cache that wouldn't be used by a build in the current config? Oct 24 21:04:01 I've tried moving my sstate_cache somewhere else and pointing to it with SSTATE_MIRRORS, but that doesn't seem to try downloading native packges. Oct 24 21:48:17 Circuitsoft: sstate-cache-management.sh, iirc. see oe-core/scripts/ Oct 25 01:00:18 kergoth: I have wks file in my own layer but its not being found do I need to add the path to WKS_SEARCH_PATH Oct 25 01:00:55 the location is actually same structure in layer scripts/lib/image/canned-wks Oct 25 01:15:17 ah figured path should be scripts/lib/wic/canned-wks not scripts/lib/image/canned-wks **** ENDING LOGGING AT Tue Oct 25 02:59:58 2016