The least desirable outcome is to have a broken services code on master for any
period of time once the patch 894 is merged.
Uze, would it be possible for you to amend the patch 894 to include the latest
fixes from android-api branch? Thereafter, we can completely abandon the
android-api branc
Hi Erich,
My request looks like slightly different from your understanding.
Change-894 has merge issue now and you need to update it with different patch.
When you update it, please include our today's works on android-api. (Change
911, Change 910, Change 914 and so on.)
These commits are alread
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150507/71c3bc0a/attachment.html>
-- next part --
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 7198 bytes
Desc: not available
URL:
<http://lists.iotivity.org/piperma
ttp://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150507/0d5213d8/attachment.html>
On Thu, 2015-05-07 at 18:40 +0900, ???(Uze Choi) wrote:
> Hi Erich,
>
> My request looks like slightly different from your understanding.
>
> Change-894 has merge issue now and you need to update it with different patch.
It'll definitely need to be rebased. There is an intent to do so.
> When
lcheck/SeenTimeChecker?do=fe69aed3ab8a86cade6eea0e2084fb4e9edd29ce8d48c5d5a1889aa8efbbee47738ed17e7639ce1f641b1a8c451b073656239170f5eb4b5c326bbdfb2ea96a2fcf878f9a26ce15a0]
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.iotivity.org/pipermail/iotivity-dev/a
was scrubbed...
URL:
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150507/0664a057/attachment.html>
I would like to add one issue to the proposal.
Currently, the connectivity abstraction is treated as a separate library
(libconnectivity-abstraction). I believe Thiago's proposal involves getting
rid of this, and I concur. There should be only one library for the stack.
I mention this because
Hey!
On Thu, May 7, 2015 at 2:47 AM, Lenahan, Charlie
wrote:
> I have a similar change that was for our objective-c/darwin/ios branch.
>
> I didn?t use a full structure thought(just a callbackParam), because
> the app is responsible for unregisterResource and know when to delete its
> context.
O
Hi Berine/Tim
I appreciate you your effort for android api working in base layer.
Anyway, by today there will be couple of update from primitive services on
android-api branch.
Please apply this change on this 894 commit by addon patch.
We have a hard time for build check in android platform,
As
ttp://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150507/60ac79b3/attachment.html>
Hi!
I've found that if I modify the command line which links
liboctbstack.so to manually include libcoap_coap_list.o from libcoap,
then those symbols still show up as missing, but my linking works:
gcc
-o out/linux/x86_64/release/resource/csdk/liboctbstack.so
-ldl
-lpthread
-m64
-shared
Hi!
Would it be possible to modify the signature for OCCreateResource and
OCEntityHandler such that it works the same way as OCDoResource - i.e.
OCCreateResource accepts a structure similar to OCCallbackData (maybe
OCResourceCallbackData or something) which contains a callback, a
context, and a de
Hi!
nm -a out/linux/x86_64/release/liboctbstack.so | grep ' U ' | grep -v 'GLIBC'
U coap_delete_list
U coap_insert
U coap_new_listnode
It's very strange that these symbols are missing since they seem to be
provided by libcoap.a, and libcoap.a is being included in
liboctbstack.so ...
Now, for com
--
An HTML attachment was scrubbed...
URL:
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150507/50a088d6/attachment.html>
An HTML attachment was scrubbed...
URL:
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150507/d675c3f1/attachment.html>
-- next part --
A non-text attachment was scrubbed...
Name: 201505071044764_EM6S04A2.gif
Type: image/gif
Size: 13168 bytes
Des
next part --
An HTML attachment was scrubbed...
URL:
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150507/245e11d4/attachment.html>
Responses inline:
On Thu, 2015-05-07 at 09:28 +0900, ???(Uze Choi) wrote:
> Hi Berine/Tim
>
> I appreciate you your effort for android api working in base layer.
> Anyway, by today there will be couple of update from primitive services on
> android-api branch.
Android-api branch is effectively c
18 matches
Mail list logo