**** BEGIN LOGGING AT Thu Mar 06 17:53:55 2014 **** ENDING LOGGING AT Thu Mar 06 18:00:42 2014 **** BEGIN LOGGING AT Thu Mar 06 18:02:19 2014 **** ENDING LOGGING AT Thu Mar 06 18:06:04 2014 **** BEGIN LOGGING AT Thu Mar 06 18:08:20 2014 Mar 06 19:40:17 ? for teh bb knowledgable - can I make a bb recipe's inheritance based on whether a class exists? Mar 06 19:41:06 that would be a very bad idea Mar 06 19:41:24 its not doable with inherit. you could hack something with include, likely Mar 06 19:41:38 'include classes/foo.bbclass' wouldn't fail if it didn't exist Mar 06 19:41:47 but more likely you should take a step back and find a better way to do what you want Mar 06 19:44:28 OKay. Here's the situation as it stands for us: Mar 06 19:45:46 We have a recipe in a seperate layer from a .bbclass, that class is qt4core.bbclass, which is a reduced set of qt4 that builds only the core, without X11/webkit for server appliance. In another layer, there is a recipe that currently depends on this Mar 06 19:46:12 That layer is usable without the other layer (obivously) and most things built with that layer actually use qt4x11 as is Mar 06 19:46:48 So for the layer stack that includes this server appliance, we'd want to build against that qt4core base, vs the qt4X11 Mar 06 19:47:11 i'd say have your distro bbappend the recipe to inherit the qt4core recipe. let the distro control such policy choices, rather than any particular layer controlling it Mar 06 19:47:14 * kergoth shrugs Mar 06 19:47:21 s/core recipe/core class/ Mar 06 19:47:44 Okay, so bbappend the software recipe to override the inherits? Mar 06 19:48:34 you can't override them, unless the recipe was altered to use a variable, you can't "un-inherit" something, but i'm guesing inheriting qt4core after qt4x11 would blow away the variables in question, but if not you could alter the recipe in the layer to use a variable that an append can override Mar 06 19:48:47 obviously there are any number of possibilities, but that's probably the one i'd go with, myself Mar 06 19:49:20 Could you provide some theoretical example? Mar 06 19:50:49 for which? if 'inherit qt4x11 qt4core' resulted in not building for x11 (since qt4core came after qt4x11), then its trivial. if not, then you'd have to have a way to control which class the recipe inherits. inherit ${QT5CLASS} or something, or even directly inherit based on a PACKAGECONFIG which your distro could set, or.. lots of options Mar 06 19:51:11 * kergoth ponders Mar 06 19:58:49 Yeah, inherit qt4x11 qt4core would break on not-found for qt4core.bbclass Mar 06 19:58:54 which is what it does not Mar 06 19:59:13 So, I suppose if a variable can be overridden prior to inheritance that might do it Mar 06 19:59:23 no, it wouldn't if the layer was included Mar 06 19:59:49 Right, but I'd like to not use the layer whcih qt4core.bbclass came from Mar 06 20:00:20 that layer or your distro layer could append it to also inherit qt4core, if it would override the qt4x11 bits. so the recipe could be left inh eriting qt4x11 only Mar 06 20:00:33 but if it wouldnt 'override, then you'd need some sort of variable to prevent the other from being included Mar 06 20:00:38 afk, food Mar 06 20:01:30 hrmm **** ENDING LOGGING AT Fri Mar 07 02:59:58 2014