**** BEGIN LOGGING AT Sun Oct 01 03:00:02 2017
**** BEGIN LOGGING AT Sun Oct 01 10:39:03 2017
Oct 01 14:52:03 <peacememories> is it just me or has combo-layer not been updated in a _while_? i went to check it out but the examples on the wiki page (even the supposedly current config repo for poky) are from 2014
Oct 02 00:56:40 <sr105> Can I put DEBUG_BUILD="1" in my image recipe instead of local.conf
Oct 02 00:56:42 <sr105> ?
Oct 02 00:57:57 <sr105> I have a production and a development image. I'd like the dev one to use DEBUG_BUILD.
Oct 02 01:17:29 <bluelightning> sr105: I'm afraid not, the image recipe can't make any changes to how other recipes are built, it can only select packages to install (and tweak the resulting files after the fact)
Oct 02 01:18:09 <sr105> Is there a way I could have two different distros where the debug one requires the regular one and sets debug flags?
Oct 02 01:18:32 <sr105> It seems like the distro is set in our local.conf currently.
Oct 02 01:33:06 <bluelightning> sr105: yes, certainly - you'd just need to have a separate .conf file that "require"s the main one - see meta-poky/conf/distro/poky-bleeding.conf for an example
Oct 02 01:38:52 <sr105> But since the local.conf is the place that determines the DISTRO to use, can I make it use a different distro for different image recipes or do I have to setup some sort of multi-build environment?
Oct 02 01:42:48 <sr105> I should probably ask the real question: Is it possible to change local/distro configuration depending on the image being built? i.e. Can I set it up to know to use DEBUG_BUILD="1" if I build my dev images, but not for production images?
Oct 02 01:42:53 <sr105> Thanks for the help.
Oct 02 02:54:26 <bluelightning> sr105: I'm afraid not, you'd effectively need two separate build environments (though DISTRO could be set from the command line i.e. "DISTRO=abc bitbake my-image" as long as you ensure DISTRO is set using ?= in local.conf)
**** ENDING LOGGING AT Mon Oct 02 03:00:01 2017