Hi Gregg, Since there doesn?t appear to be any release development branch, your best bet is to work on master. Anything done on master should make it into the next release as these have historically been created and stemmed from master.
I don?t know if you?ve contributed code to IoTivity yet, but be sure to remember to add reviewers to your changesets on gerrit. Keep in mind you need at least one maintainer/sub-maintainer to approve your changeset before it actually goes into master. Thanks, Joey From: Gregg Reynolds [mailto:[email protected]] Sent: Friday, June 3, 2016 12:23 PM To: Morrow, Joseph L <joseph.l.morrow at intel.com> Cc: iotivity-dev at lists.iotivity.org Subject: Re: [dev] build parameters On Fri, Jun 3, 2016 at 1:56 PM, Morrow, Joseph L <joseph.l.morrow at intel.com<mailto:joseph.l.morrow at intel.com>> wrote: 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). Yep. But I'm sure there's a way to finagle that. I might have to learn a little more scons and python than I really wanted to, but I think it would be worth it in order to make the build system significantly simpler and easier to understand. FYI I'm well on the way to eliminating all warnings, a few of which involve actual bugs. Did you know 'Wno-#pragma-messages' will get rid of that pesky "Use of this header is deprecated" warning from boost? I didn't, but boy am I glad to see them go. If I have fixes like that, should I work directly from the master branch? thanks, gregg -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160603/18175ad1/attachment.html>
