From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [Feature Request] script to run after build completion
Date: Thu, 24 Jan 2013 07:26:38 +0100 [thread overview]
Message-ID: <5100D41E.4030105@mind.be> (raw)
In-Reply-To: <4145444.6F8bMSMLXM@sagittae>
On 01/21/13 06:27, J?r?me Pouiller wrote:
> Hello Arnout,
>
> On Saturday 19 January 2013 11:54:37 Arnout Vandecappelle wrote:
[snip]
>> 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...
Eh? First of all, the proposed change would not be enough to support a
script like the above, because the first part (automatically setting O=
and automatically running a defconfig) is missing. So the only thing that
could be done by the post-build script is everything starting from the
line "imgfiles=..." That leaves just two lines of script that become
redundant with the post-build infrastructure:
echo $MAKE "$@"
$MAKE "$@" || exit $?
> In add, user can continue to run make without running this script (especially
> since this script does not appear in output/ directory).
If you tell the user to use that script to do the build, he won't even
know about 'make'.
> IMHO, external script is not right answer and feature asked by Stephan make
> sense.
It does make sense. I just think that other, much more useful things
have been rejected in the past (e.g. the rsync filesystem, the split
Config.in that allows extra packages to be added)
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2013-01-24 6:26 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
2013-01-24 6:26 ` Arnout Vandecappelle [this message]
-- 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=5100D41E.4030105@mind.be \
--to=arnout@mind.be \
--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.