From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "José Mendes" <jp.baltazar.mendes@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] Individual package configs
Date: Thu, 25 Jul 2024 18:10:48 +0200 [thread overview]
Message-ID: <20240725181048.11efa805@windsurf> (raw)
In-Reply-To: <CAFAK9+cYzvio3MuLh+WKJ6y1dJi+BMU_ywRoyH9wG8XFPMtD-A@mail.gmail.com>
Hello,
On Thu, 25 Jul 2024 17:26:51 +0200
José Mendes <jp.baltazar.mendes@gmail.com> wrote:
> I've noticed that the configs produced by individual package commands don't
> ever get written to the .config.
>
> Is there a way to produce a defconfig with the individual package changes?
>
> I specifically need:
> - U-Boot
> - swupdate
> - linux
make linux-savedefconfig will take the .config in
output/build/linux-<version>/ and turn it into
output/build/linux-<version>/defconfig
make linux-update-config will take the .config in
output/build/linux-<version>/ and copy it to the location defined by
BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE.
make linux-update-defconfig will take the .config in
output/build/linux-<version>/, turn it into a defconfig and copy this
defconfig to the location defined by
BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE.
These make targets exist for all packages that use kconfig.
See https://buildroot.org/downloads/manual/manual.html#customize-store-package-config
also, as well
as https://bootlin.com/doc/training/buildroot/buildroot-slides.pdf
starting from slide 75.
Hope this helps!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2024-07-25 16:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-25 15:26 [Buildroot] Individual package configs José Mendes
2024-07-25 16:10 ` Thomas Petazzoni via buildroot [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=20240725181048.11efa805@windsurf \
--to=buildroot@buildroot.org \
--cc=jp.baltazar.mendes@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
/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