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: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<mailto: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
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150528/af5842e6/attachment.html>
