notification: Enable SECURED build of unit tests. 71/22171/14
authorPawel Winogrodzki <pawelwi@microsoft.com>
Sat, 8 Jul 2017 00:28:37 +0000 (17:28 -0700)
committerMats Wichmann <mats@linux.com>
Tue, 15 May 2018 17:39:43 +0000 (17:39 +0000)
The notification consumer and provider tests didn't include
the "SECURED" macros for builds with security turned on, even
though it seems clear from the code, that it expected that macro
to be present in some cases.

Bug: https://jira.iotivity.org/browse/IOT-1583
Change-Id: I1166a60c2ad821a7d6002e22a8c9e8bda7321800
Signed-off-by: Pawel Winogrodzki <pawelwi@microsoft.com>
Reviewed-on: https://gerrit.iotivity.org/gerrit/21329
Tested-by: jenkins-iotivity <jenkins@iotivity.org>
Reviewed-by: Dan Mihai <Daniel.Mihai@microsoft.com>
Reviewed-by: Phil Coval <philippe.coval@osg.samsung.com>
(cherry picked from commit e3968b9a84ac1e577feac2924980a0ffc6846f21)

service/notification/unittest/SConscript

index eb83218..1818d8f 100644 (file)
@@ -80,6 +80,7 @@ notification_test_env.PrependUnique(CPPPATH=[
 if env.get('WITH_TCP') == True:
     notification_test_env.AppendUnique(CPPDEFINES=['WITH_TCP'])
 if env.get('SECURED') == '1':
+    notification_test_env.AppendUnique(CPPDEFINES=['SECURED'])
     notification_test_env.AppendUnique(
         LIBS=['mbedtls', 'mbedx509', 'mbedcrypto'])
     notification_test_env.AppendUnique(