From: Mike Westerhof <mike@mwester.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] Support building all project in one directory
Date: Thu, 14 Jan 2010 21:47:25 -0600 [thread overview]
Message-ID: <4B4FE54D.3070402@mwester.net> (raw)
In-Reply-To: <op.u6jv0uycmn1qzu@guohr-laptop-ubuntu>
Guo Hongruan wrote:
> 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.
But most -- in fact all except perhaps yourself and a few of the OE core
team don't build with different LIBCs in the same TMPDIR. So all that
your patch does for the overwhelming number of users of OE is add
additional directory levels to an already complicated directory
structure, and provides them with absolutely no benefit whatsoever.
At the very least, you really should provide a means to selectively
enable this -- although I still don't see why it makes sense to support
multiple LIBCs in the same TMPDIR.
-Mike (mwester)
next prev parent reply other threads:[~2010-01-15 3:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-14 7:55 [PATCH] Support building all project in one directory Guo Hongruan
2010-01-14 9:14 ` Marcin Juszkiewicz
2010-01-14 9:19 ` Guo Hongruan
2010-01-14 19:53 ` Khem Raj
2010-01-15 1:35 ` Guo Hongruan
2010-01-15 3:47 ` Mike Westerhof [this message]
2010-01-15 9:17 ` Guo Hongruan
2010-01-15 9:56 ` Phil Blundell
2010-01-15 10:42 ` Guo Hongruan
2010-01-15 10:46 ` Phil Blundell
2010-01-15 10:59 ` Guo Hongruan
2010-01-15 12:50 ` Phil Blundell
2010-01-15 12:57 ` Guo Hongruan
2010-01-15 13:02 ` Phil Blundell
2010-01-15 13:09 ` Guo Hongruan
2010-01-15 11:00 ` Koen Kooi
2010-01-15 10:43 ` Guo Hongruan
2010-01-15 6:33 ` Marcin Juszkiewicz
2010-01-15 8:23 ` Koen Kooi
2010-01-15 9:23 ` Guo Hongruan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4B4FE54D.3070402@mwester.net \
--to=mike@mwester.net \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.