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:[email protected]] Sent: Tuesday, December 13, 2016 3:06 PM To: Nash, George <george.nash at intel.com> 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 <george.nash at intel.com<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>
