[oe] [PATCH] Support building all project in one directory

[Guo Hongruan]

在 Fri, 15 Jan 2010 17:56:39 +0800，Phil Blundell <philb at gnu.org> 写道:

> 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.

OE should provide a mechanism which should not restrict one certain libc  
type.

Even though every distro supports only one libc type, you should be better  
add ${LIBC} into your pathnames if you are trying to build multiple  
projects (which use different libc) in one directory. To illustrate this  
problem, let suppose that: you are trying to build DISTR_A which uses  
glibc and DISTRO_B which uses eglibc for qemumips machine, What would  
happended when building them in one directory?

tmp/work/mips-oe-linux/libassuan-0.6.9-r0

You can not tell which the package building of libassuan is based on. And  
in fact, the next building will use the wrong temp files of packages  
libassuan-0.6.9-r0. This case will cause some little questions which is  
very very difficult to debug.

Most of the OE users do not need to build multiple projects in one  
directory, but the QA does. The QA team need to setup regression test  
environment. Without sharing, how much building time and disk space it  
will consume!


-- 
Guo Hongruan, Embedded Linux Consultant
Skype: camelguo
Twitter: camelguo
http://www.gulessoft.com