Add build profile flags to clarify which profile is used

Since the ways to identify the build profile are different from each
other, it is better to define flags for them for the readability and
maintainability.
 * WITH_DA: 1 if profile is DA, else 0
 * WITH_VD: 1 if profile is VD, else 0
 * WITH_VD_MV: 1 if profile is movable, else 0

Change-Id: Ibcd052a87b9aa8017f0dcc1415d6f09c8f61d7e7
Signed-off-by: SangYoun Kwak <sy.kwak@samsung.com>

diff --git a/packaging/hal-api-common.spec b/packaging/hal-api-common.spec
index dd2aab8cedb09973ad0ec1e1ade6e0a3dd0737ea..b2b5e32da4fb4a3d6726ac0dbdfa7cf094603fc0 100644 (file)
--- a/packaging/hal-api-common.spec
+++ b/packaging/hal-api-common.spec
@@ -1,7 +1,26 @@
 %define name           hal-api-common
 %define devel_name     hal-api-common-devel
 %define test_name      hal-api-common-haltests
-%if "%{tizen_profile_name}" != "tv" && "%{mv_prj}" != "1"
+
+%if "%{tizen_profile_name}" == "tv"
+%define WITH_VD 1
+%else
+%define WITH_VD 0
+%endif
+
+%if "%{mv_prj}" == "1"
+%define WITH_VD_MV 1
+%else
+%define WITH_VD_MV 0
+%endif
+
+%if "%{_with_da_profile}" == "1"
+%define WITH_DA 1
+%else
+%define WITH_DA 0
+%endif
+
+%if "%{WITH_VD}" != "1" && "%{WITH_VD_MV}" != "1"
 %define enable_halcc 1
 %define enable_hal_backend_service 1
 %else