**** BEGIN LOGGING AT Fri Jun 26 03:01:39 2020 Jun 26 19:38:31 JPEW: is there a way to have a dynamic dependency on a layer (e.g. meta-arm) based on the $MACHINE? Jun 26 19:43:36 MACHINE isn't defined until local.conf is parsed, long after the layers are dealt with, if you mean layer dependencies Jun 26 19:54:48 kergoth: okay. not what i was hoping for, but thanks Jun 26 19:55:31 yeah.. there are a lot of badly behaved bsp layers out there that aren't properly conditional on MACHINE, so it's hard to support multiconfig and the like with them in the mix, you can't leave them enabled Jun 26 19:56:02 that's why i'm still pulling in a different set of layers based on MACHINE in mentor's setup scripts and mandating re-sourcing them when switching machines for us right now, not ideal Jun 26 19:58:13 tlwoerner: I remember looking at this when I was setting up the Oryx distro. The best you can do is emit a warning at parse time if MACHINE is set to something that requires a layer that isn't present Jun 26 20:00:35 with meta-rockchip some MACHINEs need the AT-F from meta-arm/meta-arm, but others don't, but the entire layer depends on meta-arm, even though only some builds would actually need it Jun 26 20:16:13 tlwoerner: Ya, theres not way to do that currently Jun 26 20:20:43 what about a bbappend with COMPAT machines defined or AT-F_{rockchip machine name} Jun 26 20:23:34 or move it to core **** ENDING LOGGING AT Sat Jun 27 02:59:57 2020