[Buildroot] [.config file] Generating buildroot-like .config file from "linux-like" .config file

[vr roriz]

Thanks for answering Mr. Neuschäfer,

I've got your point. Then, I would add to my original issue: Would you have
a suggestion about the best approach to mirror an existent .config file
(from Linux source tree), without having to keep scanning strings in "make
linux-menuconfig" and editing it manually? How do buildroot users usually
do that? I know I can redefine the defconfig file for the target board
after creating a .config file, but I am referring to the first-time process.

BR,
Vitor Roriz

2017-07-25 16:13 GMT+02:00 Jonathan Neuschäfer <j.neuschaefer at gmx.net>:

> On Tue, Jul 25, 2017 at 11:28:08AM +0200, vr roriz wrote:
> > Dear all,
> >
> > I'd like to know what is the best approach to generate a buildroot-like
> > .config file (Using BR2) from an existent linux-like .config file. By
> > linux-like I mean, the .config files with the native syntax, generated by
> > make menuconfig in the Linux Source Tree, like the ones that are
> generated
> > in the output dir of buildroot after building.
>
> Buildroot .config files and Linux .config files are not compatible
> because they refer to completely different settings, but if you want to
> convert the *syntax*, a simple sed command should do (in both directions):
>
>   $ sed -e 's/CONFIG_/BR2_/' .config
>   #
>   # Automatically generated file; DO NOT EDIT.
>   # Linux/powerpc 4.11.8 Kernel Configuration
>   #
>   # BR2_PPC64 is not set
>
>   #
>   # Processor support
>   #
>   BR2_PPC_BOOK3S_32=y
>   # BR2_PPC_85xx is not set
>   # BR2_PPC_8xx is not set
>   # BR2_40x is not set
>   # BR2_44x is not set
>   # BR2_E200 is not set
>   ...
>
>
> I hope that helps,
> Jonathan Neuschäfer
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20170725/bec8ea4e/attachment-0002.html>