From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Understanding More about applying patches
Date: Sun, 29 Jul 2012 17:10:08 +0200 [thread overview]
Message-ID: <50155250.6080002@mind.be> (raw)
In-Reply-To: <CALo-6+icxYrcFpMD=GtSjfhcMzOAhQ0quKxhgHxf006quMmo5g@mail.gmail.com>
On 07/28/12 18:59, Charles Krinke wrote:
> Assuming I have the last part correct, the next step is to add a patch
> after the configure step but before the build step.
The patch step is the step after the extract step and before the configure
step. It's not a good idea to add patches after the configure step: if it
doesn't depend on the configuration, then there's no point doing it after
the configure step, but if it does depend on the configuration, than there's
a big risk that the patch won't work.
It may be possible/necessary to update the configuration after the configure
step, e.g. updating the config.h. Again, this should be avoided because it's
not very robust, but if there is no other way, you can do it in the
POST_CONFIGURE_HOOKS with a $(SED) statement.
Fortunately, your other e-mails indicate that this won't be necessary.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286540
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
prev parent reply other threads:[~2012-07-29 15:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-28 16:07 [Buildroot] Understanding More about applying patches Charles Krinke
2012-07-28 16:55 ` Charles Krinke
2012-07-28 16:59 ` Charles Krinke
2012-07-28 17:31 ` Samuel Martin
2012-07-28 18:27 ` Charles Krinke
2012-07-29 15:10 ` Arnout Vandecappelle [this message]
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=50155250.6080002@mind.be \
--to=arnout@mind.be \
--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