**** BEGIN LOGGING AT Tue Sep 26 03:00:02 2017 Sep 26 12:13:56 how can I add my custom variable into myimage.bb and make it visible in other recipes? Sep 26 14:18:41 Dvorkin: what's the nature of the variable? Such a thing usually is in a conf file that's considered for how you've configured a particular (set) of builds Sep 26 15:01:51 hey Sep 26 15:02:29 i'm trying to build a tool inside openembedded/bitbake and make it available to the host system afterwards Sep 26 15:03:54 i already made the package extend the native bbclass, but i dont seem to be able to figure out how to make it available to the host system while in the build env Sep 26 15:14:16 the host generally, or inside another recipe's build Sep 26 15:47:24 rburton: the host generally, i'm building a tool that i need to use later to build a package from the built image Sep 26 15:48:17 what I did now and what works, but seems like a terrible hack: Sep 26 15:48:25 https://www.irccloud.com/pastebin/TEmXPwMT/ Sep 26 15:50:15 bmouring, it's a variable that signals to some recipes to install one or other config file Sep 26 15:53:45 domme: should be easy enough to deploy a native properly Sep 26 15:54:06 rburton: hehe, but.. how? Sep 26 15:56:22 well for a start just copy the binary not the entire sysroot :) Sep 26 15:58:49 rburton: well, it depends on shared libs etc Sep 26 15:59:50 domme: can you build it statically, or make it build against the host? Sep 26 16:00:44 rburton: it should have no superfancy dependencies, so one could possibly build it against the host ... how does one do that? Sep 26 16:00:57 well it will by default as its native Sep 26 16:01:05 rburton: oh! Sep 26 16:01:08 (unless you're using uninative) Sep 26 16:02:59 rburton: okay, that would be possible - but i'd lose the niceties of having all deps in exactly defined versions.. there's no proper way of setting up such a sysroot externally, right? I know, I could traverse deps and install only libs to the deploy dir.. but that's a bit tedious Sep 26 16:03:18 master or ? Sep 26 16:03:53 rburton: what do you mean? openembedded master? Right now pyro, but I could probably switch if that would be needed for anything Sep 26 16:04:45 with a two liner i verified m4 Just Works Sep 26 16:04:45 $ /data/poky-tmp/master/deploy/images/intel-corei7-64/m4 --version Sep 26 16:04:46 m4 (GNU M4) 1.4.18 Sep 26 16:04:59 thats just with thi Sep 26 16:05:00 +inherit deploy Sep 26 16:05:00 +addtask deploy after do_install before do_build Sep 26 16:05:02 +do_deploy() { Sep 26 16:05:02 + install ${B}/src/m4 ${DEPLOYDIR} Sep 26 16:05:04 +} Sep 26 16:05:28 obviously a hack install, but m4 has minimal deps so it works on the host fine Sep 26 16:05:44 so does your tool have any deps to native libraries in the sysroot? Sep 26 16:06:25 rburton: various boost libs, openssl, ... Sep 26 16:10:11 domme: well pyro has recipe-specific-sysroots so copying over the entire sysroot isn't ideal but works Sep 26 16:10:39 you could generate a fresh one instead of rsyncing but that's just prettier, same end result Sep 26 16:13:33 rburton: okay, and what does master do? Sep 26 16:14:03 same, i meant pyro/master. can never remember when recipe-specific-sysroots landed :) Sep 26 16:14:04 Dvorkin: this sort of this really should live in a distro (or machine, or local) conf file Sep 26 16:17:55 rburton: okies :-) have a rough idea about it all now, i guess what i have now works for me .. and can be optimized when I have the time for it Sep 26 16:19:38 bmouring, maybe I can use PACKAGECONFIG for this? Sep 26 16:26:36 rburton: so.. thanks for the infos :) Sep 26 16:53:48 Dvorkin: so the differences in file you want to install in these separate packages is controlled in all of these packages by their respective configuration/build systems? (e.g. each recipe that you care about defines "PACKAGECONFIG[foo]" configuration control, and this configuration change will control which package is installed?) We're talking in such abstracts that it probably warrants you explaining a bit more what you're trying to do Sep 26 20:29:02 bmouring, I have one recipe with two configuration files. this recipe is required by several other recipes. but depending on Image i'm building I need change this configuration files. that's all. Easy task I can't find a solution for a long time... Sep 26 20:53:09 Dvorkin: so, imageA -> (one or more packages) -> packageFOO and imageB -> (one or more packages) -> packageFOO, and for imageA you want packageFOO to include one config file, but in imageB packageFOO should include another config file, is that correct? **** ENDING LOGGING AT Wed Sep 27 03:00:00 2017