In fact, I should implement it as a single bbclass file, which let you
enable or disable it through 'inherit'
在 Fri, 15 Jan 2010 17:56:39 +0800，Phil Blundell <[email protected]> 写道:
On Fri, 2010-01-15 at 17:17 +0800, Guo Hongruan wrote:
Without ${LIBS}, sometimes
it is difficult to determine which libc the runtime image is based on.
For the majority of DISTROs, there is only a single supported C library
anyway so there should be no ambiguity. For example, if you build for
micro-uclibc, that means you are using uClibc. If you build for micro,
that means you are using eglibc.
So, I would not be in favour of rearranging the filesystem layout for
those DISTROs to make the selection of libc explicit in the pathnames.
p.
_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
--
Guo Hongruan, Embedded Linux Consultant
Skype: camelguo
Twitter: camelguo
http://www.gulessoft.com
_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
