From: Ulf Samuelsson <ulf.samuelsson@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] Q: Modifying package builds?
Date: Wed, 11 Jun 2008 07:37:08 +0200 [thread overview]
Message-ID: <00c301c8cb8e$aaa42da0$090514ac@atmel.com> (raw)
In-Reply-To: C681C76E0D5F1E4BB01DE79E0A80EEC77C514F@usrdes03.ebgroup.elektrobit.com
> **My primary question(s) for this group is**: How can I change the
> configuration of packages before they are built?
The build of a package <package> is goverened by
<buildroot>/packages/<package>/<package>.mk
Ensure that this file contains the target:
<package>-unpacked: <package>-source
The target should be completed when the package has been decompressed
in "build_arm/<package>" and any patched present in
"<buildroot>/packages/<package>/" has been applied.
Unpack and apply the existing patches with:
$ make <package>-unpacked
$ cd build_arm
$ mv <package> <package>-0rig
$ cd ..
$ make <package>-unpacked
Now you have both
"build_arm/<package>" and "build_arm/<package>-0rig"
Make any modifications to "build_arm/<package>" and create a patch
$ cd build_arm
$ diff -urN <package>-0rig <package> > <package>-###.patch
$ mv <package>-###.patch ../packages/<package>
"###" should ensure that the new patch is applied after all existing patches.
This will handle one package at a time.
It might be a good idea to have a generic target which unpacks and patches
all packages but I am not aware that this exist and can't check right now.
Most of the packages support "make source", but very few support
"make unpacked".
Best Regards
Ulf Samuelsson
prev parent reply other threads:[~2008-06-11 5:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-10 19:35 [Buildroot] Q: Modifying package builds? Michael.Forkey at elektrobit.com
2008-06-11 5:37 ` Ulf Samuelsson [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='00c301c8cb8e$aaa42da0$090514ac@atmel.com' \
--to=ulf.samuelsson@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