linux/scripts/kconfig
Daniel Gomez a26fe287ee kconfig: merge_config: use an empty file as initfile
The scripts/kconfig/merge_config.sh script requires an existing
$INITFILE (or the $1 argument) as a base file for merging Kconfig
fragments. However, an empty $INITFILE can serve as an initial starting
point, later referenced by the KCONFIG_ALLCONFIG Makefile variable
if -m is not used. This variable can point to any configuration file
containing preset config symbols (the merged output) as stated in
Documentation/kbuild/kconfig.rst. When -m is used $INITFILE will
contain just the merge output requiring the user to run make (i.e.
KCONFIG_ALLCONFIG=<$INITFILE> make <allnoconfig/alldefconfig> or make
olddefconfig).

Instead of failing when `$INITFILE` is missing, create an empty file and
use it as the starting point for merges.

Signed-off-by: Daniel Gomez <da.gomez@samsung.com>
Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
2025-04-06 06:22:01 +09:00
..
lxdialog
tests
.gitignore
Makefile
conf.c
confdata.c
expr.c
expr.h
gconf-cfg.sh
gconf.c
gconf.glade
images.c
images.h
internal.h
lexer.l
lkc.h
lkc_proto.h
mconf-cfg.sh
mconf.c
menu.c
merge_config.sh kconfig: merge_config: use an empty file as initfile 2025-04-06 06:22:01 +09:00
mnconf-common.c
mnconf-common.h
nconf-cfg.sh
nconf.c
nconf.gui.c
nconf.h
parser.y
preprocess.c
preprocess.h
qconf-cfg.sh
qconf.cc
qconf.h
streamline_config.pl
symbol.c
util.c