**** BEGIN LOGGING AT Fri May 20 02:59:59 2016 May 20 06:31:27 Hi I was trying to use a if condition in my recipe file:if [ ${MACHINE_ARCH} == ls1 ] ; then May 20 06:31:31 but its not working May 20 06:31:41 I looked at the documentation May 20 06:31:55 but couldn't find out whats wrong May 20 06:44:23 niteshnarayanlal: you need to use "1" = "2" May 20 06:54:19 khem, something like this : if [ "${MACHINE_ARCH}" == "ls1" ] May 20 06:54:56 if [ "${MACHINE_ARCH}" = "ls1021atwr" ] May 20 08:40:14 hi, I have a question - how can I build multiple versions of a package? May 20 08:40:38 maciejjo: depends what you mean by "version" May 20 08:40:56 as in 2.0 vs 1.1 May 20 08:41:01 or x86 vs arm May 20 08:41:09 2.0 1.1 May 20 08:42:08 i'm not sure, it's probably a bitbake option, let me have a look for a sec May 20 08:42:53 ls May 20 08:43:50 Does anybody know of a nice Yocto IMX6 QT5 tutorial ? I am having problems setting up my image for targeting QT IDE May 20 08:44:41 maciejjo: I can't find it, not sure it can be done from the command line May 20 08:44:59 boucman_work: generally what I am trying to achieve is building 3 versions of linux May 20 08:45:13 you can use PREFERRED_VERSION_pn-= in local.conf and then bitbake the package twice with different version number May 20 08:47:19 ok, this would work manually, but I would like to build multiple versions for one image May 20 08:47:53 is such thing supported? May 20 08:48:27 hmm, no... multiple versions of the same package replace each-other... May 20 08:48:44 kernel is a bit special, though, but I don't think it's supported May 20 08:56:14 no its not supported May 20 08:56:21 you can version the packages explicitly, like glib is May 20 09:00:29 obviously the contents can't conflict either May 20 09:01:53 ok, maybe I'll try this way May 20 09:02:54 maciejjo: what exactly are you trying to do ? why do you want to do it ? May 20 09:04:26 I want to have an image that contains few kernels packed in fit image that allows user change which kernel to use at boot time May 20 09:07:10 this is done for development purpose so few kernels can be tested without reflashing May 20 09:08:10 Small patch question guys. May 20 09:08:30 as far as I understand simmilar enhancement to what I want has been requested here: https://bugzilla.yoctoproject.org/show_bug.cgi?id=6945 May 20 09:08:30 I want to propose a patch for adding --fbdev option for psplash. May 20 09:08:31 Bug 6945: enhancement, Medium+, 2.2 M1, zhe.he, IN PROGRESS REVIEW , kernel-dev: multiple kernel build May 20 09:08:48 But there are patchs in different repositories. May 20 09:09:05 psplash and poky May 20 09:09:19 How should it be done? May 20 09:09:20 but from what I see in patches it only adds possibilty to build multiple image formats, not kernel versions May 20 09:38:44 present: why do you need to modify the meta-poky append? May 20 09:41:38 rburton, base-files to add fbdev file May 20 09:43:45 meta/recipes-core/base-files/base-files/fbdev | 1 + May 20 09:43:45 meta/recipes-core/base-files/base-files_3.0.14.bb | 8 +++++++- May 20 09:43:46 meta/recipes-core/psplash/files/psplash-init | 7 ++++++- May 20 09:44:12 right, that's all in meta/ so send to openembedded-core@ May 20 09:46:24 rburton, I have the one for psplash itself too. May 20 09:47:16 http://git.yoctoproject.org/cgit/cgit.cgi/psplash/about/ May 20 09:48:24 They go together. May 20 10:07:55 present: isn't the core one independant from psplash ? May 20 10:08:08 (the psplash depends on the core one, i'm not sure about the other way round...) May 20 10:19:48 hello channel May 20 10:20:18 I'm getting started with using the multilib feature and have a question May 20 10:20:38 is it possible to specify that a specific package should always be built for the "lib32-" tune? May 20 10:21:01 hmm, not per-se May 20 10:21:39 multilib means that you have a whole bunch of new package available for your architecture (the 32bit variants) May 20 10:21:55 if you want foo in the lib32 tune then bitbake lib32-foo May 20 10:21:56 but those are built only if they are needed, just like any package May 20 10:22:10 (and add lib32-foo to your images etc etc) May 20 10:22:17 thanks May 20 10:22:31 so either because you ask for them on the commandline, an image needs them to install them on the target, or another package depends on them May 20 10:23:05 sure, the thing is the distro builds for 32-bit and 64-bit machines, but this package will fail on 64-bit May 20 10:24:00 don't build it then :) May 20 10:24:15 I will work around with putting an override on the packagegroup that depends on the bad package, something like RDEPENDS_${PN}_aarch64_remove = package-foo, RDEPENDS_${PN}_aarch64_append = lib32-package-foo May 20 10:24:26 rburton: thanks :) May 20 10:24:35 yeah, that works if you've got it in a packagegroup May 20 10:25:17 I was just wondering if there was a way to put this specification in the package recipe instead of the packagegroup May 20 10:25:23 but the workaround is good enough May 20 10:25:52 well you've a packagegroup that explicitly asks for the target form of the recipe May 20 10:25:56 thanks a lot, rburton and boucman_work ! May 20 10:26:02 so its doing exactly what you're telling it to do May 20 10:26:33 a neater way would be to have a variable for the recipe name and override that to pick the right form May 20 10:26:59 yes, it makes perfect sense given that they are considered separate packages May 20 10:27:17 and the variable override would be neater May 20 10:29:35 rc.local - how do we ensure it gets called during init May 20 10:44:51 boucman_work, there is the psplash sources itself. I'll first patch there and wait for an answer. May 20 12:20:26 Is there a good way to checkout the same branch on all the meta layers at once (as opposed to going into each one to change fido->krogoth for example)? This is of course assuming they all have the same branch available and they're just cloned to the poky directory. Or perhaps a better way to manage the meta layer repos than just cloning them to the poky directory? May 20 12:21:59 gferencz: you could look at tools like gitsubmodules or google repo May 20 12:23:04 CTtpollard, Sounds good. I started looking into submodules but thought I was headed down the wrong path. Thanks! May 20 14:56:21 does anyone know if local / bblayers conf can make use of .inc files? May 20 14:57:08 local.conf for sure May 20 14:58:15 cool, I have a situation where I have multiple local.conf templates for different targets, but I want them to inherit a common.inc file of values May 20 15:02:07 if they're values which are related to builds on your machine then you can use a site.conf May 20 15:02:32 gferencz: mr is another option, if you want something a bit lighter. no manifest or main repo to maintain, just a config file to make it easier to run commands on a set of repositories May 20 15:02:35 depends on your needs May 20 15:03:49 gferencz: https://myrepos.branchable.com/, if you need. touch .mrconfig at the parent of the repositories, then go into each dir and do mr register, then you can run commands like mr checkout or mr update to run against all of them May 20 15:04:07 i use repo at work, submodules for certain projects, and mr for local-only setups, myself May 20 15:17:56 kergoth, Thanks for the pointers. I'm just getting started with yocto/bitbake, trying to find a workflow and figure out my needs. Options are a good thing. May 20 15:27:47 khem: you sent a four part series but i can only see half the patches on the list May 20 15:32:24 gferencz: indeed. lots of ways to do it May 20 15:32:27 np May 20 16:47:25 rburton: only 2 were worth submitting May 20 18:10:01 somebody wants to buy my freenode nick for BTC May 20 18:10:04 "oney and the new guy gets annoyed with messages that are supposed to be for you! May 20 18:10:22 "hey. I'll pay you btc to part with your nick. my friend wants to register it." May 20 18:11:38 who is doing documentation for Yocto? I have one patch May 20 18:20:17 Xz, send it to th elist May 20 18:21:23 Crofton|work: to openembedded-core or -devel? May 20 18:22:50 -core May 20 18:23:10 maybe the yocto list May 20 18:23:18 so many lists, May 20 18:25:45 Xz: if Yocto documentation, send to yocto list. May 20 18:26:04 billr: what's "yocto list" May 20 18:26:12 heh May 20 18:26:12 billr: I am subscribed only to -devel and -core May 20 18:27:09 https://lists.yoctoproject.org/listinfo/yocto May 20 20:40:49 anyone aware of a quasi recent change in the locale rpm handling? May 20 20:41:09 I'm still seeing the rpms get built but they don't get installed in the rootfs image. May 20 20:41:42 my build is largely based on the build-appliance but with a kernel and grub etc so you can boot it. May 20 20:45:33 GLIBC_GENERATE_LOCALES is about generation ; doesn't mention installing... May 20 21:10:26 IMAGE_LINGUAS controls the install into the rootfs May 20 21:17:39 yeah I was looking at that... this sentence in the manual is kind of confusing May 20 21:17:50 Setting the IMAGE_LINGUAS variable ensures that any locale packages that correspond to packages already selected for installation into the image are also installed. May 20 21:19:00 anyway, I'm going to try setting that explicitly to en_US and en_GB and see if that "fixes" whatever changed. May 20 21:19:29 previously I'd not set either of that or GLIBC_GENERATE_LOCALES and was just taking the yocto defaults May 20 21:35:24 I should say en-us and en-gb ; looks like that var is expecting to mach the pkg name and not the locale name. May 20 21:35:41 * paulg waits on do_rootfs to see if it worked... May 20 21:49:05 kergoth, still no locale files in my new manifest. :( Not sure what to check next.... May 20 21:50:52 might just checkout sth a month old and confirm they were still installed and then let "git bisect run" chew on it over the wknd. :) **** ENDING LOGGING AT Sat May 21 02:59:58 2016