**** BEGIN LOGGING AT Sun Nov 04 03:00:02 2012 Nov 04 16:42:14 hi! I try to understand the open embedded build system. I own a logitech squeezebox - on slimdevices you can find some repository. Nov 04 16:43:03 I'm able to bitbake a subversion checkout and creating a squeezeos image. Nov 04 16:43:43 the images is a collection of a linux kernel and the userspace (cramfs). Nov 04 16:44:21 there are also build a lot of *.ipk packages but the userspace does not provide any "opkg-cl" binary. Nov 04 16:45:32 can somebody tell me the common way to get "opkg" running on OE? Nov 04 16:48:42 in other words: where is the central bitbake configuration located for bootstrapping the rootfs? Nov 04 16:54:01 hmm, maybe the yocto project is more related to my build system. Nov 04 16:58:39 isn't yocto kindof a wrapper around oe? Nov 04 17:04:56 yocto's buildsystem is poky. poky ~= bitbake+oe-core+meta-yocto. most oe folk use, by contrast, bitbake+oe-core+meta-openembedded Nov 04 17:05:08 but the core metadata is shared (oe-core, aka poky/meta) Nov 04 17:08:41 Yocto's build system is openembedded core, poky is oe-core + meta-yocto Nov 04 17:08:56 hmm, I think you just said that :) Nov 04 17:09:25 The Yocto Project is a group of tools to make embedded development easier Nov 04 17:09:32 I think I ahve al that right :) Nov 04 17:12:02 ever seen tar crap out during do_rootfs ? Nov 04 17:13:39 trying to get things building on another machine with the same set of recipes (that build fine on my server) and getting different behavior is annoying... **** ENDING LOGGING AT Mon Nov 05 02:59:59 2012