All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC] post-build scripts: limitations, and proposal
Date: Fri, 21 Jun 2013 08:59:19 +0200	[thread overview]
Message-ID: <20130621085919.4f2c6579@skate> (raw)
In-Reply-To: <CAAXf6LVO6Rz3RXLW++kOOfaHGRvR_4AB8Mi=VS2S-pKhJSm5Lw@mail.gmail.com>

Yann, Thomas,

On Fri, 21 Jun 2013 08:17:05 +0200, Thomas De Schampheleire wrote:

> Instead of passing multiple scripts, you could just pass one wrapper
> post build script, without options. This wrapper would be different in
> your different configurations, and would call all relevant scripts in
> turn. Adding a script for a certain configuration now no longer means
> updating the buildroot configuration, but instead updating the wrapper
> script.

This is absolutely what should be done in Yann's case. There's no need
to make the post-build script mechanism in Buildroot more complicated,
just handle the complexity in our own scripts, it is much more
flexible.

Best regards,

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-06-21  6:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-20 21:36 [Buildroot] [RFC] post-build scripts: limitations, and proposal Yann E. MORIN
2013-06-21  6:17 ` Thomas De Schampheleire
2013-06-21  6:59   ` Thomas Petazzoni [this message]
2013-06-23 17:06   ` Arnout Vandecappelle
2013-06-23 17:45     ` Thomas De Schampheleire

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=20130621085919.4f2c6579@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.