From: "Jérôme Pouiller" <jezz@sysmic.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] pkg-infra: log current message
Date: Mon, 07 Oct 2013 12:09:50 +0200 [thread overview]
Message-ID: <30033387.d25L1SpIx8@sagittae> (raw)
In-Reply-To: <1381058388-24055-1-git-send-email-yann.morin.1998@free.fr>
Hello Yann,
On Sunday 06 October 2013 13:19:48 Yann E. MORIN wrote:
> From: "Yann E. MORIN" <yann.morin.1998@free.fr>
>
> In order to help the auto-builders (our own, or in-house ones),
> just log the current message in a file that contains:
> Package: $($(PKG)_NAME)
> Version: $($(PKG)_VERSION)
> Action : Last '>>>' message displayed
I have also in my local git some branches modified in a similar fashion.
Some weeks ago, Francois Perrad also suggested a patch with a similar
modification (http://patchwork.ozlabs.org/patch/265214). Thomas also
wrote a patch to get build time statistics
(http://lists.busybox.net/pipermail/buildroot/2011-October/046513.html).
IMHO, these patchs are too much specific and should not be mainlined.
However, Buildroot may provide a generic framework to make this kind
instrumentation easier.
For example, we may add a (another) new hooks at beginning and end of
each action of pkg-generic.mk. It will give opportunity to user to
implement its instrumentation in local.mk.
Another need would be to call external scripts from these hooks. In this
case, it may be difficult to pass all needed information to an external
script (I mean all $($(PKG)_*) variables). Buildroot may provide a
generic way to to it (passing $($(PKG)_*) in environment for example).
--
J?r?me Pouiller, Sysmic
Embedded Linux specialist
http://www.sysmic.fr
next prev parent reply other threads:[~2013-10-07 10:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-06 11:19 [Buildroot] [PATCH] pkg-infra: log current message Yann E. MORIN
2013-10-06 14:31 ` Thomas Petazzoni
2013-10-07 10:09 ` Jérôme Pouiller [this message]
2013-10-07 12:07 ` Thomas Petazzoni
2013-10-07 16:48 ` Yann E. MORIN
2013-10-07 16:59 ` Yann E. MORIN
2013-10-07 17:19 ` Thomas Petazzoni
2013-10-08 16:47 ` Arnout Vandecappelle
2013-10-07 20:53 ` Jérôme Pouiller
2013-10-07 19:46 ` Jérôme Pouiller
2013-10-08 16:53 ` Arnout Vandecappelle
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=30033387.d25L1SpIx8@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox