[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20110419192426.GA1096@debian.debian>
Date: Tue, 19 Apr 2011 21:24:27 +0200
From: Jonathan Neuschäfer <j.neuschaefer@....net>
To: Francis Moreau <francis.moro@...il.com>
Cc: Américo Wang <xiyou.wangcong@...il.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Kbuild: how to cleanly retrieve information compilation about
the last build
On Sun, Apr 17, 2011 at 12:27:29PM +0200, Francis Moreau wrote:
> On Sun, Apr 17, 2011 at 6:57 AM, Américo Wang <xiyou.wangcong@...il.com> wrote:
> > On Sat, Apr 16, 2011 at 10:00 PM, Francis Moreau <francis.moro@...il.com> wrote:
> >> On Sat, Apr 16, 2011 at 10:26 AM, Américo Wang <xiyou.wangcong@...il.com> wrote:
> >>> So why not just put that line into your script?
> >>>
> >>
> >> Because this line was an _example_ of how the makefile could had been invoked.
> >>
> >> But the script has currently no idea how the previous invocation was
> >> made, hence my question.
> >
> > You use a bad design, why not just pass these parameters to your script?
> > Something like,
> >
> > $ ./your_script CC=my-gcc CFLAGS="-g -fwhatever"
> >
> > or whatever you want.
> >
>
> Yes, I think I'll continue to do that.
>
> Thanks
You may also try this little script (call it instead of plain "make"):
#!/bin/sh
MAKE=make
CMDLINE=make.cmdline
if [ "x$@" != "x" ]; then
echo -n "$@" > $CMDLINE
$MAKE "$@"
else
if [ -f $CMDLINE ]; then
$MAKE $(cat $CMDLINE)
else
$MAKE
fi
fi
thanks,
Jonathan Neuschäfer
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists