From: Michael Olbrich <m.olbrich@pengutronix.de>
To: Christian Melki <christian.melki@t2data.com>
Cc: Andreas Helmcke <ahelmcke@ela-soft.com>, ptxdist@pengutronix.de
Subject: Re: [ptxdist] How to get ptxdist recognize changes in busybox Config.src?
Date: Fri, 6 May 2022 08:07:52 +0200 [thread overview]
Message-ID: <YnS7OJ1rObPXSbN/@pengutronix.de> (raw)
In-Reply-To: <32151948-9a2d-fb1a-21d2-809422b5cd4b@t2data.com>
Hi,
On Tue, May 03, 2022 at 12:27:17PM +0200, Christian Melki wrote:
> On 5/3/22 11:24 AM, Andreas Helmcke wrote:
> > I am trying to make / change a patch for busybox. The patch contains
> > some changes to the busybox configuration in loginutils/Config.src.
> > Calling make menuconfig in
> > ptxdist/platform-.../build-target/busybox-1.35.0 works and shows the new
> > menu entries.
> > But ptxdist menuconfig does not offer this entries in the busybox menu
> > at -> PTXdist Base Configuration -> Shell & Console Tools.
> >
> > Any suggestion how to make ptxdist recognize these changes?
> Ptxdist keeps a set of the busybox configuration.
> This is used to render the changes locally.
> So any changes must also be reflected in the local set.
> Take a look under config/busybox.
> These are generated and refreshed in ptxdist when busybox is updated.
What you need to do is this:
- Add the patches and extract busybox
- run "ptxdist make busybox_import PTXDIST_IMPORTDIR=`pwd`"
This will create the busybox kconfig files in config/busybox/ in your BSP.
They will be used instead of the files from PTXdist.
Michael
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
prev parent reply other threads:[~2022-05-06 6:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-03 9:24 Andreas Helmcke
2022-05-03 10:27 ` Christian Melki
2022-05-06 6:07 ` Michael Olbrich [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=YnS7OJ1rObPXSbN/@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ahelmcke@ela-soft.com \
--cc=christian.melki@t2data.com \
--cc=ptxdist@pengutronix.de \
/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