**** BEGIN LOGGING AT Wed Jul 20 02:59:58 2016 Jul 20 07:26:05 morning Jul 20 11:24:28 Hi guys, what is the best way of having two recipes (-native and nativesdk-) that share excatly the same metadata? Jul 20 11:24:50 What I have so far is a recipe.inc and two recipe-native.bb, nativesdk-recipe.bb Jul 20 11:25:23 On each recipe I add inherit native, or nativesdk, and include recipe.inc. Jul 20 11:25:56 The problem are the DEPENDS and RDEPENDS that need have the respective -native or nativesdk- names. Jul 20 11:32:14 have a recipe.bb which does BBCLASSEXTEND=native nativesdk Jul 20 11:32:15 done Jul 20 11:32:46 The problem is that I don't want that recipe to support target class. Jul 20 11:32:54 fine, ignore that Jul 20 11:33:14 howcome? OE will still allow to build it and it will fail in my case. Jul 20 11:33:16 the alternative to using bbclassextend is either writing two recipes, or writing a pile of python to auto-translate Jul 20 11:33:26 put some python in so it refuses to build in the target case? Jul 20 11:33:34 or, it will fail, so what's the problem Jul 20 11:34:01 Well, what I did is the following: Added BBCLASSEXTEND=native in the recipe-native.bb and the same for the nativesdk recipe. Jul 20 11:34:08 Is that appropriate? It works Jul 20 11:34:32 don't see the point over just using bbclassextend with recipe.bb Jul 20 11:34:47 Because I don't want to allow the recipe to build for target. Jul 20 11:34:55 so write a line of python to forbid that Jul 20 11:35:09 I have no idea how to do it, TBH. Jul 20 11:35:10 you asked, i told you what my opinion is :) Jul 20 11:35:38 Ross, you know that looks more hacky, come on.. :) Jul 20 11:36:04 if class is target, raise skippackage Jul 20 11:36:24 Will not trigger its dependencies build? Jul 20 11:36:28 two lines of anon py. or, put a # TODO: patches welcome to make target builds work Jul 20 11:37:05 Right... Jul 20 11:37:54 if you want two separate recipes then inheriting native or nativesdk is likely better than using bbclassextend Jul 20 11:38:17 Well, That's what I did, but it will fail to recognize the dependencies properly. Jul 20 11:38:41 If I don't add bbclassextend, the native.bbclass won't add the -native to the DEPENDS. Jul 20 11:38:44 :/ Jul 20 11:39:34 take a look at native_virtclass_handler() in native.bbclass Jul 20 11:39:49 BTW, I am using jethro. Jul 20 11:40:19 Didn't check if Krogoth has this. Jul 20 11:41:44 right, youll need to manually handle those Jul 20 11:55:13 yep. Jul 20 19:48:21 BBCLASSEXTEND is best approach whats the harm in leaving it alone for target you are not needing it anyway or are there specific reasons to disable native compile ? Jul 20 19:49:15 you can always add COMPATIBLE_HOST_class-target = (null) Jul 20 19:49:21 and be done with it Jul 20 19:56:58 yeah thats a good solution Jul 20 19:57:25 i'd say why not leave it for target as its a very rare tool that you'll want for native and nativesdk but will *never* want on target Jul 20 19:57:37 so leave it to break and whoever wants it, can fix it first Jul 20 20:41:20 that too **** ENDING LOGGING AT Thu Jul 21 02:59:58 2016