Build content_shell by default in desktop build

If you don't like to build it, pass '--no-content-shell' to build_desktop.sh.
Reviewed by: Antonio Gomes, Hyunhak Kim

Change-Id: I23e42e9a3ee1138f9b51c6d3bda229765c6bd019
Signed-off-by: SeungSeop Park <sns.park@samsung.com>

diff --git a/tizen_src/build/common.sh b/tizen_src/build/common.sh
index 29b0c2d..a22fe68 100755 (executable)
--- a/tizen_src/build/common.sh
+++ b/tizen_src/build/common.sh
@@ -39,7 +39,7 @@ OPTIONS:
    --build-ewk-unittests Build ewk unittests
    --ccache              Configure ccache installed in your system
    --clang               Use chromium's clang compiler to build the sources
-   --content-shell       Build content_shell application
+   --no-content-shell    Don't build content_shell application
    --debug               Build debug version of chromium-efl (out.${host_arch}/Debug instead of out.${host_arch}/Release)
    -jN                   Set number of jobs, just like with make or ninja
    --skip-gyp            Skip restore_gyp, jhbuild and gyp_chromium steps
@@ -62,7 +62,7 @@ function parseHostBuildScriptParams() {
   export FORCE_JHBUILD=0
   export SKIP_NINJA=0
   export BUILD_EWK_UNITTESTS=0
-  export BUILD_CONTENT_SHELL=0
+  export BUILD_CONTENT_SHELL=1
   export BUILD_XWALK=0
   export BUILD_SUBDIRECTORY=Release
   export COMPONENT_BUILD=0
@@ -86,8 +86,8 @@ function parseHostBuildScriptParams() {
       --clang)
         export USE_CLANG=1
         ;;
-      --content-shell)
-        export BUILD_CONTENT_SHELL=1
+      --no-content-shell)
+        export BUILD_CONTENT_SHELL=0
         ;;
       --force-jhbuild)
         export FORCE_JHBUILD=1