From: Steven J. Hill <sjhill@realitydiluted.com>
To: buildroot@busybox.net
Subject: [Buildroot] "toolchain/patch-kernel.sh" => $(APPLY)
Date: Thu, 12 Jul 2007 08:51:19 -0500 [thread overview]
Message-ID: <20070712135118.GA10707@real.realitydiluted.com> (raw)
In-Reply-To: <1184241425.5175.9.camel@elrond.sweden.atmel.com>
> Today most packages uses the patch-kernel.sh script in toolchain.
> Should this really be hardwired.
> Is it OK to create a symbolic variable.
>
> APPLY:=toolchain/patch-kernel.sh
>
Why? Can you explain what is lacking with this script that you are
suggesting adding another variable to track through the build system?
> Also, I would like to see a "script" directory.
> "patch-kernel.sh" is then moved here and
> "depmod.pl" maybe belongs as well in this instead of in
> target/device/x86.
>
I suppose a 'toolchain/scripts' directory would be okay. I do
question the need for 'depmod.pl' at all. Doesn't the target
'cross-depmod26' create the depmod that does the same thing?
-Steve
next prev parent reply other threads:[~2007-07-12 13:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-12 11:57 [Buildroot] "toolchain/patch-kernel.sh" => $(APPLY) Ulf Samuelsson
2007-07-12 13:51 ` Steven J. Hill [this message]
2007-07-12 15:35 ` Ulf Samuelsson
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=20070712135118.GA10707@real.realitydiluted.com \
--to=sjhill@realitydiluted.com \
--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