**** BEGIN LOGGING AT Fri Jul 27 03:00:01 2018 Jul 27 07:26:32 New news from stackoverflow: way to add a component in yocto, by making new package || Patch sources from yocto based on the git commit hash/tag Jul 27 08:00:16 Hi! Is there a easier alternative to write a full recipe (configure+compile+install) for a given package (non included in Openembedded Layers)? Jul 27 08:01:12 e.g. Can introduce a built package (maybe from raspberry pi repos) into my Yocto system? Jul 27 08:02:01 My target system is an imx.6 though Jul 27 08:22:28 malanecora: OE builds from source so you need to put together a recipe, but sometimes its easier if it uses some known component build systemd e.g. automake, cmake Jul 27 08:22:53 those are abstracted in OE so all you need it inherit cmake or inherit autotools Jul 27 08:26:46 New news from stackoverflow: How do I use header file with Yocto-generated SDK? Jul 27 09:03:09 Thank you @khem Jul 27 09:26:54 New news from stackoverflow: How to use header file with Yocto-generated SDK? Jul 27 10:08:33 BTW, is there any good resource for learning Yocto with? I mean, other than the official website manuals... Jul 27 10:16:39 malanecora: sure look into https://www.yoctoproject.org/docs/ Jul 27 10:26:43 malanecora: I have twp books that are OK if a little dated. Jul 27 11:23:42 TafThorne: pdf? Jul 27 11:46:06 https://stackoverflow.com/questions/51496061/using-files-generated-by-other-recipes-in-yocto Jul 27 11:48:19 Hello! how does one set a desired distro? In my layer I have conf/distro/xy.conf ... but which variable sets it to xy? is it set from image recipe ? Jul 27 11:56:49 local.conf sets DISTRO="xy" Jul 27 11:57:27 New news from stackoverflow: Patch sources from yocto recipe based on the git commit hash/tag of the sources Jul 27 11:58:04 rburton: or in the image recipes, i guess Jul 27 11:58:07 rburton: tnx Jul 27 11:58:25 no definitely not in the image recipe Jul 27 12:00:35 rburton: what is the rationale? I plan to build several different images sharing same design decisions made with the distro Jul 27 12:01:18 because if you change a variable in a recipe (such as an image recipe) then it doesn't impact *any other recipes* Jul 27 12:01:38 so you can't set DISTRO=something in an image and expect the distro changes to impact the packages that go into that image Jul 27 12:02:04 they've all been built with whatever DISTRO is set in the local.conf Jul 27 12:09:00 rburton: ok, that makes sense. Jul 27 12:09:55 rburton: but it adds extra burden on a developer to manually add (=not forget to add) DISTRO=xy in local.conf Jul 27 12:11:16 ak77: well, not really. "i want to use this distro" is kind of important. if you're building a distro layer etc then you can provide a template local.conf which sets the right distro for new build dirs (meta-poky does this) Jul 27 12:18:34 rburton: yes, but if I we define images a/b/c for products A/B/C, there is should be no decision which distro to use Jul 27 12:19:05 rburton: * yes, but if we define images a/b/c for products A/B/C, there should be no decision which distro to use Jul 27 12:27:22 rburton: or is this logic flawed? Jul 27 12:36:20 Hi there, did you ever seen this error on glibc-locale_2.26.bb ? https://pastebin.com/YXVCLZjq , it's used by poky, branch rocko Jul 27 13:41:28 ak77: if you need a distro per product then so be it, you need to set the distro before building. ideally, you can have a single distro across all products. Jul 27 13:41:44 easy enough to make the images throw an error if they need a specific distro to be set Jul 27 13:43:46 it is common to use the same images for different distros... if you have an image -> distro mapping requirement, you can simply put a check in your image recipe that the expected DISTRO is set, and 'skip' that image with an appropriate message if it's not.. Jul 27 13:44:16 (better practice is to understand WHY it's not allowed, a specific distro setting, etc.. and simply check for that minimal behavior vs the actual name of the DISTRO you use) Jul 27 13:46:05 maybe someone here might know -- I'm working on meta-flatpak (a copy of a layer someone gave me).. I'm trying to trace origins, and I found a layer with that name in the layer index pointing to the intel-iot-refkit repository... Jul 27 13:46:15 however, there is a note that is more or less abandoned.. Jul 27 13:46:35 so i did further searching on github, and came across: https://github.com/klihub/meta-flatpak Jul 27 13:46:46 what I can't tell is, is this also abandoned or is it being maintained? Jul 27 13:47:30 last commit was from may 16th, but I don't see any OE/Yocto branch names or anything associated.. so I have no idea what it's expected to work with.. Jul 27 13:47:49 he was on the refkit team but isn't anymore, i'm surprised he pushed a commit this year Jul 27 13:48:30 I also found: https://github.com/lifupan/meta-flatpak which appears to be a fork of it, that is more up to date.. but it's clearly a fork -- as it divered last year some time.. this one does seem to be getign regular updates (at elast through may of this year) Jul 27 13:48:52 rburton is the WHOLE of the intel-iot-refkit abandoned? Jul 27 13:48:56 or just flatpak? Jul 27 13:48:58 pretty much Jul 27 13:49:14 ok.. that's good info.. there is a small part one of my guys wants to use.. I might suggest he fork it Jul 27 13:51:20 sounds sensible Jul 27 13:51:27 a actual maintained flatpak layer would be great Jul 27 13:51:39 not aware of anyone actually doing that though Jul 27 13:59:19 rburton: Did you happen to see my comments on pylibfdt in u-boot? I can't decide if pythonnative.bbclass is broken (seems less likely) or isn't appropriate for that situation. Jul 27 14:00:21 JPEW: i didn't but i've not worked for a few days Jul 27 14:00:41 rburton: Ok, np Jul 27 14:58:01 New news from stackoverflow: Request for clarification on Yocto inheritance Jul 27 15:09:36 rburton: I had in mind a single distro for all products. checking for distro in image recipe will do i guess. thank you Jul 27 15:10:43 ak77: if you have a single distro for all products then either 1) make setting it in local.conf step 1 of the instructions or 2) provide a template local.conf that does this already. no need to check in your images, as you'll hate yourself when you make a second distro for whatever reason :) Jul 27 15:11:36 rburton: Jul 27 15:11:40 rburton: thank you Jul 27 15:42:59 hi, is there a commit hash in the uname output of a system running linux built via yocto? "Linux dscr-ap2 4.1.41-dey+gf1a146c #3 SMP PREEMPT Wed Apr 18 07:41:47 EDT 2018 armv7l GNU/Linux" Jul 27 16:11:48 zarzar: kernel sha Jul 27 17:21:01 rburton, sounds like a Californian surfer Jul 27 17:21:58 I was thinking snow boarder Jul 27 17:22:16 especially with a name like burton.. ;) Jul 27 17:22:23 : ) Jul 27 17:27:12 ugh, so behind on submitting patches from mentor's backlog, need to catch up Jul 27 18:16:31 Hi. I'm trying to add a pre-mirror for a yocto build. Can anyone help me with this? Jul 27 18:30:12 hk_: https://www.yoctoproject.org/docs/latest/mega-manual/mega-manual.html#var-PREMIRRORS ? Jul 27 18:35:16 Thnk you JPEW Jul 27 18:39:04 as part of my main image build, hw-test-image, i need to generate a .fat32 image containing zImage and the .dtb files. how do i add this to my hw-test-image.bb? Jul 27 18:51:43 kergoth, know how you feel Jul 27 18:55:35 RP, stable/sumo-next updated. may want to use it for next QA run Jul 27 18:57:16 nm, i lied. Jul 27 18:58:45 New news from stackoverflow: Include a custom device tree overlay in bitbake for BeagleBoneBlack Jul 27 19:03:47 does the bootloader recipe generate the .dtb files? Jul 27 19:10:48 yates: Usually the kernel recipe generates those Jul 27 19:17:06 Hello, How do I include my dtb in the rootfs /boot directory? I have tried appending do_install in my linux bbappend file with install -m 0644 arch/arm/boot/dts/${KERNEL_DEVICETREE} ${D}/boot/. However I get an error stating: QA Issue: linux-imx: Files/directories were installed but not shipped in any package: /boot/my-device.dtb. Any ideas? Jul 27 19:18:31 justinttt: Have you appended the filename to the variable FILES_${PN} ? Jul 27 19:19:23 I believe this is necessary for declaring any files you've added to the filesystem that you want packaged in the final image Jul 27 19:23:02 justinttt: Here's some more information on the FILES variable if you need it: https://www.yoctoproject.org/docs/1.8/ref-manual/ref-manual.html#var-FILES Jul 27 19:23:56 robbawebba I did not do that. I will give that a try, thank you Jul 27 19:33:26 justinttt: cheers :) Jul 27 19:53:32 robbawebba: also found out that adding "kernel-image kernel-devicetree" to my image handles all that for me. Thanks for the help. Jul 27 20:06:16 anyone know how I might set up connman for static ip on a systemd build? Jul 27 20:43:14 just reading some old logs.... Someone, lets call him Joe asks a question... kergoth - "blah blah" Joe - "hmm, I dunno, rburton, can you confirm this?", lol Jul 27 21:03:17 rburton: Can you pick few patches that I posted some days ago Jul 27 21:03:27 http://git.openembedded.org/openembedded-core-contrib/commit/?h=kraj/master&id=7f36beee96ea8e8a9243b42b2975e8c29692aef6 Jul 27 21:03:39 http://git.openembedded.org/openembedded-core-contrib/commit/?h=kraj/master&id=b5772fd58d938676acf8b1d1cdb6bd98469595ae Jul 27 21:03:51 http://git.openembedded.org/openembedded-core-contrib/commit/?h=kraj/master&id=73676538a9292391c8e17705ee0c2b31e4e20bc4 Jul 27 21:04:05 http://git.openembedded.org/openembedded-core-contrib/commit/?h=kraj/master&id=35012934a6b385e355d681c79f5102bf1e7e192d Jul 27 22:20:46 armpit: thanks **** ENDING LOGGING AT Sat Jul 28 02:59:59 2018