Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Design issue with the out-of-tree support
Date: Mon, 27 May 2013 21:53:54 +0200	[thread overview]
Message-ID: <20130527215354.133444a6@skate> (raw)
In-Reply-To: <51A3B793.6050409@mind.be>

Dear Arnout Vandecappelle,

On Mon, 27 May 2013 21:44:19 +0200, Arnout Vandecappelle wrote:

> > For now, I consider doing the prepare step even on OVERRIDE_SRCDIR
> > package, even if that means that we are modifying the source directory.
> 
>   Given that we've recently accepted some patches that solve problems of 
> non-writeable source directories, I don't think this is appropriate. I 
> think it's a valid use case to use OVERRIDE_SRCDIR to define the custom 
> source of a package, which is located in some shared directory. Having 
> random builds modifying that source is not appropriate.
> 
>   And now is the time to define this behaviour - changing it later can be 
> considered "ABI breakage".

Right.

What about packages that are using the "local" site method (which
basically, are equivalent to doing OVERRIDE_SRCDIR) ?

I know some people (or, said otherwise, customers) that use the local
SITE_METHOD for autotools-based components. Those are version
controlled, and of course, only configure.ac + Makefile.am are version
controlled. So, when the build starts, "something" should do the
autoreconf.

If Buildroot doesn't do it, who will do it? The user manually, when
there are 30+ software components? Doesn't seem really practical and
realistic.

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2013-05-27 19:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-23 11:12 [Buildroot] Design issue with the out-of-tree support Thomas Petazzoni
2013-05-23 12:43 ` Will Wagner
2013-05-23 12:53   ` Thomas Petazzoni
2013-05-23 14:49     ` Markos Chandras
2013-05-23 18:12 ` Yann E. MORIN
2013-05-27 16:50 ` Arnout Vandecappelle
2013-05-27 19:12   ` Thomas Petazzoni
2013-05-27 19:44     ` Arnout Vandecappelle
2013-05-27 19:53       ` Thomas Petazzoni [this message]
2013-05-28 19:26         ` Arnout Vandecappelle

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=20130527215354.133444a6@skate \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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