**** BEGIN LOGGING AT Fri Mar 09 03:00:01 2018 Mar 09 04:49:53 New news from stackoverflow: Error in yocto meta-udoo build. Krogoth branch Mar 09 06:46:44 How I do specify the sysroot parameter in my EXTRA_OEMAKE ? Mar 09 08:47:33 hi everyone Mar 09 08:58:26 someone use know how to leave write the recipe versión in sysroot to read it lated from the app (and show the version to the user in an automatic mode)? Any help to read about it? Mar 09 09:00:32 can you try to reword it? at i personally fail to understand what you actually need, sorry. Mar 09 09:01:56 yes, sorry. I have the recipe of my application and I wish write its version when I bake it. Later I need to show this version to the user Mar 09 09:02:38 zuribost: you could just do some install append that basically pipes the ${PV} into a file that you can read later. Mar 09 09:02:44 thats the super simple version Mar 09 09:02:51 this "version" to the user, like V1.0.15 to be sure the last available versión of the app is installed Mar 09 09:04:48 but actually, usually an application is able to show its own version. so if you have some external thing thats meant to show a lot of versioning/package info, you might want to look at the buildinfo stuff, if i remembder correctly. that can include a lot of such information automagically in the image. Mar 09 09:10:52 thanks, I already have the image build info with the md5 inside (I inherit the proyect), but I have in mind add this other one Mar 09 09:11:16 i'm not talking about the md5 Mar 09 09:11:36 I will try to do a simpy one making a directory using the ${PV} var Mar 09 09:12:08 here you go: https://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/classes/image-buildinfo.bbclass Mar 09 09:13:35 I only name the md5 because is what done other colleague. Thank for the help Mar 09 09:29:39 Does OE/yocto support overriding with package name? Mar 09 09:29:50 like I do have package psplash Mar 09 09:30:11 then I do create psplash.bbappend Mar 09 09:30:29 and in it: PROVIDES += "psplash-foo" Mar 09 09:31:16 Is it possible to alter for example SPLASH_IMAGES_psplash-foo = "image-foo" Mar 09 09:31:32 and then also SPLASH_IMAGES_psplash = "default OE wallpaper" Mar 09 09:31:50 When I do use ${PN} than it is correctly the psplash image Mar 09 09:32:22 And the problem is to have different splash screens for rootfs and initramfs ....... Mar 09 09:45:51 hi, I'm trying to find the "correct" way to install custom kernel headers so they are found by my userspace application Mar 09 09:46:09 I read the note in poky/meta/recipes-kernel/linux-libc-headers/linux-libc-headers.inc Mar 09 09:52:05 which states do_shared_workdir is supposed to install the headers Mar 09 09:52:48 but do_shared_workdir does not do it, and actually "headers_install" does not appear in any recipe except linux-libc-headers.inc Mar 09 09:58:09 Ok. I seems like SPLASH needs to be properly set per package Mar 09 09:59:01 lucaceresoli: shluldn't them be already included in the toolchain? Mar 09 10:09:04 mckoan: I have a custom header file in my kernel sources (for a custom driver) Mar 09 10:09:53 mckoan: that file does not seem to be installed by the toolchain -- I suspect the toolchain uses mainline headers, not those from my kernel Mar 09 10:13:39 mckoan: my kernel recipe is custom too; it does 'require recipes-kernel/linux/linux-yocto.inc' and adds a defconfig and a few minor things Mar 09 10:16:15 lukma: if the psplash recipe is using PN correctly then you can just make a psplash-init.bb and include psplash.bb in it, then set SPLASH to the value you want Mar 09 10:19:56 rbutfon: As fair as I read it should be possible to Mar 09 10:20:19 some recipes will use the name literally instead of PN but that's basically a bug in the recipe Mar 09 10:20:40 so the PN is the base package name Mar 09 10:20:45 not the alias ? Mar 09 10:21:27 even when I do set IMAGE_INSTALL += "psplash-foo" Mar 09 10:21:45 the ${PN} would resolve to psplash Mar 09 10:22:17 in the other recipe its not an alias, its the real name Mar 09 10:22:43 include isn't doing anything magic, its just pulling the text of the file you specify in Mar 09 10:24:55 rburton_: And what's about the magic behind SPLASH ? Mar 09 10:25:07 I shall be able to have psplash_%.bbappend Mar 09 10:26:12 with SPLASH_IMAGES = "psplash-poky-img.h,outsuffix=default psplash-foo-img.h,outsuffix=foo" Mar 09 10:26:26 i'd be writing a bbappend for psplash to change your main splash, and a new recipe including the original for the init splash Mar 09 10:27:05 and then in my init image SPLASH = "foo" Mar 09 10:27:15 and IMAGE_INSTALL += "psplash-foo" ? Mar 09 10:27:19 Is this correct ? Mar 09 10:28:46 just setting SPLASH will work assuming you have the splash feature enabled for the image Mar 09 10:32:28 But I is cleaner to use the psplash-init.bb for initramfs Mar 09 11:47:57 I think I found a solution to the custom kernel header issue -- but I'm not sure it's 100% correct Mar 09 11:48:23 First: the comment in poky/meta/recipes-kernel/linux-libc-headers/linux-libc-headers.inc _looks_ wrong to me Mar 09 11:49:09 it says I should get my headers from STAGING_KERNEL_DIR, but STAGING_KERNEL_DIR here expands to: Mar 09 11:49:38 tmp/work-shared//kernel-source Mar 09 11:49:52 which is a symlink the the kernel source dir Mar 09 11:50:20 which you're patching if you have a custom kernel header, surely Mar 09 11:51:58 rburton_: yup, but I should use the headers produced by 'make headers_install', not the bare sources, right? Mar 09 11:52:32 * rburton_ shrugs Mar 09 11:52:43 ask zeddiii zeddii_home when he wakes Mar 09 11:53:44 rburton_: and anyway why should I depend on virtual/kernel:do_shared_workdir and then use the bare sources? Mar 09 11:53:56 rburton_: :-? Mar 09 12:02:10 How can I get the recipe sys root dir in my .bb file to be able to pass it to the Makefile ? Mar 09 12:10:03 I am looking for help translating the default poky/meta/conf/machine/qemuarm.conf so that I can emulate an armv6 environment. Mar 09 12:11:32 I've tried commenting out the 'tune-arm926ejs.inc' and commenting in the 'tune-arm1136jf-s.inc' requires, and that appears to get me an armv6 build, but when I try to `runqemu` after the build, I just get a black qemu screen... Mar 09 13:34:11 any chance to know some bitbake predefined variables ? Mar 09 13:34:18 dzen: see bitbake.conf Mar 09 13:34:21 (or the documentation) Mar 09 13:34:48 thanks ! Mar 09 13:35:31 oww bitbake.conf is pretty nice Mar 09 13:36:14 rburton_: Ok, so I do have pspash, psplash-default and psplash-foo installed Mar 09 13:36:19 for initramfs Mar 09 13:36:38 (as I did IMAGE_INSTALL += psplash-foo) Mar 09 13:36:57 Is there a way to force psplash to only install psplash-foo in the initramfs ? Mar 09 13:37:12 SPLASH="psplash-foo" is not working Mar 09 13:55:22 Does anyone here have time to help me make qemuarm.conf emulate an armv6 environment instead of an armv5? Mar 09 16:08:31 I am trying to build a qemuarm based yocto image that can operate as a docker host. Most arm-based docker images assume arm32v6 or better, and I'm wondering what the right way is to configure a qemuarm build that is arm32v6 or better. Mar 09 16:22:02 New news from stackoverflow: How to bring software console in Yocto Mar 09 16:29:08 I'm wondering if ALTERNATIVE PRIORITY can be accessed from the image recipe? Mar 09 16:29:42 the psplash now has psplash-devault (update laternative prio 100) and psplash-foo (update-alternative 100) Mar 09 16:29:54 I include psplash in two images Mar 09 16:30:13 in one I would like to see psplash1 and in second psplash2 Mar 09 16:30:34 to do that I need in image-foo increase alternative priority Mar 09 16:31:30 like ALTERNATIVE_PRIORITY[psplash-foo] = "101" Mar 09 16:31:44 when above put in the psplash recipe or bbappend then it works Mar 09 16:31:52 if moved to image-foo the it seems to be out of scope Mar 09 16:31:58 Any help? Mar 09 16:32:01 On this issue Mar 09 16:34:06 i woudln't recommend trying to use that in an image, instead just use ROOTFS_POSTPROCESS_COMMAND to run update-alternatives to alter its configuration Mar 09 16:34:09 * kergoth shrugs Mar 09 16:34:21 armpit: Are you on right now? Mar 09 16:36:13 kergoth: Hmm ....... Mar 09 16:36:28 Then I could avoid doing magic with the package itself Mar 09 16:37:21 But which update-alternatives to run - from the yocto build ? Mar 09 16:37:48 follow the same method the bbclass uses. it runs the -native binary with args/env vars to point at the alternate root Mar 09 16:37:53 i'd read the bbclass Mar 09 16:38:56 it *may* be possible to use the class the way you suggested, but as it is today it injects the commands into package postinsts, which obviously wouldn't be run, so you'd still have to inject those commands via another method either way, so it's simpler to just add the commands directly rather than using the metadata vars to control it Mar 09 16:40:55 kergoth: So I shall use ROOTFS_POSTPROCESS_COMMAND Mar 09 16:41:18 and then update-alternatives manually from there? Mar 09 17:10:47 * armpit hmm rocko went south Mar 09 17:11:12 JPEWhacker, yes for a few minutes Mar 09 23:48:01 armpit: Has there been any organization for transportation to/from OEDAM, besides people indicating how many they can take? **** ENDING LOGGING AT Sat Mar 10 03:00:03 2018