* [Buildroot] Build Output
@ 2014-06-05 19:27 Dan Pattison
2014-06-05 20:21 ` Peter Korsgaard
2014-06-05 20:39 ` Thomas Petazzoni
0 siblings, 2 replies; 5+ messages in thread
From: Dan Pattison @ 2014-06-05 19:27 UTC (permalink / raw)
To: buildroot
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?
Thank you,
--
Dan Pattison
Ethertek Circuits
^ permalink raw reply [flat|nested] 5+ messages in thread
* [Buildroot] Build Output
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
1 sibling, 1 reply; 5+ messages in thread
From: Peter Korsgaard @ 2014-06-05 20:21 UTC (permalink / raw)
To: buildroot
>>>>> "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
--
Bye, Peter Korsgaard
^ permalink raw reply [flat|nested] 5+ messages in thread* [Buildroot] Build Output
2014-06-05 20:21 ` Peter Korsgaard
@ 2014-06-05 21:00 ` Dan Pattison
0 siblings, 0 replies; 5+ messages in thread
From: Dan Pattison @ 2014-06-05 21:00 UTC (permalink / raw)
To: buildroot
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
^ permalink raw reply [flat|nested] 5+ messages in thread
* [Buildroot] Build Output
2014-06-05 19:27 [Buildroot] Build Output Dan Pattison
2014-06-05 20:21 ` Peter Korsgaard
@ 2014-06-05 20:39 ` Thomas Petazzoni
2014-06-05 21:18 ` Dan Pattison
1 sibling, 1 reply; 5+ messages in thread
From: Thomas Petazzoni @ 2014-06-05 20:39 UTC (permalink / raw)
To: buildroot
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
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
^ permalink raw reply [flat|nested] 5+ messages in thread
* [Buildroot] Build Output
2014-06-05 20:39 ` Thomas Petazzoni
@ 2014-06-05 21:18 ` Dan Pattison
0 siblings, 0 replies; 5+ messages in thread
From: Dan Pattison @ 2014-06-05 21:18 UTC (permalink / raw)
To: buildroot
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
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2014-06-05 21:18 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox