Disable component build automagically
authorBalazs Kelemen <b.kelemen@samsung.com>
Thu, 4 Sep 2014 20:01:46 +0000 (16:01 -0400)
committerYoungsoo Choi <kenshin.choi@samsung.com>
Tue, 10 Jul 2018 06:57:09 +0000 (06:57 +0000)
I regularly run into this. For open source developement the component
build is a great feature so it should be ok to keep it to be on by default.
This change adds a tiny bit of logic to the build system to disable it
automatically as it is not compatible with chromium-efl.

Bug: N/A

Change-Id: Ifcbbee3d8763f299752584b804108f41bac67b41
Signed-off-by: Balazs Kelemen <b.kelemen@samsung.com>
tizen_src/build/common.sh

index cd221be..0d33de1 100644 (file)
@@ -10,6 +10,13 @@ if [[ -z "${CHROME_SRC}" ]]; then
   export CHROME_SRC="${PROJECT_ROOT_PATH}/src"
 fi
 
+ORI_GYP_DEFINES=$GYP_DEFINES
+export GYP_DEFINES=$(echo $GYP_DEFINES | sed 's/component=shared_library//g')
+if [ "$ORI_GYP_DEFINES" != "$GYP_DEFINES" ]; then
+    echo "WARNING: component build is not supported!"
+    echo "removing component=shared_library from GYP_DEFINES"
+fi
+
 function applyPatch {
   directory=$1
   shift