From: Aleksandar Simeonov <aleksandar@barix.com>
To: buildroot@busybox.net
Subject: [Buildroot] Using packages overrides
Date: Wed, 6 Apr 2016 10:44:04 +0200 [thread overview]
Message-ID: <5704CC54.5080007@barix.com> (raw)
Hi All,
Could someone help me to understand how to use properly the package
override in BR? I'm trying to override a BR package by defining the
BR2_PACKAGE_OVERRIDE_FILE="$(BR2_EXTERNAL)/local.mk"
and putting in local.mk the right
PKGFOO_OVERRIDE_SRCDIR = $(BR2_EXTERNAL)/package/override/sysvinit
The problem is that whatever package I try to override, the build
complains that it has been redefined-once in the original BR2 package
folder, and second time in the override folder. Am I misinterpreting the
BR user manual chapter 8.12.6 ? Can we use Config.in and pkgfoo.mk files
in the override folder, or we have to share those of the original
package? That wouldn't make anysense, because the user may also need to
customise the .mk file. What I'm missing/doing wrong ?
Thanks in advance,
Alex Simeonov
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20160406/8cc1a7ad/attachment.html>
next reply other threads:[~2016-04-06 8:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-06 8:44 Aleksandar Simeonov [this message]
2016-04-06 22:03 ` [Buildroot] Using packages overrides Arnout Vandecappelle
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=5704CC54.5080007@barix.com \
--to=aleksandar@barix.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