From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] Custom tarball and .config file
Date: Tue, 10 Dec 2019 14:11:45 +0100 [thread overview]
Message-ID: <20191210141145.5969eb63@windsurf> (raw)
In-Reply-To: <1575964472511-0.post@n4.nabble.com>
On Tue, 10 Dec 2019 01:54:32 -0600 (CST)
rscr <rafacrespiramon@gmail.com> wrote:
> Hello,
>
> I am trying to use my Custom Tarball and I would like to use the
> bcmrpi_defconfig as a base config for creating my custom linux config file.
>
> Here are the paths I am using.
>
> BR2_LINUX_KERNEL_CUSTOM_TARBALL_LOCATION="file://home/tec/rcr/tools/src/linux-rpi-4.19.y.tar.gz"
> BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE="/home/tec/rcr/projects/cp4/rscr_br2_extree/configs/ibLinux_defconfig"
>
> I can build an image with that BR2_LINUX_KERNEL_CUSTOM_TARBALL_LOCATION and
> the bcmrpi_defconfig, but now I would like to use my own .config based on
> bcmrpi
So if I understand, the above configuration is working well for you ?
> 1) Is there any way of using "make linux-menuconfig" pointing to my
> BR2_LINUX_KERNEL_CUSTOM_TARBALL_LOCATION path instead of the /dl/linux
> sources?
Well, if the above configuration with a file:// path is working for
you, why don't you simply use this ?
> 2) Is there any way of doing something like "make bcmrpi_defconfig", "make
> linux-menuconfig"...just as for the buildroot defconfig file?
I'm not sure to follow you here. As long as Buildroot is configured
with the Linux kernel package enabled, you can run "make
linux-menuconfig".
To be honest, I am quite puzzled by your questions, so I believe there
is a misunderstanding somewhere.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-12-10 13:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-10 7:54 [Buildroot] Custom tarball and .config file rscr
2019-12-10 13:11 ` Thomas Petazzoni [this message]
2019-12-10 13:58 ` rscr
2019-12-12 6:59 ` rscr
2019-12-13 12:27 ` rscr
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=20191210141145.5969eb63@windsurf \
--to=thomas.petazzoni@bootlin.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