**** BEGIN LOGGING AT Sun Jul 10 02:59:58 2016 Jul 10 10:10:20 hi Jul 10 10:10:53 I would like to add a package to DEPEND but only when one variable is defined Jul 10 10:10:55 how can I do that? Jul 10 10:11:09 I guess I have to use bb.utils.contains ,or .conditional, or similar... But it is not clear to me Jul 10 11:40:19 learner: DEPENDS += "${@'value' if d.getVar('OTHERVAR', True)}" Jul 10 11:40:36 In a lot of cases this can be achieved in a simpler and clearer way, though Jul 10 11:41:28 e.g. if you want to add something to DEPENDS but only for the target system, you could use VAR = ""; VAR_class-target = "value"; DEPENDS += "${VAR}" Jul 10 12:06:33 neverpanic: thanks! that does what I wanted Jul 10 21:49:24 Hi, I'm new to yocto/ostro. I'd like to start with ostro (with these directions https://ostroproject.org/documentation/howtos/building-images.html ), but change to kernel 4.1. I see there's a 4.1.bb file in ostro-os alongside a 4.4.bb file, and I'm not sure how to set one versus the other as the one to use. Any guidance? Thanks! Jul 10 21:51:31 (this is the 4.1 bb file I found https://github.com/ostroproject/ostro-os/blob/master/meta/recipes-kernel/linux/linux-yocto_4.1.bb - there's also a lsb 4.1 bb file available. Bit overwhelmed trying to follow how these all connect) Jul 10 21:55:40 catau: set it using PREFERRED_VERSION_linux-yocto = "4.1%" Jul 10 21:56:14 khem: thanks, would this go in my build/local.conf? Jul 10 21:57:10 you can if you have one machine Jul 10 21:57:13 (I am still building out a VM to try this, so I am not yet looking at a local.conf file to see if that is already present somewhere, sorry!) Jul 10 21:57:21 but usually it goes into machine conf file Jul 10 21:57:29 which machine are you building for Jul 10 21:57:42 I do, a galileo in my case Jul 10 21:59:05 ok then find the definition for galileo.conf Jul 10 21:59:25 and see if that definition is there usually it should be setting kernel version there Jul 10 22:01:40 khem: thanks. I'm puzzled now by what I think is a discrepancy -- this is the galileo file I would imagine you are referring to https://github.com/ostroproject/ostro-os/blob/master/meta-ostro-bsp/conf/machine/quark.conf Jul 10 22:02:16 and 4.1 is set there, but when I downloaded a pre-built image for the galileo from ostroproject.org, I found myself on 4.4 (with uname -a) Jul 10 22:04:23 the tagged 1.0 release in github (https://github.com/ostroproject/ostro-os/blob/v1.0.0/meta-ostro-bsp/conf/machine/quark.conf) also still only specifies 4.1 -- perhaps it was overridden elsewhere? Jul 10 22:07:08 are you still building linux-ostro Jul 10 22:08:27 or is it linux-yocto ? Jul 10 22:09:36 my apologies, I'm uncertain how to answer Jul 10 22:11:15 morning all Jul 10 22:12:16 catau: ok how do you know its 4.4 Jul 10 22:12:19 gm bluelightning Jul 10 22:12:38 bluelightning: are you in NZ Jul 10 22:12:47 khem: ostroproject.org provides an already built image; I booted my galileo from that and found it to be 4.4 -- I believe the instructions from https://ostroproject.org/documentation/howtos/building-images.html may be for meta-ostro (and perhaps this may explain the 4.4 default in turn), but I don't know how to verify that Jul 10 22:12:49 khem: I am indeed Jul 10 22:13:31 khem: I'm here permanently now Jul 10 22:13:56 bluelightning: ah nice, I have plans for NZ and Aus in 2017 Dec. Jul 10 22:14:21 catau: can you check the version string for kernel when booting ? Jul 10 22:14:32 it should dump it into dmesg Jul 10 22:15:52 khem: will do, booting now Jul 10 22:18:03 khem: cool! if you have time it would be great to meet up while you are down here :) Jul 10 22:20:22 khem: Linux version 4.4.3-yocto-standard according to dmesg (and that agrees with uname-a too) Jul 10 22:20:55 uname-a outputs Linux intel-quark 4.4.3-yocto-standard ... Jul 10 22:24:25 perhaps I downloaded an image that's not congruent with the source tree? Jul 10 22:26:34 seems so Jul 10 22:27:00 bluelightning: its a long term plan still more than a year ahead but I will let you know Jul 10 22:29:14 khem: thanks, I'll try setting it in my local.conf just for kicks too. Jul 10 22:29:18 On that note, I think this is also not the correct place to add my next change, but if I want linux-headers on my image, can I set TOOLCHAIN_TARGET_TASK_append = " kernel-devsrc" in my local.conf (from http://stackoverflow.com/a/31261404) Jul 10 22:30:50 (this is all to compile a different version of iwlwifi using the instructions here http://dhalperi.github.io/linux-80211n-csitool/installation.html -- I am not sure if it makes more sense to replace the iwlwifi directory in the kernel sources that poky will download into my DL directory) Jul 10 22:56:13 < Jul 11 02:20:57 Hi, I'm trying to build an Intel Galileo image using https://github.com/ostroproject/ostro-os but with two modifications: (1) kernel 4.1 and (2) linux-headers -- I made the following two changes to local.conf, neither of which seemed to take effect Jul 11 02:21:20 PREFERRED_VERSION_linux-ostro ?= "4.1%" and TOOLCHAIN_TARGET_TASK_append = " kernel-devsrc" Jul 11 02:21:45 (I also tried PREFERRED_VERSION_linux-yocto ?= "4.1%" ) Jul 11 02:23:02 ?= is *not* what you want there Jul 11 02:23:05 that's set if it isn't set already Jul 11 02:23:12 which explicitly does *not* set it when it's already set Jul 11 02:23:16 use = Jul 11 02:24:12 kergoth: oh, geez, what a simple fix, sorry! Jul 11 02:24:27 kergoth: thanks so much! I should have read the docs more patiently :) Jul 11 02:26:39 regarding the source, I looked in /usr/src/ and didn't spot anything there. /lib/modules didn't seem to have a link for 'build' either Jul 11 02:27:06 am I misunderstanding the kernel-devsrc command? Jul 11 02:33:22 skimming the docs, do I need to somehow edit my local.conf file to build an sdk image? Jul 11 02:34:32 (perhaps OSTRO_IMAGE_EXTRA_FEATURES = "dev-pkgs tools-sdk debug-tweaks" ?) Jul 11 02:38:47 TOOLCHAIN_TARGET_TASK is how you add packages to an sdk. if you're building a rootfs, not an sdk, that's the wrong variable Jul 11 02:39:07 you'd do better with CORE_IMAGE_EXTRA_INSTALL += "kernel-devsrc" or IMAGE_INSTALL_append = " kernel-devsrc" if the latter Jul 11 02:39:14 which is in the docs Jul 11 02:42:22 kergoth: thanks again, I mistakenly assumed the sdk was a different flavor of the rootfs. Can I trouble you to clarify, to what you're referring to when you say the latter? Jul 11 02:42:47 look up 'former' and 'latter' in a dictionary Jul 11 02:43:12 CORE_IMAGE_EXTRA_INSTALL or IMAGE_INSTALL_append are used to add packages to your rootfs, as is, again, documented in the yocto project docs, and examples are in the local.conf sample Jul 11 02:43:49 my apologies, I'll refer to the docs **** ENDING LOGGING AT Mon Jul 11 02:59:58 2016