From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Overriding Buildroot packages
Date: Tue, 24 Nov 2015 16:41:07 +0100 [thread overview]
Message-ID: <20151124164107.3570084a@free-electrons.com> (raw)
In-Reply-To: <CAPER3A0P1Qyd_=ktyHt=udawndUfHue8SE_zDQxMHjz+r+pPtg@mail.gmail.com>
Hello,
On Tue, 24 Nov 2015 14:43:21 +0100, Hajime Branko Yamasaki Vukelic
wrote:
> I've set up my build such that all modification are done in
> BR2_EXTERNAL directory, and I have a submodule that points to
> unmodified upstream buildroot sources.
>
> I've been trying to find a way to override a package that is normally
> provided by Buildroot. By 'override' I mean completely swap it with
> another package definition, possibly with different patches, etc.
>
> Right now I've created a package that has a completely different name
> (e.g., for package 'foo', I have 'foo-custom'), but this breaks
> dependencies for packages that would otherwise depend on the original.
>
> I've dug into pkg-generic.mk and I see that it may not really be
> possible, but I wanted to confirm. Can someone tell me if I'm missing
> something or this really isn't possible without modifying the
> buildroot version of the package?
This is really not possible with the current Buildroot, and would be
quite complicated to implement in a generic way.
If all you need is to apply a set of additional patches, then you can
do so without modifying the Buildroot package itself by using the
BR2_GLOBAL_PATCH_DIR mechanism.
However, if you indeed need a completely different version of the
package, we don't have a really good way of handling that.
Are you able to give more details about which specific package you need
to override and why? It would be useful for us to understand such use
cases, and see if there is a different solution/option, or if the use
case is really too specific.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-11-24 15:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-24 13:43 [Buildroot] Overriding Buildroot packages Hajime Branko Yamasaki Vukelic
2015-11-24 15:41 ` Thomas Petazzoni [this message]
2015-11-24 18:27 ` Hajime Branko Yamasaki Vukelic
2015-11-24 22:30 ` Arnout Vandecappelle
2015-11-25 9:48 ` Hajime Branko Yamasaki Vukelic
2015-11-29 23:09 ` Arnout Vandecappelle
2015-12-05 17:29 ` Yann E. MORIN
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=20151124164107.3570084a@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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