[dev] 1.3-rel Branch out/QA start request.

[Bell, Richard S]

Uze,
I notice that you had created the 1.3-rel branch but no tag.
Will there be a tag?

I have created the 1.3-rel branch for iotivity-upnp-bridge 
(https://gerrit.iotivity.org/gerrit/#/admin/projects/iotivity-upnp-bridge,branches)
I will add the a similar tag when put in iotivity.
We will test 1.3-rel branch for iotivity-upnp-bridge with 1.3-rel branch 
iotivity.

Thanks,
-Rick

From: iotivity-dev-bounces at lists.iotivity.org 
[mailto:iotivity-dev-boun...@lists.iotivity.org] On Behalf Of ???
Sent: Monday, April 10, 2017 3:50 PM
To: Kevin Kane ; Mats Wichmann ; 
iotivity-dev at lists.iotivity.org
Subject: Re: [dev] 1.3-rel Branch out/QA start request.

Definitely.
Please mergeback into master after work on 1.3-rel if not release branch 
specific.
BR Uze Choi

- Original Message -
Sender : Kevin Kane mailto:kkane at microsoft.com>>
Date : 2017-04-11 07:31 (GMT+9)
Title : RE: RE: [dev] 1.3-rel Branch out/QA start request.
For changes that are already pending, that sounds fine, especially since the 
branches haven?t yet diverged at all. But from this point forward, for any new 
changes, let?s submit directly to 1.3-rel and then have a regular merge cadence.

From: ??? [mailto:uzc...@samsung.com]
Sent: Monday, April 10, 2017 3:24 PM
To: Kevin Kane mailto:kkane at microsoft.com>>; Mats 
Wichmann mailto:mats at wichmann.us>>; iotivity-dev at 
lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org>
Subject: RE: RE: [dev] 1.3-rel Branch out/QA start request.

Hi Kevin,
Thank you for your suggestion.
It will be good to strictly follow the release branch merging policy.
However for the better efficiency, let's accept currently pending commits 
merged into master branch first and cherrypick in to 1.3-rel as a next step.
BR Uze Choi

- Original Message -
Sender : Kevin Kane mailto:kkane at microsoft.com>>
Date : 2017-04-11 06:14 (GMT+9)
Title : RE: [dev] 1.3-rel Branch out/QA start request.

It'd be better for any 1.3 changes/bug fixes to be committed directly to 
1.3-rel, and then 1.3-rel should be merged regularly into master to pick those 
changes up for the future. I'd suggest any pending changes on master that 
should be in 1.3 be abandoned and resubmitted to 1.3-rel. All the 
cherry-picking that happened between 1.2-rel and master did not work well at 
all.



-Original Message-

From: iotivity-dev-bounces at lists.iotivity.org<mailto:iotivity-dev-bounces at 
lists.iotivity.org> [mailto:iotivity-dev-boun...@lists.iotivity.org] On Behalf 
Of Mats Wichmann

Sent: Monday, April 10, 2017 1:50 PM

To: ??? (Uze Choi) mailto:uzchoi at samsung.com>>; 
iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org>

Subject: Re: [dev] 1.3-rel Branch out/QA start request.



On 04/10/2017 04:57 AM, ??? (Uze Choi) wrote:

> Hi All,

>

>

>

> 1.3-rel branch has been created. 1.3.0 Release period just started.

>

> There are approximately 70 change sets waiting merge on the master

> branches

>

> Except this patches, All code merge should have the release management Lead 
> review +1 on the release branch.





So for owners of waiting changesets... how do we proceed?  The small number I 
have in the queue (five public) I would not consider release-critical, but also 
letting master and 1.3-rel diverge is not wonderful, makes lots of work later 
for someone - I'm remembering what Phil and others had to do to get master back 
in sync with 1.2-rel.



Advice please?







___

iotivity-dev mailing list

iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org>

https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.iotivity.org%2Fmailman%2Flistinfo%2Fiotivity-dev=02%7C01%7Ckkane%40microsoft.com%7C3a7057b259e34a700d8608d4805326b6%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636274542026472282=kaW7CiPhNlVkyehkZTEnFkQMMNTJXNXUHlkjKaXuMWQ%3D=0






[cid:image001.gif at 01D2B2CE.16E63B40]

[http://ext.samsung.net/mail/ext/v1/external/status/update?userid=uzchoi=bWFpbElEPTIwMTcwNDEwMjI1MDAxZXBjbXMxcDc0NWFkNzAyODE2MThlOTBlMjU3YjJkOTJjYTIyYWRkYyZyZWNpcGllbnRBZGRyZXNzPWlvdGl2aXR5LWRldkBsaXN0cy5pb3Rpdml0eS5vcmc_]
-- next part --
An HTML attachment was scrubbed...
URL: 
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170411/9b021e2f/attachment.html>
-- next part --
A non-text attachment was scrubbed...
Name: image001.gif
Type: image/gif
Size: 13402 bytes
Desc: image001.gif
URL: 
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170411/9b021e2f/attachment.gif>

[dev] Android build fails in 1.3-rel branch

[Nash, George]

ile "/home/jhha85/workspace/iotivity/build_common/android/SConscript", line 
12:
SConscript('../../extlibs/android/ndk/SConscript')
  File "/usr/lib/scons/SCons/Script/SConscript.py", line 614:
return method(*args, **kw)
  File "/usr/lib/scons/SCons/Script/SConscript.py", line 551:
return _SConscript(self.fs, *files, **subst_kw)
  File "/usr/lib/scons/SCons/Script/SConscript.py", line 260:
exec _file_ in call_stack[-1].globals
  File "/home/jhha85/workspace/iotivity/extlibs/android/ndk/SConscript", line 
25:
env.Download('android-ndk-r10d.bin', 
'http://dl.google.com/android/ndk/android-ndk-r10d-linux-x86_64.bin')



Is there anyone who knows the problem and how to resolve this?

My linux machine is Ubuntu 16.04.



Thank you.



Best Regards,



Jihun Ha (???/???, Ph.D.)

IoT, IoTivity, OIC | IoT Lab

Software R Center | Samsung Electronics Co., Ltd

Mobile +82 10 2533 7947

jihun.ha at samsung.com | jhha85 at gmail.com

___

iotivity-dev mailing list

iotivity-dev at lists.iotivity.org

https://lists.iotivity.org/mailman/listinfo/iotivity-dev





[cid:image001.gif at 01D2B2C3.10E69740]

[Image removed by sender.]
-- next part --
An HTML attachment was scrubbed...
URL: 
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170411/f0899a87/attachment.html>
-- next part --
A non-text attachment was scrubbed...
Name: ~WRD000.jpg
Type: image/jpeg
Size: 823 bytes
Desc: ~WRD000.jpg
URL: 
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170411/f0899a87/attachment.jpg>
-- next part --
A non-text attachment was scrubbed...
Name: image001.gif
Type: image/gif
Size: 13402 bytes
Desc: image001.gif
URL: 
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170411/f0899a87/attachment.gif>

[dev] Visual Studio 2017

[Morten Nielsen]

Sorry for being impatient - I?ll slowly drag my feet over and install some most 
stuff on my puny harddrive ?

/Morten


From: Dave Thaler<mailto:dtha...@microsoft.com>
Sent: Tuesday, April 11, 2017 10:59 AM
To: Morten Nielsen<mailto:mn at iter.dk>; Mats Wichmann<mailto:mats at 
wichmann.us>; Morrow, Joseph L<mailto:joseph.l.morrow at intel.com>; 
iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org>
Cc: mashraf at asp-netconsulting.com<mailto:mashraf at asp-netconsulting.com>
Subject: RE: [dev] Visual Studio 2017

One step at a time.  Yes I believe the 2017 toolset should be supported, but my 
understanding is that first requires some changes to scons to support VS2017.

From: Morten Nielsen [mailto:m...@iter.dk]
Sent: Tuesday, April 11, 2017 10:38 AM
To: Mats Wichmann ; Dave Thaler ; Morrow, Joseph L ; iotivity-dev 
at lists.iotivity.org
Cc: mashraf at asp-netconsulting.com
Subject: RE: [dev] Visual Studio 2017

So there are no plans to support the VS2017 toolset too? I was hoping to not 
add so much extra crap, and if I?m not mistaken I need the latest toolset to 
build for UWP SDK 10063.


/Morten


From: Mats Wichmann<mailto:m...@wichmann.us>
Sent: Tuesday, April 11, 2017 10:11 AM
To: Dave Thaler<mailto:dthaler at microsoft.com>; Morrow, Joseph 
L<mailto:joseph.l.morrow at intel.com>; Morten Nielsen<mailto:mn at iter.dk>; 
iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org>
Cc: mashraf at asp-netconsulting.com<mailto:mashraf at asp-netconsulting.com>
Subject: Re: [dev] Visual Studio 2017

On 04/10/2017 01:57 PM, Dave Thaler wrote:
> Thanks Ashraf and Joey.
> I've updated the iotivity wiki 
> page<https://wiki.iotivity.org/windows<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwiki.iotivity.org%2Fwindows=02%7C01%7Cdthaler%40microsoft.com%7C1256ef5278ac45e0114008d481017952%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636275290711257445=6g1BW6yKvcuXCfy2bxSwNYgSs1YwcY1vHXMBxRk9yeM%3D=0>>
>  with that information.

While we're at it, I used that page a while back to set up the builds
I've done on Windows (vs 2015 installed), and it worked fine.

But when it came to trying things ("Execution" section), it did not work
as documented.  Do we know if those instructions are vetted? e.g.

run server

leads to
The system cannot find the path specified.
'simpleserver.exe' is not recognized as an internal or external command,
operable program or batch file.
Done


I needed to navigate to the place it was stored under out
(out\windows\amd64\release\resource\examples), AND then copy in a copy
of octbstack.dll from two levels up, to get the
simpleclient/simpleserver to run.

Is there some extra path setup that either needs to be done by the
developer or needs to go into build.bat (since apparently build.bat is
expected to know about the examples)?




-- next part --
An HTML attachment was scrubbed...
URL: 
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170411/14c5cf52/attachment.html>

[dev] Visual Studio 2017

[Dave Thaler]

One step at a time.  Yes I believe the 2017 toolset should be supported, but my 
understanding is that first requires some changes to scons to support VS2017.

From: Morten Nielsen [mailto:m...@iter.dk]
Sent: Tuesday, April 11, 2017 10:38 AM
To: Mats Wichmann ; Dave Thaler ; Morrow, Joseph L ; iotivity-dev 
at lists.iotivity.org
Cc: mashraf at asp-netconsulting.com
Subject: RE: [dev] Visual Studio 2017

So there are no plans to support the VS2017 toolset too? I was hoping to not 
add so much extra crap, and if I'm not mistaken I need the latest toolset to 
build for UWP SDK 10063.


/Morten


From: Mats Wichmann<mailto:m...@wichmann.us>
Sent: Tuesday, April 11, 2017 10:11 AM
To: Dave Thaler<mailto:dthaler at microsoft.com>; Morrow, Joseph 
L<mailto:joseph.l.morrow at intel.com>; Morten Nielsen<mailto:mn at iter.dk>; 
iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org>
Cc: mashraf at asp-netconsulting.com<mailto:mashraf at asp-netconsulting.com>
Subject: Re: [dev] Visual Studio 2017

On 04/10/2017 01:57 PM, Dave Thaler wrote:
> Thanks Ashraf and Joey.
> I've updated the iotivity wiki 
> page<https://wiki.iotivity.org/windows<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwiki.iotivity.org%2Fwindows=02%7C01%7Cdthaler%40microsoft.com%7C1256ef5278ac45e0114008d481017952%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636275290711257445=6g1BW6yKvcuXCfy2bxSwNYgSs1YwcY1vHXMBxRk9yeM%3D=0>>
>  with that information.

While we're at it, I used that page a while back to set up the builds
I've done on Windows (vs 2015 installed), and it worked fine.

But when it came to trying things ("Execution" section), it did not work
as documented.  Do we know if those instructions are vetted? e.g.

run server

leads to
The system cannot find the path specified.
'simpleserver.exe' is not recognized as an internal or external command,
operable program or batch file.
Done


I needed to navigate to the place it was stored under out
(out\windows\amd64\release\resource\examples), AND then copy in a copy
of octbstack.dll from two levels up, to get the
simpleclient/simpleserver to run.

Is there some extra path setup that either needs to be done by the
developer or needs to go into build.bat (since apparently build.bat is
expected to know about the examples)?




-- next part --
An HTML attachment was scrubbed...
URL: 
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170411/5c9fc5fe/attachment.html>

[dev] 1.3-rel Branch out/QA start request.

[Kevin Kane]

Two more things:


  1.  Do we have a resource available to make sure there are regular merges 
from 1.3-rel to master? This also means there should never be a cherry-pick 
from 1.3-rel to master.
  2.  For changes already up for master to be later cherry-picked: There was 
confusion during 1.2 about who was responsible for doing the cherry-picks. I 
suggest this time around, if an author has submitted a change to master and 
believes it should be on 1.3-rel, the author is responsible for doing the 
cherry-pick and getting the appropriate people on the review, to shepherd the 
change into 1.3-rel. There should be no expectation that anyone else will 
cherry-pick the change to 1.3-rel.

From: ??? [mailto:uzc...@samsung.com]
Sent: Monday, April 10, 2017 3:50 PM
To: Kevin Kane ; Mats Wichmann ; 
iotivity-dev at lists.iotivity.org
Subject: RE: RE: RE: [dev] 1.3-rel Branch out/QA start request.

Definitely.
Please mergeback into master after work on 1.3-rel if not release branch 
specific.
BR Uze Choi

- Original Message -
Sender : Kevin Kane mailto:kkane at microsoft.com>>
Date : 2017-04-11 07:31 (GMT+9)
Title : RE: RE: [dev] 1.3-rel Branch out/QA start request.
For changes that are already pending, that sounds fine, especially since the 
branches haven?t yet diverged at all. But from this point forward, for any new 
changes, let?s submit directly to 1.3-rel and then have a regular merge cadence.

From: ??? [mailto:uzc...@samsung.com]
Sent: Monday, April 10, 2017 3:24 PM
To: Kevin Kane mailto:kkane at microsoft.com>>; Mats 
Wichmann mailto:mats at wichmann.us>>; iotivity-dev at 
lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org>
Subject: RE: RE: [dev] 1.3-rel Branch out/QA start request.

Hi Kevin,
Thank you for your suggestion.
It will be good to strictly follow the release branch merging policy.
However for the better efficiency, let's accept currently pending commits 
merged into master branch first and cherrypick in to 1.3-rel as a next step.
BR Uze Choi

- Original Message -
Sender : Kevin Kane mailto:kkane at microsoft.com>>
Date : 2017-04-11 06:14 (GMT+9)
Title : RE: [dev] 1.3-rel Branch out/QA start request.

It'd be better for any 1.3 changes/bug fixes to be committed directly to 
1.3-rel, and then 1.3-rel should be merged regularly into master to pick those 
changes up for the future. I'd suggest any pending changes on master that 
should be in 1.3 be abandoned and resubmitted to 1.3-rel. All the 
cherry-picking that happened between 1.2-rel and master did not work well at 
all.



-Original Message-

From: iotivity-dev-bounces at lists.iotivity.org<mailto:iotivity-dev-bounces at 
lists.iotivity.org> [mailto:iotivity-dev-boun...@lists.iotivity.org] On Behalf 
Of Mats Wichmann

Sent: Monday, April 10, 2017 1:50 PM

To: ??? (Uze Choi) mailto:uzchoi at samsung.com>>; 
iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org>

Subject: Re: [dev] 1.3-rel Branch out/QA start request.



On 04/10/2017 04:57 AM, ??? (Uze Choi) wrote:

> Hi All,

>

>

>

> 1.3-rel branch has been created. 1.3.0 Release period just started.

>

> There are approximately 70 change sets waiting merge on the master

> branches

>

> Except this patches, All code merge should have the release management Lead 
> review +1 on the release branch.





So for owners of waiting changesets... how do we proceed?  The small number I 
have in the queue (five public) I would not consider release-critical, but also 
letting master and 1.3-rel diverge is not wonderful, makes lots of work later 
for someone - I'm remembering what Phil and others had to do to get master back 
in sync with 1.2-rel.



Advice please?







___

iotivity-dev mailing list

iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org>

https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.iotivity.org%2Fmailman%2Flistinfo%2Fiotivity-dev=02%7C01%7Ckkane%40microsoft.com%7C3a7057b259e34a700d8608d4805326b6%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636274542026472282=kaW7CiPhNlVkyehkZTEnFkQMMNTJXNXUHlkjKaXuMWQ%3D=0






[cid:image001.gif at 01D2B2B1.0748E920]

[http://ext.samsung.net/mail/ext/v1/external/status/update?userid=uzchoi=bWFpbElEPTIwMTcwNDEwMjI1MDAxZXBjbXMxcDc0NWFkNzAyODE2MThlOTBlMjU3YjJkOTJjYTIyYWRkYyZyZWNpcGllbnRBZGRyZXNzPWtrYW5lQG1pY3Jvc29mdC5jb20_]
-- next part --
An HTML attachment was scrubbed...
URL: 
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170411/02343da6/attachment.html>
-- next part --
A non-text attachment was scrubbed...
Name: image001.gif
Type: image/gif
Size: 13402 bytes
Desc: image001.gif
URL: 
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170411/02343da6/attachment.gif>

[dev] Visual Studio 2017

[Morten Nielsen]

So there are no plans to support the VS2017 toolset too? I was hoping to not 
add so much extra crap, and if I?m not mistaken I need the latest toolset to 
build for UWP SDK 10063.


/Morten


From: Mats Wichmann<mailto:m...@wichmann.us>
Sent: Tuesday, April 11, 2017 10:11 AM
To: Dave Thaler<mailto:dthaler at microsoft.com>; Morrow, Joseph 
L<mailto:joseph.l.morrow at intel.com>; Morten Nielsen<mailto:mn at iter.dk>; 
iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org>
Cc: mashraf at asp-netconsulting.com<mailto:mashraf at asp-netconsulting.com>
Subject: Re: [dev] Visual Studio 2017

On 04/10/2017 01:57 PM, Dave Thaler wrote:
> Thanks Ashraf and Joey.
> I've updated the iotivity wiki page<https://wiki.iotivity.org/windows> with 
> that information.

While we're at it, I used that page a while back to set up the builds
I've done on Windows (vs 2015 installed), and it worked fine.

But when it came to trying things ("Execution" section), it did not work
as documented.  Do we know if those instructions are vetted? e.g.

run server

leads to
The system cannot find the path specified.
'simpleserver.exe' is not recognized as an internal or external command,
operable program or batch file.
Done


I needed to navigate to the place it was stored under out
(out\windows\amd64\release\resource\examples), AND then copy in a copy
of octbstack.dll from two levels up, to get the
simpleclient/simpleserver to run.

Is there some extra path setup that either needs to be done by the
developer or needs to go into build.bat (since apparently build.bat is
expected to know about the examples)?





-- next part --
An HTML attachment was scrubbed...
URL: 
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170411/c35589bc/attachment.html>

[dev] Android build fails in 1.3-rel branch

[Mats Wichmann]

On 04/11/2017 02:23 PM, Nash, George wrote:
> For the first error the fix is quite easy I have filed a Jira ticket for that 
> issue and will have a patch submitted shortly
> https://jira.iotivity.org/browse/IOT-2029
> I have not been able to reproduce the second issue.
> I have seen this type of issue when old build products are causing an error.
> Here are two things to try.
> 1st
> Do a clean build
> $> scons TARGET_OS=android TARGET_ARCH=armeabi SECURED=0 LOGGING=1 WITH_TCP=1 
> WITH_CLOUD=1 -c
> $> scons TARGET_OS=android TARGET_ARCH=armeabi SECURED=0 LOGGING=1 WITH_TCP=1 
> WITH_CLOUD=1
> 
> If that does not work manually clean the build output and try again sometimes 
> the scons clean misses something that should have been cleaned and this 
> solves the problem. If you have another build linux or tizen this will wipe 
> out the build output for those OS if you may want to be more selective than 
> this. Sometimes just deleting the .sconsign.dblite file will fix the issue 
> but I normally just rebuild everything.
> $> scons TARGET_OS=android TARGET_ARCH=armeabi SECURED=0 LOGGING=1 WITH_TCP=1 
> WITH_CLOUD=1 ?c
> $> rm -fr out #delete the output directory
> $> rm .sconsign.dblite #delete scons?s database file that it uses for 
> tracking which files need a rebuild.
> $> scons TARGET_OS=android TARGET_ARCH=armeabi SECURED=0 LOGGING=1 WITH_TCP=1 
> WITH_CLOUD=1


I should note the clean targets are relatively broken: scons isn't told
about everything that is built, because some of the things happen
outside defined scons "targets".  So not the fault of scons. Not sure if
that's enough to actually affect a subsequent build, that would take
research I haven't done, but manual cleaning may be a good idea. Recent
not-directly-related but possibly interesting example: I found out a
useful #define from iotivity_config.h was missing, because
iotivity_config.h in resource/c_common is not recreated if it exists,
and nothing ever removes it (it's not a "target", just the effect of
some statements in a file); my copy was six months old and another four
or so checks had been added since).

[dev] Visual Studio 2017

[Mats Wichmann]

On 04/11/2017 12:07 PM, Morten Nielsen wrote:
> Sorry for being impatient - I?ll slowly drag my feet over and install some 
> most stuff on my puny harddrive ?
> 
> /Morten
> 
> 
> From: Dave Thaler
> Sent: Tuesday, April 11, 2017 10:59 AM
> To: Morten Nielsen; Mats Wichmann wichmann.us>; Morrow, Joseph L; 
> iotivity-dev at lists.iotivity.org
> Cc: mashraf at asp-netconsulting.com
> Subject: RE: [dev] Visual Studio 2017
> 
> One step at a time.  Yes I believe the 2017 toolset should be supported, but 
> my understanding is that first requires some changes to scons to support 
> VS2017.

Cool.  In fact this sounds like the problem Morten was complaining about
originally:

https://stackoverflow.com/questions/41106407/programmatically-finding-the-vs2017-installation-directory

In a different thread:

https://pairlist4.pair.net/pipermail/scons-users/2017-March/005785.html


I love the quote, '''Looks like Microsoft "improved" things'''

Hi, Dave!  :)

[dev] Visual Studio 2017

[Mats Wichmann]

On 04/11/2017 11:37 AM, Morten Nielsen wrote:
> So there are no plans to support the VS2017 toolset too? I was hoping to not 
> add so much extra crap, and if I?m not mistaken I need the latest toolset to 
> build for UWP SDK 10063.
> 
> 
> /Morten

Morten, I wouldn't make assumptions about the future; resources are
tight enough right now that essential features are having to squeeze in
just under the wire for 1.3, infrastructure stuff just doesn't have a
lot of attention (in my unique case, I'm not getting paid for iotivity
work, so I can pick what I want to poke at in the time I have to give it).

I'm sure iotivity building will stay up with the latest versions of
build hosts, but it may take some time till folks get around to it,
(we're behind on the Linux side too, and nobody's babysitting Mac builds
at all, it's not even an "official" host).

[dev] Android build fails in 1.3-rel branch

[하지훈]

An HTML attachment was scrubbed...
URL: 
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170411/7178a3a9/attachment.html>
-- next part --
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 13402 bytes
Desc: not available
URL: 
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170411/7178a3a9/attachment.gif>

[dev] [IoTivity Helpdesk #38605] RE: please let's not change file modes carelessly

[CJ Collier via RT]

Uze,

I can have a specific set of builds run a script during the verify phase which 
checks file permissions.  However, I don't know what you need the script to 
verify.  Can you provide a script to do the verification?  I'll make sure the 
script gets executed.

C.J.

[dev] Visual Studio 2017

[Mats Wichmann]

On 04/11/2017 11:05 AM, Mats Wichmann wrote:
> On 04/10/2017 01:57 PM, Dave Thaler wrote:
>> Thanks Ashraf and Joey.
>> I've updated the iotivity wiki page with 
>> that information.
> 
> While we're at it, I used that page a while back to set up the builds
> I've done on Windows (vs 2015 installed), and it worked fine.
> 
> But when it came to trying things ("Execution" section), it did not work
> as documented.  Do we know if those instructions are vetted? e.g.
> 
> run server
> 
> leads to
> The system cannot find the path specified.
> 'simpleserver.exe' is not recognized as an internal or external command,
> operable program or batch file.
> Done
> 
> 
> I needed to navigate to the place it was stored under out
> (out\windows\amd64\release\resource\examples), AND then copy in a copy
> of octbstack.dll from two levels up, to get the
> simpleclient/simpleserver to run.
> 
> Is there some extra path setup that either needs to be done by the
> developer or needs to go into build.bat (since apparently build.bat is
> expected to know about the examples)?

sorry, that's run.bat

[dev] Visual Studio 2017

[Mats Wichmann]

On 04/10/2017 01:57 PM, Dave Thaler wrote:
> Thanks Ashraf and Joey.
> I've updated the iotivity wiki page with 
> that information.

While we're at it, I used that page a while back to set up the builds
I've done on Windows (vs 2015 installed), and it worked fine.

But when it came to trying things ("Execution" section), it did not work
as documented.  Do we know if those instructions are vetted? e.g.

run server

leads to
The system cannot find the path specified.
'simpleserver.exe' is not recognized as an internal or external command,
operable program or batch file.
Done


I needed to navigate to the place it was stored under out
(out\windows\amd64\release\resource\examples), AND then copy in a copy
of octbstack.dll from two levels up, to get the
simpleclient/simpleserver to run.

Is there some extra path setup that either needs to be done by the
developer or needs to go into build.bat (since apparently build.bat is
expected to know about the examples)?

[dev] Keeping connection to RD up.

[Jee Hyeok Kim]

An HTML attachment was scrubbed...
URL: 
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170411/1ed41bca/attachment.html>
-- next part --
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 13402 bytes
Desc: not available
URL: 
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170411/1ed41bca/attachment.gif>

[dev] unauthorized resource observation

[Peter Hatina]

Hello folks,

I encountered a problem with observation of some arbitrary resource -- once I
OC::OCResource::observe() a resource and then cancel the observation via
OC:OCResource::cancelObserve(), I start getting OC_STACK_UNAUTHORIZED_REQ
from various calls.

This issue can be reproduced, for example, with aircondition sample; just apply
this patch:

diff --git a/cloud/samples/client/airconditioner/aircon_controller.cpp 
b/cloud/samples/client/airconditioner/aircon_controller.cpp
index 2235b44..e87866c 100644
--- a/cloud/samples/client/airconditioner/aircon_controller.cpp
+++ b/cloud/samples/client/airconditioner/aircon_controller.cpp
@@ -217,6 +217,12 @@ void getCollectionResource(const HeaderOptions &,

 QueryParamsMap  query;
 g_binaryswitchResource->observe(ObserveType::Observe, query, 
);
+
+if (g_binaryswitchResource->cancelObserve() != OC_STACK_OK)
+std::cerr << "Failed to cancel observation of binary switch 
resource" << std::endl;
+
+if (g_binaryswitchResource->observe(ObserveType::Observe, query, 
) != OC_STACK_OK)
+std::cerr << "Failed to observe a binary switch resource" << 
std::endl;
 }

 if (it->getResourceTypes().at(0).compare("x.samsung.firmware") == 0)

With the example modified in attached way, you won't be able to control the
binary switch anymore:

POST response: 46

Thank you very much for any feedback and help!

-- 
thanks and regards,
Peter Hatina

[dev] Android build fails in 1.3-rel branch

[하지훈]

An HTML attachment was scrubbed...
URL: 
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170411/0d48be1e/attachment.html>
-- next part --
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 13402 bytes
Desc: not available
URL: 
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170411/0d48be1e/attachment.gif>