From: Stephan Hoffmann <sho@relinux.de>
To: buildroot@busybox.net
Subject: [Buildroot] [Feature Request] script to run after build completion
Date: Wed, 16 Jan 2013 18:07:21 +0100 [thread overview]
Message-ID: <50F6DE49.4000600@relinux.de> (raw)
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.
>
> Some examples to put in this script are:
>
> - Printing some king of a "build completed" message,
> - Printing build time,
> - Nfs directory creation from rootfs.tar file,
> - Copying necessary images to some other locations,
- any other kind of project/board specific post processing
> - Playing some sound when build is completed.
>
> Also, it will be nice to pass a build failed/completed parameter to
> this script, so different actions could be taken, (i.e. different
> sounds could be played)
I would rather think of a hook that only gets called after successful
image completion.
>
> What do you think about this Thomas?
>
> Cheers
> Alper
I tried to implement such a hook, but did not find the right place.
Could anybody give me a hint?
Kind regards
Stephan
--
reLinux - Stephan Hoffmann
Am Schmidtgrund 124 50765 K?ln
Tel. +49.221.95595-19 Fax: -64
www.reLinux.de sho at reLinux.de
next reply other threads:[~2013-01-16 17:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-16 17:07 Stephan Hoffmann [this message]
2013-01-19 10:54 ` [Buildroot] [Feature Request] script to run after build completion Arnout Vandecappelle
2013-01-21 5:27 ` Jérôme Pouiller
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=50F6DE49.4000600@relinux.de \
--to=sho@relinux.de \
--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