From: "Jérôme Pouiller" <jezz@sysmic.org>
To: buildroot@busybox.net
Subject: [Buildroot] [Feature Request] script to run after build completion
Date: Mon, 21 Jan 2013 06:27:35 +0100 [thread overview]
Message-ID: <4145444.6F8bMSMLXM@sagittae> (raw)
In-Reply-To: <50FA7B6D.9040504@mind.be>
Hello Arnout,
On Saturday 19 January 2013 11:54:37 Arnout Vandecappelle wrote:
> On 16/01/13 18:07, Stephan Hoffmann wrote:
> > Hello all,
> >
> > I am picking up a feature request from 2011, because I am currently in a
> > situation where I could use the proposed feature.
> >
> > Alper Y?ld?r?m wrote on 8 Jun 2011 22:40
> >
> >> Hello,
> >>
> >> A feature i want to see in buildroot is to have a post build script to
> >> run after image creation process, in other words just before "make"
> >> returns to console. This way i can put my post build commands inside
> >> this script. It will definitely ease my buildroot usage.
[...]
> >
> > I would rather think of a hook that only gets called after successful
> > image completion.
>
> I think this very much falls into the category of featuritis.
>
> In many situations, you'll want a script around 'make' to automate
> things beyond what buildroot does. As long as this script only does
> things _before_ and _after_ the 'make' invocation, there is no need for a
> change in buildroot infrastructure. And these top-level scripts are so
> different from project to project that it doesn't make sense to include
> them in buildroot either.
Stephan does not suggest to include these scripts in Buildroot, but just add
needed framework.
> For example, here's a script that will automatically take a defconfig
> and copy the images to the target:
>
> #! /bin/sh
> # Wrapper around make
>
> # We allow running from a foreign directory
> topdir="$(dirname $0)"
> [ "$topdir" = . ] && output="output/" || outdir="O=$PWD"
> MAKE="make -C $topdir $outdir"
>
> if [ ! -e .config ]; then
> $MAKE project_defconfig
> fi
>
> echo $MAKE "$@"
> $MAKE "$@" || exit $?
>
> imgfiles="${output}images/bzImage ${output}images/rootfs.cpio.bz2"
>
> # Terminate if image files were not generated
> for f in $imgfiles; do
> [ -r "$f" ] || exit 1
> done
>
> if [ "$TARGET_IP" ]; then
> scp $imgfiles root@$TARGET_IP:/mnt/boot
> ssh root@$TARGET_IP /sbin/reboot
> fi
>
>
> There is really no need to change buildroot to support this kind of thing.
This script is not trivial in comparison to post-build.sh. Buildroot should
deliver a template of it...
In add, user can continue to run make without running this script (especially
since this script does not appear in output/ directory).
IMHO, external script is not right answer and feature asked by Stephan make
sense.
--
J?r?me Pouiller
next prev parent reply other threads:[~2013-01-21 5:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-16 17:07 [Buildroot] [Feature Request] script to run after build completion Stephan Hoffmann
2013-01-19 10:54 ` Arnout Vandecappelle
2013-01-21 5:27 ` Jérôme Pouiller [this message]
2013-01-24 6:26 ` Arnout Vandecappelle
-- strict thread matches above, loose matches on Subject: below --
2011-06-08 20:40 Alper Yıldırım
2011-06-08 22:30 ` Steve Calfee
2011-06-09 11:23 ` Bjørn Forsman
2011-06-09 15:55 ` Steve Calfee
2011-06-09 11:21 ` Bjørn Forsman
2011-06-09 19:35 ` Alper Yıldırım
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=4145444.6F8bMSMLXM@sagittae \
--to=jezz@sysmic.org \
--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.