I've looked a bit closer into this, and I've noticed that the Tizen scripts are doing AddOption in both connectivity/build/SConscript and connectivity/samples/tizen/SConscript. Additionally, we set the same option in build_common/SConscript.
It seems that the error is that we're defining it multiple times in a single build, in this case, "building com.oic.ca.sample.spec (user abuild)" Does your team have any idea what this issue might be? can you submit a patch to fix this? Thanks, Erich On Wed, 2015-07-22 at 16:44 -0700, Erich Keane wrote: > Hi Abhishek: > I'm not sure which commit caused it, but I'm seeing Tizen build issues, > like here: > https://build.iotivity.org/ci/job/Verify-IoTivity-Tizen/23/console > > I was wondering if you ahd any idea what the cause of this is? I am > lookinga t the build scripts, but don't really see anything. > > The blockwise-transfer, and camessagehandler merges both made it to > master, but otherwise I'm not sure what could ahve caused these. > > Thanks, > Erich > > > On Tue, 2015-07-21 at 11:25 +0000, Abhishek Pandey (Code Review) wrote: > > Abhishek Pandey has posted comments on this change. > > > > Change subject: Re-enable Tizen build > > ...................................................................... > > > > > > Patch Set 1: > > > > Please take the changes in https://gerrit.iotivity.org/gerrit/#/c/1755/ > > to fix Tizen build errors related to ifaddrs.c. > > >
