All of 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:12:00 +0200	[thread overview]
Message-ID: <20130527211200.735491c7@skate> (raw)
In-Reply-To: <51A38EEE.7000406@mind.be>

Dear Arnout Vandecappelle,

On Mon, 27 May 2013 18:50:54 +0200, Arnout Vandecappelle wrote:

>   I haven't read the thread in detail or thought about it very carefully, 
> but some time ago I already thought that this would be better.
> 
>   It is not necessarily limited to autoreconf. For example, the way that 
> xenomai patches the linux sources fits in this as well (xenomai could add 
> to LINUX_POST_AUTORECONF_HOOKS).
> 
>   So I would propose to add another step to the generic infrastructure. I 
> would call it the PREPARE step, and make it a full step with CMDS and HOOKS.

Indeed. For now, it's only has a CMDS and no HOOKS, but it could be
added later on.

>   The question is whether the OVERRIDE_SRCDIR infrastructure should apply 
> this step or not. Conceptually, it shouldn't, but that means that users 
> of OVERRIDE_SRCDIR for packages that need an autoreconf would need to do 
> the autoreconf manually. Which is probably for the best anyway, but which 
> is a change compared to current behaviour.

For now, I consider doing the prepare step even on OVERRIDE_SRCDIR
package, even if that means that we are modifying the source directory.

>   BTW the libtool fixup should probably be done in this prepare step as 
> well. But again, I haven't thought this through in detail.

This is already done:

 http://git.free-electrons.com/users/thomas-petazzoni/buildroot/commit/?h=out-of-tree-v3&id=5cf6166d713a43cdf83cdf794502eb77be36d43f

Thanks for the feedback!

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:12 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 [this message]
2013-05-27 19:44     ` Arnout Vandecappelle
2013-05-27 19:53       ` Thomas Petazzoni
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=20130527211200.735491c7@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 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.