Hello N Ravi, Please pull latest master branch. This problem has been fixed. Now when you set RELEASE to '0' 'false' or 'no' (actually when you set it to anything other than ['y', 'yes', 'true', 't', '1', 'on', 'all']), the LOGGING default value will be "true" (unless the TEST param is "true", then LOGGING will default to false).
Again, please pull the latest master branch and you will see different (the right!) results. Thanks, Joey -----Original Message----- From: RAVI NANJUNDAPPA [mailto:[email protected]] Sent: Friday, May 29, 2015 3:09 AM To: Morrow, Joseph L; Light, John J; iotivity-dev at lists.iotivity.org Subject: Re: Re: [dev] build RELEASE=0 not working Hi All, (re-sending the mail in the plain text format. Sorry for the inconvenience). Sharing my observation in my development environment. I hope this is of useful in this context. I tried the following in my Ubuntu machine (x86 - 32bit platform) $ scons resource RELEASE=0 -h $ scons resource RELEASE=0 TEST=1 -h $ scons resource RELEASE=1 -h In all the cases/scenarios, LOGGING is false, as that's the default setting. My development environment is : TARGET_OS: linux TARGET_ARCH: x86 and $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 12.04.5 LTS Release: 12.04 Codename: precise Thanks and Best Regards, N Ravi ------- Original Message ------- Sender : Morrow, Joseph L<joseph.l.morrow at intel.com> Date : May 29, 2015 01:37 (GMT+05:30) Title : Re: [dev] build RELEASE=0 not working Hi All, I have uploaded a changeset which fixes this issue where the SCons param "LOGGING" default value is incorrectly set when RELEASE==false. It was only never right when you set RELEASE to anything other than the exact phrase "false". For instance "0" would not work correctly. This changeset can be found here: https://gerrit.iotivity.org/gerrit/#/c/1130/ Thanks, Joey From: Light, John J Sent: Thursday, May 28, 2015 10:48 AM To: Morrow, Joseph L; iotivity-dev at lists.iotivity.org Subject: RE: build RELEASE=0 not working Joey, That's sorta what I thought, though I hadn't understood the separate LOGGING variable. My build line is scons resource RELEASE=0 According to what you wrote, I would expect LOGGING to be true. But when I run scons resource RELEASE=0 -h I see LOGGING: Enable stack logging (yes|no) default: False actual: False I'm not opposed to setting the LOGGING flag now that I know about it, but I'm surprised by current behavior. John Intel OTC OIC Development From: Morrow, Joseph L Sent: Thursday, May 28, 2015 7:40 AM To: Light, John J; iotivity-dev at lists.iotivity.org Subject: RE: build RELEASE=0 not working Hi John, Hi John, Please also see the flag "LOGGING". Also, take note of the effect that "TEST=1" has on "LOGGING" as shown below: If just RELEASE=0, then default for LOGGING=true If RELEASE=0 && TEST=1, then default for LOGGING=false In all other cases (ie. RELEASE=1), the default for LOGGING=false Thanks, Joey Morrow From: iotivity-dev-bounces at lists.iotivity.org [mailto:[email protected]] On Behalf Of Light, John J Sent: Thursday, May 28, 2015 10:31 AM To: iotivity-dev at lists.iotivity.org Subject: [dev] build RELEASE=0 not working I typically build with RELEASE=0 during development, and I build before pushing to Gerrit. Recently I've been getting back Jenkins builds that get real errors in, for example, caipclient.c OIC_LOG_V. The arguments to OIC_LOG_V needed to be changed, but I didn't get any indication from my local build with RELEASE=0. It's as if my local build wasn't building DEBUG. I run "-h" on my scons line, and it reports RELEASE is False. Any thoughts? Am I missing something? John Light Intel OTC OIC Development
