build: force a valid config at each step

If you re-build after stuff has been added to Kconfig, the .config you already have in place is wrong. This means the dot-config at runtime will have missing items. We thus force a silent "make oldconfig" at each build step, to ensure user preverences are saved, but new options get the default value. Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

build: force a valid config at each step
If you re-build after stuff has been added to Kconfig, the .config you already have in place is wrong. This means the dot-config at runtime will have missing items. We thus force a silent "make oldconfig" at each build step, to ensure user preverences are saved, but new options get the default value. Signed-off-by: Alessandro Rubini <rubini@gnudd.com>
1a2fb30f · Alessandro Rubini · 0add2783 · 1a2fb30f
Commit 1a2fb30f authored Jul 20, 2015 by Alessandro Rubini
Hide whitespace changes
Inline Side-by-side

Showing with 2 additions and 1 deletion

wrs_functions build/scripts/wrs_functions +2 -1

No files found.
--- a/build/scripts/wrs_functions
+++ b/build/scripts/wrs_functions
@@ -173,7 +173,8 @@ export WRS_MAKE_J=-j$WRS_MAKE_J_NUMBER
 # Also, check the configuration each time this is executed (i.e., each step)
 WRS_CONFIG_DIR=$(dirname "$WRS_BASE_DIR")
 if [ -f "$WRS_CONFIG_DIR/.config" ]; then
-    true
+    # If Kconfig changed since last build, add missing items
+    (cd "$WRS_CONFIG_DIR" && yes "" | make oldconfig)
 else
    echo "No configuration, using default" >& 2
    (cd "$WRS_CONFIG_DIR" && make defconfig)