All of 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:00:06 -0700	[thread overview]
Message-ID: <5390DA56.30508@ethertek.ca> (raw)
In-Reply-To: <87ppinm7jy.fsf@dell.be.48ers.dk>

On 6/5/2014 1:21 PM, Peter Korsgaard wrote:
>>>>>> "Dan" == Dan Pattison <dan.pattison@ethertek.ca> writes:
>   > Hello,
>   > 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 show the various stages of package installation like buildroot
>   > does with text that has a highlighted back ground. This helps in
>   > debugging to see where certain programs start their build process.
>
>   > For instance, when the post-image script fires it outputs the line
>   > below with a highlighted back ground that is easy to spot.
>   >>>> Executing post-image script board/ethertek/ws/post-build.sh
>
>   > I tried the line below in my own post-build.sh, but get a command not
>   > found error.
>   > $(call MESSAGE,"Building Package FOO");
>
>   > Is it possible to make the call command above work in my own shell
>   > scripts that reside in the board folder? If yes, what do I include to
>   > make that work?
>
> Not really. MESSAGE is a make macro, so you cannot use it from a shell
> script.
>
> But you can take a look at the implementation in package/pkg-utils.mk
> and create a similar shell function, something like:
>
> MESSAGE() {
>      tput smso
>      echo ">>> $*"
>      tput rmso
> }
>
> MESSAGE hello world
>
Hello Peter,

Thanks for the reply. I will try that.

Dan Pattison
Ethertek Circuits

  reply	other threads:[~2014-06-05 21:00 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 [this message]
2014-06-05 20:39 ` Thomas Petazzoni
2014-06-05 21:18   ` Dan Pattison

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=5390DA56.30508@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 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.