Fixed issue where Scons param 'LOGGING' is assigned wrong default value.
authorJoseph Morrow <joseph.l.morrow@intel.com>
Thu, 28 May 2015 19:57:09 +0000 (15:57 -0400)
committerErich Keane <erich.keane@intel.com>
Thu, 28 May 2015 20:53:16 +0000 (20:53 +0000)
This will fix issue reported on the IoTivity dev list where the flag
for Stack Logging (ie. TB_LOG) was not being enabled in any Debug build
that wasn't invoked by using exactly "false" for the Scons param
'RELEASE'.

Change-Id: I19677113d3d195059cf15c7073adc6418a152a1f
Signed-off-by: Joseph Morrow <joseph.l.morrow@intel.com>
Reviewed-on: https://gerrit.iotivity.org/gerrit/1130
Reviewed-by: Erich Keane <erich.keane@intel.com>
Reviewed-by: John Light <john.j.light@intel.com>
Reviewed-by: Doug Hudson <douglas.hudson@intel.com>
Tested-by: jenkins-iotivity <jenkins-iotivity@opendaylight.org>
build_common/SConscript

index 5666630..02cbed3 100644 (file)
@@ -53,7 +53,10 @@ require_upload = ARGUMENTS.get('UPLOAD', False)
 if ARGUMENTS.get('TEST'):
        logging_default = False
 else:
-       logging_default = (ARGUMENTS.get('RELEASE', True) == 'false')
+       release_mode = False
+       if ARGUMENTS.get('RELEASE', True) in ['y', 'yes', 'true', 't', '1', 'on', 'all']:
+               release_mode = True
+       logging_default = (release_mode == False)