From 166397238603b9b4d444513fe23309e8874f0b29 Mon Sep 17 00:00:00 2001 From: sunghan Date: Thu, 3 Aug 2017 14:32:33 +0900 Subject: [PATCH] check whether CONFIG_NAME is valid or not at create_appspec.sh If Kconfig_ENTRY is not existed, CONFIG_NAME is not valid. IF CONFIG_NAME is not valid, let's skip to make an application list. Here is an abnormal case. { aws_sample, aws_sample_main, CONFIG_, y, y, } --- apps/tools/create_appspec.sh | 3 +++ 1 file changed, 3 insertions(+) diff --git a/apps/tools/create_appspec.sh b/apps/tools/create_appspec.sh index b013905..f64523d 100755 --- a/apps/tools/create_appspec.sh +++ b/apps/tools/create_appspec.sh @@ -37,6 +37,9 @@ do APPNAME=`sed -n '/^APPNAME/p' $APPDIR$FILE$MAKEFILE | sed -n 's/APPNAME = //p'` FUNCTION=`sed -n '/^FUNCNAME/p' $APPDIR$FILE$MAKEFILE | sed -n 's/FUNCNAME = //p'` CONFIG_NAME=`sed -n '/depends/p' $APPDIR$FILE$KCONFIG_ENTRY | sed -n 's/.*depends on //p'` + if [ "$CONFIG_NAME" = "" ]; then + continue + fi CHECK=`sed -n "/# CONFIG_$CONFIG_NAME is not set/p" $DOTCONFIG` if [ "$CHECK" = "" ] then CONFIG_USE="y" -- 2.7.4