在 Fri, 15 Jan 2010 03:53:01 +0800，Khem Raj <[email protected]> 写道:
On (14/01/10 17:19), Guo Hongruan wrote:
After changing this way, the native tools can be shared with
different buildings.
They get shared even now. I have my TMPDIR = /scratch/oe/build and
DEPLOY_DIR = ${TMPDIR}/deploy/${LIBC}
I share the native tools all the time
This way, the packages built in ${TMPDIR}/work/ will bother each other. It
is obvious that a binary package built based on uclibc is different with
the same one built base on glibc. So I think it's better to classify them
using ${LIBC}.
After applying my patch, all everything built based on uclibc will be
placed in some directories different with glibc,eglibc. The stamps will be
placed in ${TMPDIR}/stamps/${LIBC}, the package data will be placed in
${TMPDIR}/pkgdata/${LIBC} and so on. So you can see, when I tried to build
lots of projects (with different libc), their data will never bother each
other. In you way, we must select different TMPDIR for different libc,
that are very convenient for incremental building by QA.
And more, the native tools (quilt-native, qemu-native) are completely libc
independent, so they could be shared with projects with different libc.
After applying the patch, native tools are shared. It will save my
building machine lots of time on building native tools.
-Khem
_______________________________________________
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
