.dll isn?t created (this might be a build issue in itself).
Is there another trick to get the octbstack.dll created with TEST=0 ?
Thanks
/Morten
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/2016
FindResource option on Eclipse Simulator.
Please Suggest on it.
--
With Regard's'
Matta Jayaram
+91-9493952323
+91-8096796118
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20161227/9357fbdd/attachment.html>
be a build issue in itself).
Is there another trick to get the octbstack.dll created with TEST=0 ?
Thanks
/Morten
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20161227/a8a4212e/attachment.html>
nd creds, and ACLs, just like
> any other resource action. See p. 100 of the security spec, which includes
> "discover" in the "R" access policy - to allow discovery, your ACL must
> include that, AFAIK. There is not, to my knowledge, anything in the Spec
> that address
_
> iotivity-dev mailing list
> iotivity-dev at lists.iotivity.org
> https://lists.iotivity.org/mailman/listinfo/iotivity-dev
>
>
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.iotivity.org/pipermail/iotivity
s subject to the same security constraints as any others,
>> which means in particular - to address the OP's question - that it is not
>> the case that "any client capable of discovering whatever device running
>> the stack". Since a "device" is just a resource, like any other.
>>
>> HTH
>>
>> gregg
>>
>> ___
>> iotivity-dev mailing list
>> iotivity-dev at lists.iotivity.org
>> https://lists.iotivity.org/mailman/listinfo/iotivity-dev
>>
>>
>
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20161227/b9acb699/attachment.html>
