From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] providing post-build scripts in buildroot
Date: Fri, 8 Mar 2013 13:12:03 +0100 [thread overview]
Message-ID: <20130308131203.2a847c24@skate> (raw)
In-Reply-To: <1787200172.233322.1362742213566.JavaMail.root@openwide.fr>
Dear Jeremy Rosen,
On Fri, 8 Mar 2013 12:30:13 +0100 (CET), Jeremy Rosen wrote:
> i'm not sure what you mean here... do you want the script mentionned
> in the documentation ? in that case yes, that makes sense
>
> do you want the script "directly included as text" in the doc ?
> I am less convinced, unless you want to use them as examples rather
> than tools provided by the poject....
Yes, the scripts included directly into the documentation. At the last
Buildroot meeting, we've discussed the idea of extending the
documentation with more "Use cases descriptions", i.e how to use
Buildroot in practice for a project. I think examples of what can be
done in post-build scripts who fit quite well in this.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-03-08 12:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1890922777.231675.1362739947331.JavaMail.root@openwide.fr>
2013-03-08 10:55 ` [Buildroot] providing post-build scripts in buildroot Jeremy Rosen
2013-03-08 10:58 ` Thomas Petazzoni
2013-03-08 11:30 ` Jeremy Rosen
2013-03-08 12:12 ` Thomas Petazzoni [this message]
2013-03-08 13:21 ` Jeremy Rosen
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=20130308131203.2a847c24@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