summaryrefslogtreecommitdiff
path: root/scripts
diff options
context:
space:
mode:
authorSergey Ryazanov <ryazanov.s.a@gmail.com>2017-05-07 20:19:13 +0300
committerJo-Philipp Wich <jo@mein.io>2017-12-13 15:27:36 +0100
commitbb9eb2c96e47b2ca6c3596cf9af1a497d3f55f23 (patch)
treeea85e78e3b41294b87cc00fd0bc92a807a0248d9 /scripts
parent4607007a86cc240b091b9176b3d7aa82a6ca0c71 (diff)
downloadmtk-20170518-bb9eb2c96e47b2ca6c3596cf9af1a497d3f55f23.zip
mtk-20170518-bb9eb2c96e47b2ca6c3596cf9af1a497d3f55f23.tar.gz
mtk-20170518-bb9eb2c96e47b2ca6c3596cf9af1a497d3f55f23.tar.bz2
build: new fixes for symlinked .config handling
When running "make {config|defconfig|oldconfig}" with symlinked .config (e.g. to env/.config) it renames symlink to .config.old, creates new .config file, and writes the updated configuration into it. This breaks the desired workflow when changes in the configuration can be checked using "scripts/env diff" and commited using "scripts/env save". Since the env/.config file is not updated. The things become even worse when working with feeds, since feeds script quite often silently invokes "make {oldconfig|defconfig}" and breaks the symlink. Fix this issue by exporting KCONFIG_OVERWRITECONFIG=1, which forces mconf to overwrite the .config content, instead of renaming it and creating a new file. This variable is set only if .config is a symlink, otherwise the variable is not exported and the old behaviour is preserved. This change uses the same behaviour as "make menucofig", which has already been fixed in commit 5bf98b1acc3b6b178f8954c5075a58e1e6a99d6a. Also make a tiny cosmetic update to the "make menuconfig" target code layout to make it look like other config handling targets. Signed-off-by: Sergey Ryazanov <ryazanov.s.a@gmail.com> (cherry picked from commit e06d8f0f6f041c8ac1acba810eea96c32dc983e4)
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions