-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 17-05-11 08:23, Anders Darander wrote: > On Mon, May 16, 2011 at 18:49, Phil Blundell <[email protected]> wrote: >> On Mon, 2011-05-16 at 14:52 +0200, Frans Meulenbroeks wrote: >>> I think the community could benefit if you add info (a pointer) in this >>> thread >>> - how to set up a build environment >>> - policies on what goes into oe-core and meta-oe and what not (and how to >>> deal with things that do not go into it) > > Yes, this is definitely needed. Which type of new > applications/libraries can get into meta-oe, and which are supposed to > be kept in higher layers... > > In what cases can additional versions of the recipe in oe-core be > added? E.g. dbus is built using 'EXTRA_OECONF = "--with-x"', which at > least on head-less systems seems to be overkill.
Dbus is a really good example where the above knee-jerk reaction is misplaced :) The --with-x only turns on building dbus-launch, which is x specific, but that's the only bit that is. All the other dbus subpackages lack X dependencies. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) iD8DBQFN0hfyMkyGM64RGpERAmkdAJ96oZbdWIr0vN9+ys7FNBGoH2HtaACfVyTl /5bZEgjnUvyLTFB9apyiFQc= =XEmW -----END PGP SIGNATURE----- _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
