Gregg, That?s not to confuse the fact that cleanup could certainly occur.
Thanks, Joey Morrow From: Morrow, Joseph L Sent: Friday, June 3, 2016 11:57 AM To: 'Gregg Reynolds' <dev at mobileink.com>; iotivity-dev at lists.iotivity.org Subject: RE: [dev] build parameters Hi Gregg, At location ?IOTIVITY/resource/csdk/stack?, you will see that this is the C SDK. This is compiled in C, not C++. Also, other platforms which may not utilize C++ 11 are supported (eg. Arduino). 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 Gregg Reynolds Sent: Friday, June 3, 2016 11:45 AM To: iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org> Subject: [dev] build parameters I'm beginning to get the hang of scons. One question I have is why are the same flags set over and over in the local SConscripts? In working on the darwin port I found -std=c++11 eliminated some warnings (or something, of course now I forget), and since c++0x is obsolete anyway I decided to replace it everywhere. (Any reason not to do this?) Then it dawned on me that this can be set globally. So I added env['CXXFLAGS'] = ['-std=c++11'] to the main SConstruct file. And it seems to work. Is there some reason this is not done? I can't really see the advantage of setting this explicitly in every scons file. Ditto for lots of other flags. thanks, gregg -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160603/8f5098a0/attachment.html>
