From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Petazzoni Date: Fri, 8 Mar 2013 13:12:03 +0100 Subject: [Buildroot] providing post-build scripts in buildroot In-Reply-To: <1787200172.233322.1362742213566.JavaMail.root@openwide.fr> References: <20130308115829.700879e1@skate> <1787200172.233322.1362742213566.JavaMail.root@openwide.fr> Message-ID: <20130308131203.2a847c24@skate> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net 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