>
> (apply some symbols)
> make defconfig
>
> [...]
>
> (apply some symbols)
> make defconfig
>
> This is called up to 30 times till our '.config' is ready.
>
> Question: is it *safe* to call 'defconfig' only at there very
> end?
That's all I've ever done. I have a little snippet of maybe 20-
* Bastian Bittorf [09.02.2017 17:45]:
> is 'make menuconfig' also using 'package-metadata.pl'?
>
> I ask, because start 'menuconfig' and selecting/unselecting
> symbols with the GUI is very fast, but the same operation - is'nt it?
i will answer the question myself: it is not.
defconfig must be c
* Jo-Philipp Wich [07.02.2017 15:20]:
> Check "git log scripts/config/" and compare the complexity & size of
> "./scripts/metadata.pl config tmp/.packageinfo" in OpenWrt with
> "./scripts/package-metadata.pl config tmp/.packageinfo" on LEDE.
is 'make menuconfig' also using 'package-metadata.pl'?
* Jo-Philipp Wich [07.02.2017 15:20]:
> Check "git log scripts/config/" and compare the complexity & size of
> "./scripts/metadata.pl config tmp/.packageinfo" in OpenWrt with
> "./scripts/package-metadata.pl config tmp/.packageinfo" on LEDE.
>
> Also compare the runtimes of "make prepare-tmpinfo"
Hi,
> I'am not sure, what is internally done and how,
> can somebody point me to the program.c so maybe i
> get an idea whats "wrong".
Check "git log scripts/config/" and compare the complexity & size of
"./scripts/metadata.pl config tmp/.packageinfo" in OpenWrt with
"./scripts/package-metadata.p
in our build-process we make intensive use of
'make defconfig' and registrated a massive speed-loss
in building comparing with OpenWrt r49276 on the
same machine with nearly the same .config:
r49276: ~1.2sec
LEDE: ~10 sec
everything is in a tmpfs, it's a Xeon 5680@3.33GHz
I'am not sure, what is
