**** BEGIN LOGGING AT Mon Aug 12 02:59:58 2013 Aug 12 16:55:38 bluelightning: hi! the @base_contains('DISTRO_FEATURES', 'systemd',... thing in the neard reciept, does this need some fancy new bitbake? Aug 12 16:55:56 freinhard: not at all Aug 12 16:56:16 the base_contains mechanism is very old Aug 12 16:57:02 you could check if your DISTRO_FEATURES value contains systemd, maybe that's the issue Aug 12 16:57:12 how would i do that? Aug 12 16:57:21 btw i'm building meta-angstrom/recipes-images/angstrom/systemd-image.bb Aug 12 16:57:25 bitbake -e | grep ^DISTRO_FEATURES= Aug 12 16:59:04 yes, that's the issue Aug 12 17:00:44 systemd got added to angstrom.inc in january Aug 12 17:00:48 ah right, which version of angstrom are you building with? Aug 12 17:00:55 https://github.com/Angstrom-distribution/meta-angstrom/commit/b63c87cb318171cd67ced79583e12f778351dd71 Aug 12 17:01:32 i'm building whatever version the setup-scripts point to by default atm Aug 12 17:02:06 hmm, I can only guess it's older than this version Aug 12 17:02:45 yes, anyways the reciept should work with that version as well Aug 12 17:03:19 I think you can safely exclude that check in any case Aug 12 17:03:29 current versions don't need it Aug 12 17:03:44 sysinitv is deprecated? Aug 12 17:03:50 no, not at all Aug 12 17:04:11 ok, so i would need to ship /etc/init.d/ scripts as well? Aug 12 17:04:13 but if systemd isn't enabled we just delete the whole systemd_unitdir directory automatically Aug 12 17:04:44 ultimately it depends if you care about the recipe being used on sysvinit systems... but for broadest usage yes Aug 12 17:05:22 that's what i get http://paste.kde.org/pd4f652ae/ Aug 12 17:05:54 well, yes i care, otherwise having the reciept public wouldn't make sense Aug 12 17:07:26 right Aug 12 17:10:25 freinhard: it looks like you'd get that error if you hadn't installed the systemd unit file into the correct directory Aug 12 17:12:41 http://paste.kde.org/p5e8c2c30/ Aug 12 17:12:56 if i comment line 34/38 i don't get that error message Aug 12 17:13:13 i installed the package and launched hd-idle via systemctl Aug 12 17:13:34 so i guess it's just the DISTRO_FEATURES issue Aug 12 17:13:50 (general comments to the hd-idle.bb are welcome ;) ) Aug 12 17:14:32 freinhard: I'd say just drop that conditional Aug 12 17:15:24 also use hd-idle.service rather than ${PN}.service (since the file you're installing isn't named with ${PN}) Aug 12 17:15:53 of course they're the same now but if the recipe got renamed then you'd want them to remain the same Aug 12 17:16:46 do_compile should use oe_runmake and you probably need some arguments to make sure it's using the cross-compiler etch Aug 12 17:16:51 s/etch/etc/ Aug 12 17:17:20 remove setting DEPENDS and RDEPENDS to "", these won't be doing anything Aug 12 17:23:23 this article just does a plain make, that's why i didn't care: http://www.openembedded.org/wiki/How_to_create_a_bitbake_recipe_for_dummies#Recipe_Template Aug 12 17:24:01 right, that article is definitely out-of-date as noted at the top of the page Aug 12 17:25:35 freinhard: http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#usingpoky-extend-addpkg Aug 12 17:26:43 bbiab Aug 12 17:37:37 better? http://paste.kde.org/pf5a8e7d3/ Aug 12 17:39:47 i stripped the EXTRA_OEMAKE to the variables used by the upstream Makefile Aug 12 18:13:57 freinhard: looks OK Aug 12 18:14:14 freinhard: I'd suggest setting SUMMARY instead of DESCRIPTION for a one-line description such as that Aug 12 19:38:28 Hello, I'm trying to build angstrom-staging-yocto1.4, but it seems there is a recipe missing in  meta-angstrom/recipes-tweaks/connman can anyone confirm this? Aug 12 19:44:27 i.e. target connman-angstrom-settings has no provider, but it is required by systemd-image Aug 12 20:03:31 http://bit.ly/1d0FLZC Aug 12 21:13:46 SlashV: I noticed that earlier, not sure what has happened ther Aug 12 21:13:47 e Aug 12 21:13:53 Crofton|work: fixit :-D Aug 12 21:16:16 urg **** BEGIN LOGGING AT Mon Aug 12 22:07:04 2013 **** ENDING LOGGING AT Tue Aug 13 02:59:59 2013