Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Pattison <dan.pattison@ethertek.ca>
To: buildroot@busybox.net
Subject: [Buildroot] Build Output
Date: Thu, 05 Jun 2014 14:18:22 -0700	[thread overview]
Message-ID: <5390DE9E.1010003@ethertek.ca> (raw)
In-Reply-To: <20140605223928.3794a407@free-electrons.com>

On 6/5/2014 1:39 PM, Thomas Petazzoni wrote:
> Dear Dan Pattison,
>
> On Thu, 05 Jun 2014 12:27:24 -0700, Dan Pattison wrote:
>
>> I am using the post image script feature to compile and install various
>> custom packages. In my shell and make files I want to make the ouput
> Why don't you create additional Buildroot packages instead? That would
> be a lot more logical that doing this in a post-image script.
>
> Thomas

Hello Thomas,

Thank you for the reply. I found the need to run some custom scripts 
just before the images are created to do various things like add a 
firmware build number file, tar up the /etc folder for use in a factory 
reset situation, and a few other product specific jobs. As it is doing 
each step, it's nice to get the highlighted output for debugging. For 
whatever reason, I started building some custom packages from the 
post-image script also. Peter showed me a way to do the highlight from 
my shell script by making a custom MESSAGE() function.

MESSAGE() {
     tput smso
     echo ">>> $*"
     tput rmso
}

MESSAGE hello world

Thanks,
Dan Pattison
EtherTek Circuits

      reply	other threads:[~2014-06-05 21:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-05 19:27 [Buildroot] Build Output Dan Pattison
2014-06-05 20:21 ` Peter Korsgaard
2014-06-05 21:00   ` Dan Pattison
2014-06-05 20:39 ` Thomas Petazzoni
2014-06-05 21:18   ` Dan Pattison [this message]

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=5390DE9E.1010003@ethertek.ca \
    --to=dan.pattison@ethertek.ca \
    --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