Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Design issue with the out-of-tree support
Date: Tue, 28 May 2013 21:26:16 +0200	[thread overview]
Message-ID: <51A504D8.3040607@mind.be> (raw)
In-Reply-To: <20130527215354.133444a6@skate>

On 27/05/13 21:53, Thomas Petazzoni wrote:
> 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.

  Well, actually the autotools-generated makefile will itself detect that 
configure.ac has changed and regenerate it in the source directory, so a 
non-writeable source directory will be broken anyway.

  Okay then. If anyone has an issue with buildroot messing with their 
OVERRIDE_SRCDIR, they can still add a OVERRIDE_SKIP_PREPARE variable that 
disables the prepare step.

  Regards,
  Arnout


-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

      reply	other threads:[~2013-05-28 19:26 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
2013-05-28 19:26         ` Arnout Vandecappelle [this message]

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=51A504D8.3040607@mind.be \
    --to=arnout@mind.be \
    --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