**** BEGIN LOGGING AT Sat Nov 07 02:59:59 2015 Nov 07 11:32:24 hey guys Nov 07 11:32:31 i have a question i have a cubieboard 2 Nov 07 11:32:44 and i am wondering if OE would be a good way to start building my own highly customized environement Nov 07 11:49:57 eagles0513875_: oe is a good way to build highly customized linux distributions, thats for certain. how much it fits your usecase is something else, though Nov 07 11:50:22 LetoThe2nd: i have a cubieboard 2 with an all winner a20 dual core armv7 Nov 07 11:50:30 i want something super light and highly performant Nov 07 11:50:32 eagles0513875_: depending on your experience and aims it might be easier to just use a standard distro and beat it into shape for your usecase. Nov 07 11:50:33 if possible Nov 07 11:50:41 LetoThe2nd: ok Nov 07 11:50:49 LetoThe2nd: then what would be the use case to go for OE Nov 07 11:51:10 eagles0513875_: the standard usecase for OE is reproductibility from scratch. Nov 07 11:51:30 LetoThe2nd: meaning what Nov 07 11:51:31 eagles0513875_: paired with high customavbility Nov 07 11:51:42 couldnt you get both of those wiht a standard distro which you customize Nov 07 11:51:46 like debian for example Nov 07 11:52:21 eagles0513875_: meaning that when you build your image with oe once, you can be sure to reproduce it later, and also reproduce a modified version later - without needing to go through the whole process again. Nov 07 11:52:58 eagles0513875_: so OE and comparable things are a good fit if you want to create firmware for prodcution runs, for example Nov 07 11:53:28 eagles0513875_: if you want a one of a kind, like for your home tinkering box, starting off debian is way less frustration prone Nov 07 11:53:47 LetoThe2nd: im already rather frustrated as i have no idea how i am going to get a system on my cubieboard 2 Nov 07 11:53:50 or where to start lol Nov 07 11:54:47 eagles0513875_: well thats out of the OE focus as well as out of that of any other distro as well Nov 07 11:55:02 eagles0513875_: e.g., read the documentation for your board. Nov 07 11:55:46 LetoThe2nd: sadly there isnt much for it Nov 07 11:56:40 eagles0513875_: i see, but neither OE nor debian or anything else will help you in getting that ironed out first. Nov 07 11:57:49 ya i hear ya Nov 07 11:57:59 LetoThe2nd: really reproducible builds are unlikely to work with OE though, aren't they? Nov 07 11:58:28 I mean I see recipes depend on things that are installed on the host instead of -native packages and such Nov 07 11:59:15 tbr: shouldn't be much besides the toolchain, in fact. but of course, lazy recipe writers can always whack that up. Nov 07 12:00:39 also unless you whack your cache into oblivion after doing something non-standard you're likely to pollute your builds due to other headers being available and possibly detected by your other packages Nov 07 12:01:23 tbr: well i didn't say reproductibility comes always and for everyone. Nov 07 12:01:52 sure, just checking if I missed something Nov 07 12:04:04 :-) Nov 07 12:22:02 tbr most host depends are things that are hard to bootstrap around or really stable Nov 07 12:22:08 note I said most :) Nov 07 12:22:33 and use a vm, chroot or something simialr :) Nov 07 12:22:46 Crofton|work: as long as recipe writers take care, and not the easy route. meta-atmel for example has a nasty hidden dependency on hosts pandoc Nov 07 12:23:32 xbmc/kodi is a minefield in this regard. I found at least 5 undeclared host dependencies when building on a clean VM Nov 07 12:24:11 and e.g. openjdk doesn't even build as native dependency, so you can't even fix it Nov 07 12:27:39 i'd like to package my rootfs, kernel and dtb into a single firmware update file. Where would be the best place to do this? Add the packaging as a new "IMAGE TYPE", or just add a new task to my image recipe? Nov 07 12:28:03 mago_: have a look at stefano babics swupdate layer Nov 07 12:28:20 mago_: that offer some magic around this. Nov 07 12:28:29 LetoThe2nd: ah, great. it's actually swupdate im using :) Nov 07 12:28:48 mago_: i you only want to have kernel and dtb in the rootfs, jetzt add the packages to IMAGE_INSTALL Nov 07 12:30:24 LetoThe2nd: no, i meant i want to package rootfs, kernel and dtb into the compound image. i dont want kernel and dtb inside the rootfs Nov 07 12:30:36 but meta-swupdate/classes/swupdate.bbclass seem to be what i need Nov 07 12:30:49 tbr: can't say i'm surprised. i tried to package r-lang and ran into all kind of ugly s**t concerning fortran Nov 07 12:31:06 mago_: :-) Nov 07 12:38:21 LetoThe2nd: oh boy, that file was really ..magic =) Nov 07 13:01:59 heh, fun: the nodejs package is only about 2.5m, but pulls in roughly 11m dependencies in relation to core-image-minimal Nov 07 13:09:17 LetoThe2nd: have you used this swupdate.bblcass yourself? i don't fully understand how to use it, i suppose i inherit it from my image recipe. And set SWUPDATE_IMAGES to the stuff i want in my compound, and also put a sw-description into my image SRC_URI? Nov 07 13:09:37 LetoThe2nd: i don't understand why it resets COMPRESSIONTYPES though? Nov 07 13:10:22 mago_: i have no hands-on experience with it, sorry. i just suggested it because i know that our update mechanisms also relies on it (but isn't maintained by me) Nov 07 13:14:46 okay, thanks anyway Nov 07 13:20:18 out of interest - how do people automate the installation of npm packages into images? Nov 07 13:21:29 LetoThe2nd: i don't think ppl do, .. i asked the same thing a few weeks ago, and turns out it's too messy. Someone linked me a meta-layer where they managed it using some kind of registry files that had to be updated whenever a npm module was updated Nov 07 13:21:57 mago_: so people just generate some application blob and copy that verbatim? Nov 07 13:24:50 no, you can run npm from recipes, but it'll download any dependencies without bitbake knowing about it Nov 07 13:25:18 there's also this meta-nodejs, but it also does not solve the problem of dependencies Nov 07 13:25:35 hmhm Nov 07 13:25:49 .. but it does introduce a npm:// fetcher for bitbake, which is nice Nov 07 13:26:05 ah really? let me see.... Nov 07 13:27:37 or, hold on.. maybe that was some other layer :) now that i look, i can't see any mention of npm:// Nov 07 13:28:02 here it is, https://github.com/imyller/bitbake-npm Nov 07 13:29:04 thx Nov 07 17:20:11 /whois sbabic Nov 07 17:20:30 wops **** ENDING LOGGING AT Sun Nov 08 02:59:58 2015