[dev] generic java support merged with master
An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20161213/6d1ea86c/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/20161213/6d1ea86c/attachment.gif>
[dev] generic java support merged with master
I not 100% sure, but I think the only thing needed for the samples is provisioning code. Then they should with SECURED=1. I did discover today that the build will fail with TARGET_TRANSPORT=ALL I have already created a Jira ticket https://jira.iotivity.org/browse/IOT-1677 and I am looking into it. For the time being if you want to use java on Linux specify TARGET_TRANSPORT=IP George From: Thiago Moura [mailto:thiago...@gmail.com] Sent: Tuesday, December 13, 2016 3:06 PM To: Nash, George Cc: iotivity-dev at lists.iotivity.org Subject: Re: [dev] generic java support merged with master Thanks for it!! Great work! What is missing to get samples working with SECURED=1? On Tue, Dec 13, 2016 at 3:36 PM, Nash, George mailto:george.nash at intel.com>> wrote: I the work on the generic java bindings was **merged** with master yesterday: - https://jira.iotivity.org/browse/IOT-1089 - https://gerrit.iotivity.org/gerrit/#/c/14931/ This change moves around all of the java related code. Since there is a java implementation for almost every part of the IoTivity project this change will likely affect every project at least a little. Currently we are not trying to build the generic Java on any platform other than Linux and Android. We tried to keep code changes to a minimum, but the structural changes are quite significant. Directory organization changes: `android` --> `java` `android/android_api/jni` --> `java/jni` `android/android_api/src` --> `java/common/src` --> `java/iotivity-android/src` --> `java/iotivity-linux/src` `android/examples` --> `java/examples-android` New directory: `java/examples-java` Other changes: The jni code is no longer built using Android.mk build files. It is built using scons. Due to the folder reorganization there are changes to multiple build scripts to address the new folder paths. To build the generic-java code: For Android: No change. It builds using the same build instructions as before. For Linux: 1. Specify JAVA_HOME environment variable with the path to the JDK. (i.e. `export JAVA_HOME=/usr/lib/jvm/java-1.8.0/`) 2. `scons BUILD_JAVA=1` #add any additional build options or `autobuild.py linux_unsecured_with_java` or `autobuild.py linux_secured_with_java` Running Linux samples: (Samples currently only works with SECURED=0 build) export LD_LIBRARY_PATH=$(pwd)/out/linux/x86_64/debug/:$LD_LIBRARY_PATH for SimpleClient: java -cp java/examples-java/simpleclient/build/libs/simpleclient.jar:java/iotivity-linux/build/libs/iotivity-linux.jar org.iotivity.base.examples.SimpleClient for SimpleServer: java -cp java/examples-java/simpleserver/build/libs/simpleserver.jar:java/iotivity-linux/build/libs/iotivity-linux.jar org.iotivity.base.examples.SimpleServer Thanks the following people for all their work: Peter Eftime ? for doing the initial work Larry Sachs ? for all the time spent testing and re-testing the android code to make sure it continued to work as expected Rick Bell ? for reviews and the final merge If you have any questions I will do my best to answer them. George ___ iotivity-dev mailing list iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org> https://lists.iotivity.org/mailman/listinfo/iotivity-dev -- Thiago Guedes Cunha de Moura Graduando em Ci?ncia da Computa??o Instituto de Ci?ncias Exatas e Biol?gicas - Universidade Federal de Ouro Preto cel.: (31)99484-9864 -- next part -- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20161213/d5507f3c/attachment.html>
[dev] generic java support merged with master
Thanks for it!! Great work! What is missing to get samples working with SECURED=1? On Tue, Dec 13, 2016 at 3:36 PM, Nash, George wrote: > I the work on the generic java bindings was **merged** with master > yesterday: > > - https://jira.iotivity.org/browse/IOT-1089 > > - https://gerrit.iotivity.org/gerrit/#/c/14931/ > > > > > > This change moves around all of the java related code. Since there is a > java implementation for almost every part of the IoTivity project this > change will likely affect every project at least a little. Currently we are > not trying to build the generic Java on any platform other than Linux and > Android. > > > > We tried to keep code changes to a minimum, but the structural changes are > quite significant. > > > > Directory organization changes: > > `android` --> `java` > > `android/android_api/jni` --> `java/jni` > > `android/android_api/src` --> `java/common/src` > > --> `java/iotivity-android/src` > > --> `java/iotivity-linux/src` > > `android/examples` --> `java/examples-android` > > > > New directory: > > `java/examples-java` > > > > > > Other changes: > > The jni code is no longer built using Android.mk build files. It is built > using scons. > > > > Due to the folder reorganization there are changes to multiple build > scripts to address the new folder paths. > > > > > > To build the generic-java code: > > For Android: > > No change. It builds using the same build instructions as before. > > For Linux: > > 1. Specify JAVA_HOME environment variable with the path to the JDK. > (i.e. `export JAVA_HOME=/usr/lib/jvm/java-1.8.0/`) > > 2. `scons BUILD_JAVA=1` #add any additional build options or > `autobuild.py linux_unsecured_with_java` or `autobuild.py > linux_secured_with_java` > > > > Running Linux samples: (Samples currently only works with SECURED=0 build) > > > > export LD_LIBRARY_PATH=$(pwd)/out/linux/x86_64/debug/:$LD_LIBRARY_PATH > > for SimpleClient: > > java -cp java/examples-java/simpleclient/build/libs/ > simpleclient.jar:java/iotivity-linux/build/libs/iotivity-linux.jar > org.iotivity.base.examples.SimpleClient > > for SimpleServer: > > java -cp java/examples-java/simpleserver/build/libs/ > simpleserver.jar:java/iotivity-linux/build/libs/iotivity-linux.jar > org.iotivity.base.examples.SimpleServer > > > > > > Thanks the following people for all their work: > > Peter Eftime ? for doing the initial work > > Larry Sachs ? for all the time spent testing and re-testing the android > code to make sure it continued to work as expected > > Rick Bell ? for reviews and the final merge > > > > If you have any questions I will do my best to answer them. > > > > George > > > > > > ___ > iotivity-dev mailing list > iotivity-dev at lists.iotivity.org > https://lists.iotivity.org/mailman/listinfo/iotivity-dev > > -- *Thiago Guedes Cunha de Moura* Graduando em Ci?ncia da Computa??o Instituto de Ci?ncias Exatas e Biol?gicas - Universidade Federal de Ouro Preto cel.: (31)99484-9864 -- next part -- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20161213/83764f55/attachment.html>
[dev] Getting all the keys of an OCRepPayload
OCRepPayload has a field called OCRepPayloadValue which is just a simple linked list. While there is no C API that I know that acts like Java?s Map.keySet(), you can iterate through the linked list and check the ?name? field in OCRepPayloadValue and check the type from the OCRepPayloadPropType. The relevant structs are in resource/csdk/stack/include/octypes.h From: iotivity-dev-bounces at lists.iotivity.org [mailto:iotivity-dev-boun...@lists.iotivity.org] On Behalf Of Morten Nielsen Sent: Tuesday, December 13, 2016 10:17 AM To: iotivity-dev at lists.iotivity.org Subject: [dev] Getting all the keys of an OCRepPayload I don?t see any methods in the C-API code that returns a list of all the value keys, or a way to interrogate the value type of a key. It seems to me you have to magically know which values will be there, and what type they are. Am I missing just something here, and there?s a completely different way to do this? Thanks /Morten -- next part -- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20161213/6f2c08c5/attachment.html>
[dev] Iotivity With ESP8266
Dear Team, I ported Iotivity to ESP8266 & I am able to control it From Iotivity Ported Ubuntu PC. Now I want to control it from Iotivity based Android App.That App has to Work Similar to Generic Eclipse Simulator Iotivity Client Plugin to Initiate GET,PUT with Different Payloads, POST, OBSERVE Queries. If any of you find Sample Iotivity Android Client App or Web Interface please suggest 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/20161213/d2fcf75e/attachment.html>
[dev] generic java support merged with master
I the work on the generic java bindings was **merged** with master yesterday: - https://jira.iotivity.org/browse/IOT-1089 - https://gerrit.iotivity.org/gerrit/#/c/14931/ This change moves around all of the java related code. Since there is a java implementation for almost every part of the IoTivity project this change will likely affect every project at least a little. Currently we are not trying to build the generic Java on any platform other than Linux and Android. We tried to keep code changes to a minimum, but the structural changes are quite significant. Directory organization changes: `android` --> `java` `android/android_api/jni` --> `java/jni` `android/android_api/src` --> `java/common/src` --> `java/iotivity-android/src` --> `java/iotivity-linux/src` `android/examples` --> `java/examples-android` New directory: `java/examples-java` Other changes: The jni code is no longer built using Android.mk build files. It is built using scons. Due to the folder reorganization there are changes to multiple build scripts to address the new folder paths. To build the generic-java code: For Android: No change. It builds using the same build instructions as before. For Linux: 1. Specify JAVA_HOME environment variable with the path to the JDK. (i.e. `export JAVA_HOME=/usr/lib/jvm/java-1.8.0/`) 2. `scons BUILD_JAVA=1` #add any additional build options or `autobuild.py linux_unsecured_with_java` or `autobuild.py linux_secured_with_java` Running Linux samples: (Samples currently only works with SECURED=0 build) export LD_LIBRARY_PATH=$(pwd)/out/linux/x86_64/debug/:$LD_LIBRARY_PATH for SimpleClient: java -cp java/examples-java/simpleclient/build/libs/simpleclient.jar:java/iotivity-linux/build/libs/iotivity-linux.jar org.iotivity.base.examples.SimpleClient for SimpleServer: java -cp java/examples-java/simpleserver/build/libs/simpleserver.jar:java/iotivity-linux/build/libs/iotivity-linux.jar org.iotivity.base.examples.SimpleServer Thanks the following people for all their work: Peter Eftime - for doing the initial work Larry Sachs - for all the time spent testing and re-testing the android code to make sure it continued to work as expected Rick Bell - for reviews and the final merge If you have any questions I will do my best to answer them. George -- next part -- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20161213/4692231f/attachment.html>
[dev] Provisioning Client Error
Dear Developers, I am working on provisioning client program to implement some extra functions. I made few changes inside the program. I am getting the below error when I initialize discovery. Can someone help with this? I am sure that no changes has been made inside the discoverAllDevices() function. Discovering Only Unowned Devices on Network.. 04:54.122 DEBUG: OIC_PM_UTILITY: IN PMDeviceDiscovery 04:54.122 INFO: OIC_RI_STACK: Entering OCDoResource 04:54.122 DEBUG: OIC_CA_CONN_MGR: CAGenerateToken 04:54.122 DEBUG: OIC_CA_PRTCL_MSG: token len:8, token: 04:54.122 DEBUG: OIC_CA_PRTCL_MSG: 76 5A 2E 63 33 9F C9 9A 04:54.122 INFO: OIC_RI_CLIENTCB: Adding client callback with token 04:54.122 INFO: OIC_RI_CLIENTCB: 76 5A 2E 63 33 9F C9 9A 04:54.122 INFO: OIC_RI_CLIENTCB: Added Callback for uri : /oic/sec/doxm?Owned=FALSE 04:54.122 DEBUG: OIC_RM_UTIL: IN 04:54.122 DEBUG: OIC_RM_UTIL: IN 04:54.122 ERROR: OIC_RM_UTIL: Invalid input:options 04:54.122 INFO: OIC_RM_UTIL: Route option is not present Segmentation fault (core dumped) Thanks, Karthikeyan Prakash, Software Engineer, -- next part -- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20161213/5d8bb3fb/attachment.html> -- next part -- A non-text attachment was scrubbed... Name: Screenshot from 2016-12-13 16-46-40.png Type: image/png Size: 72562 bytes Desc: not available URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20161213/5d8bb3fb/attachment.png>
[dev] ESP 8266 Support in IoTivity
shnu Bemre wrote: > > hi Philippe Coval, > > Thanks. I will try to spend time on this. > > > Great ! I can try to help if you're facing wall > > > > I could see the code but unable to download it. > > > Do you see the "download" menu on right of > https://gerrit.iotivity.org/gerrit/#/c/13315/ > > There you can download the code on the right base : > https://gerrit.iotivity.org/gerrit/changes/13315/revisions/ > 7ec9b1f3ea5461e92da8a7f0e8c537979034eab1/archive?format=txz > > > > > Do I need any special permission for this? > > > > you just need a linuxfoundation account to log it, it's free ! > > > > > > -- > > -- > https://wiki.tizen.org/wiki/User:Pcoval > > > > ::DISCLAIMER:: > > > > > The contents of this e-mail and any attachment(s) are confidential and > intended for the named recipient(s) only. > E-mail transmission is not guaranteed to be secure or error-free as > information could be intercepted, corrupted, > lost, destroyed, arrive late or incomplete, or may contain viruses in > transmission. The e mail and its contents > (with or without referred errors) shall therefore not attach any liability > on the originator or HCL or its affiliates. > Views or opinions, if any, presented in this email are solely those of the > author and may not necessarily reflect the > views or opinions of HCL or its affiliates. Any form of reproduction, > dissemination, copying, disclosure, modification, > distribution and / or publication of this message without the prior > written consent of authorized representative of > HCL is strictly prohibited. If you have received this email in error > please delete it and notify the sender immediately. > Before opening any email and/or attachments, please check them for viruses > and other defects. > > > > > > > ___ > iotivity-dev mailing list > iotivity-dev at lists.iotivity.org > https://lists.iotivity.org/mailman/listinfo/iotivity-dev > > > > ___ > 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/20161213/42c982f4/attachment.html>
[dev] IoTivity simulator release aligning to IoTivity v.1.2.1
Hi All, Simulator with IoTivity 1.2.1 library has been release. If you have installed simulator thru https://mirrors.kernel.org/iotivity/tools/simulator/latest/, you can get the update. Otherwise, need to reinstall, please check it https://wiki.iotivity.org/iotivity_tool_guide. I appreciate Senthil G.S your contribution for simulator work. BR, Uze Choi -- next part -- HTML ?? ??... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20161213/2afe5915/attachment.html>
