From: Ulf Samuelsson <ulf@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] Best way to add custom step
Date: Mon, 11 Feb 2008 16:26:29 +0100 [thread overview]
Message-ID: <000201c86d49$57af3700$2301a8c0@atmel.com> (raw)
In-Reply-To: 47B0661A.6070605@carallon.com
----- Original Message -----
From: "Will Wagner" <will_wagner@carallon.com>
To: <buildroot@uclibc.org>
Sent: Monday, February 11, 2008 4:13 PM
Subject: [Buildroot] Best way to add custom step
> Hi All,
>
> I need to add a custom step to my build process after the linux image is
> built into the binaries directory. I was wondering about what was the
> best way to go about this.
>
> I could add my changes to the top level makefile or to the
> target\linux\Makefile.in file. Is one way better than the other? Is
> there a better way of doing this?
>
> Thanks,
>
If it is board specific, then it makes more sense to put it
in target/device and let the target depend on the linux binary.
What is the custom step?
Best Regards
Ulf Samuelsson
next prev parent reply other threads:[~2008-02-11 15:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-11 15:13 [Buildroot] Best way to add custom step Will Wagner
2008-02-11 15:26 ` Ulf Samuelsson [this message]
2008-02-12 9:17 ` Will Wagner
2008-02-12 9:24 ` 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='000201c86d49$57af3700$2301a8c0@atmel.com' \
--to=ulf@atmel.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