From: Colin Walters <walters@verbum.org>
To: Mark Hatle <mark.hatle@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] autotools.bbclass: Add functionality to force a distclean when reconfiguring
Date: Sat, 08 Sep 2012 11:36:25 -0400 [thread overview]
Message-ID: <1347118585.2583.14.camel@lenny> (raw)
In-Reply-To: <504B4880.5000304@windriver.com>
On Sat, 2012-09-08 at 08:30 -0500, Mark Hatle wrote:
> In principal I agree completely, however in practice at least 20-30% of the
> packages I try won't deal w/ the B/S separation properly.
So what I did in my most recent build system[1] is:
1) Default to srcdir != builddir
2) Tag modules which don't support that
See: http://people.gnome.org/~walters/docs/build-api.txt
If a module doesn't support srcdir != builddir, I simply copy the source
tree to the builddir. This is can be a confusing trap from a developer
perspective; I've caught myself editing the copied source files, and
then had them blown away during a build.
But in general we should pressure upstreams to support srcdir !=
builddir, because the benefits are great and the drawbacks small.
It'd be awesome if you guys considered having the bitbake autotools
class implement the same semantics.
[1]
http://git.gnome.org/browse/gnome-ostree/tree/src/ostbuild/pyostbuild/builtin_compile_one.py#n132
next prev parent reply other threads:[~2012-09-08 15:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-07 16:05 [PATCH] autotools.bbclass: Add functionality to force a distclean when reconfiguring Richard Purdie
2012-09-07 16:32 ` Mark Hatle
2012-09-07 16:37 ` Richard Purdie
2012-09-07 16:42 ` Burton, Ross
2012-09-07 17:09 ` Richard Purdie
2012-09-07 17:15 ` Phil Blundell
2012-09-08 8:05 ` Khem Raj
2012-09-08 13:30 ` Mark Hatle
2012-09-08 15:36 ` Colin Walters [this message]
2012-09-08 15:44 ` Colin Walters
2012-09-08 15:49 ` Mark Hatle
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=1347118585.2583.14.camel@lenny \
--to=walters@verbum.org \
--cc=mark.hatle@windriver.com \
--cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox