On Thu, 2011-12-08 at 11:14 +0100, Koen Kooi wrote: > Op 8 dec. 2011, om 10:34 heeft Xiaofeng Yan het volgende geschreven: > > > From: Xiaofeng Yan <xiaofeng....@windriver.com> > > > > gtk run over x11 at current OE-core. If gtk want to run over directfb, then > > \ > > the configuration related to x11 should be disabled and directfb should be > > enabled. > > Since I still can't get an answer to "what happens when you enable both x11 > and directfb as distro features",
The answer to that question seems to be that you will get undefined behaviour. Both PACKAGECONFIG flags will match so you'll get the configure options for both of them, but the packageconfig mechanism doesn't appear to guarantee what the ordering will be. (You might expect that it would be the order of the entries in PACKAGECONFIG itself but, from a quick look at the code, that doesn't appear to be the case.) So, you'll end up with both sets of things in DEPENDS and either: --with-x=yes --with-gdktarget=x11 --with-gdktarget=directfb or --with-gdktarget=directfb --with-x=yes --with-gdktarget=x11 in EXTRA_OECONF but there doesn't seem to be any obvious way to predict which it'll be. It would be nice if there was a way to declare PACKAGECONFIG options as conflicting with each other so that you'd get a diagnostic if you tried to turn both on. But there's no mechanism to support that at present and it doesn't seem like it would merit ad-hoc python hacks in the gtk+ recipe. p. _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
