Op 16 mei 2011, om 15:50 heeft Richard Purdie het volgende geschreven: > On Mon, 2011-05-16 at 15:11 +0200, Koen Kooi wrote: >> Op 16 mei 2011, om 13:41 heeft Richard Purdie het volgende geschreven: >> >>> On Mon, 2011-05-16 at 02:55 -0700, Khem Raj wrote: >>>> On Sun, May 15, 2011 at 11:58 PM, Koen Kooi <k...@dominion.thruhere.net> >>>> wrote: >>>>> >>>>> Op 16 mei 2011, om 08:04 heeft Khem Raj het volgende geschreven: >>>>> >>>>>> Do not define DEPLOY_DIR_IMAGE >>>>>> Append -uclibc to STAGING_DIR_TARGET only for target recipe and cross >>>>>> recipes >>>>>> Append -uclibc to STAGING_DIR_HOST only for target recipes. >>>>>> >>>>>> These changes make sure that we still share the native sysroot >>>>> >>>>> I still stay we append tclibc unconditionally. >>>> >>>> yes thats would simplify things if we agree to use TCLIBC in bitbake.conf >>> >>> We can't depend on TCLIBC in bitbake.conf since someone still has the >>> option of not using the standard configuration boilerplate we're >>> providing. >> >> So we can't add TCLIBC ??= eglibc to bitbake.conf? > > No, I can just see the bug reports for uclibc building in a directory > called XXX-eglibc as the user had only set the PREFERRED_PROVIDER > variables.
Do you really care about such usecases? Someone who thinks he is too smart to use the includes can 'fix' the paths himself, no? _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
