Hello Uze, As planned we pushed the merged Android API base layer for review and this patch is out for review. https://gerrit.iotivity.org/gerrit/834
As we previously mentioned you will need to make API changes to your services and applications to adapt to the API changes introduced by the push and the merge of the Stack from master. I would be great if you could make your changes and push for review on the Android API branch on your Monday and send us any questions that arise. If needed we can have a quick conference call on Monday evening PDT to resolve any lingering questions. Finally assuming that by Monday or Tuesday we have a complete Android Base and Service API on the android-api branch we can push to master for review at that point and abandon the Android-api branch. Hope this is all clear. BR Bernie On 4/23/15, 6:29 PM, "???(Uze Choi)" <uzchoi at samsung.com> wrote: >Hi Bernie, > >It looks Strange. Even few days ago, it worked well. >Anyway, it's a good news regarding fix within the next few days. > >BR, Uze Choi >-----Original Message----- >From: Keany, Bernie [mailto:bernie.keany at intel.com] >Sent: Friday, April 24, 2015 10:02 AM >To: uzchoi at samsung.com; Kourt, Tim A; ???; ???; ???; ???; ??? >Cc: ???; iotivity-dev at lists.iotivity.org; Lankswert, Patrick >Subject: Re: Android base issue on android-api branch > >Hi Uze, > >Sorry this isn?t working, it appears that a recent checkin approved by you >has caused this problem. > >Here is the link to the file that broke gradle build: >https://gerrit.iotivity.org/gerrit/#/c/570/3/SConstruct > >We?ve completed the integration of the CA changes for Android into the >Android Base API and are testing the merged code. >We plan to push the code to master for review tomorrow and as you?re aware >this means that you?ll need to modify your applications to accommodate the >new C++ signatures from the CA layer along with parameter that we?ve >introduced to handle exceptions. > >Assuming the integration of the applications and services goes smoothly >IoTivity will have full support for Android on Master for review early as >soon as the applications and services are modified. > >Hope this is clear and explains the build issue. > >BR >Bernie > >From: "Choi) ???(Uze" <uzchoi at samsung.com<mailto:uzchoi at samsung.com>> >Reply-To: "Choi) ???(Uze" <uzchoi at samsung.com<mailto:uzchoi at samsung.com>> >Date: Thursday, April 23, 2015 at 6:36 AM >To: "Kourt, Tim A" <tim.a.kourt at intel.com<mailto:tim.a.kourt at intel.com>>, >Bernie Keany <bernie.keany at intel.com<mailto:bernie.keany at intel.com>>, >"Choi) ???(Uze" <uzchoi at samsung.com<mailto:uzchoi at samsung.com>>, ??? ><rami.jung at samsung.com<mailto:rami.jung at samsung.com>>, ??? ><jihun.ha at samsung.com<mailto:jihun.ha at samsung.com>>, ??? ><hyunjun2.kim at samsung.com<mailto:hyunjun2.kim at samsung.com>>, ??? <minjii. >park at samsung.com<mailto:minjii.park at samsung.com>>, ??? ><yh_.joo at samsung.com<mailto:yh_.joo at samsung.com>> >Cc: ??? <jihyeok13.kim at samsung.com<mailto:jihyeok13.kim at samsung.com>>, >"iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org>" ><iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at >lists.iotivity.org>>, >"Lankswert, Patrick" ><patrick.lankswert at intel.com<mailto:patrick.lankswert at intel.com>> >Subject: Fwd: Android base issue on android-api branch > >Hi Bernie, >Please figure out the android api branch issue for our development. We are >all stuck on dev > > >---?? ???--- >??? : ??? >???? : 2015/04/23 21:41 (GMT+09:00) >?? : Android base issue on android-api branch > > >Dear Tim and Bernie > > > >Hello! I'm JK > > > >While we are trying to do QA process using android-api branch code, > >we found that liboc.so (base stack) is cracked that > >android app could not load liboc.so (also any examples failed to run) > > > >System.loadLibrary("oc_logger"); >System.loadLibrary("coap"); >System.loadLibrary("octbstack"); > >System.loadLibrary("oc"); <-- fail to load library, check below error log > > > >04-23 21:35:39.416: D/dalvikvm(23434): Added shared lib /data/app- >lib/org.iotivity.service.ssm-7/liboc_logger.so 0x42ee29c0 >04-23 21:35:39.416: D/dalvikvm(23434): No JNI_OnLoad found in /data/app- >lib/org.iotivity.service.ssm-7/liboc_logger.so 0x42ee29c0, skipping init >04-23 21:35:39.631: D/dalvikvm(23434): Trying to load lib >/data/app-lib/org. >iotivity.service.ssm-7/libcoap.so 0x42ee29c0 >04-23 21:35:39.631: D/dalvikvm(23434): Added shared lib /data/app- >lib/org.iotivity.service.ssm-7/libcoap.so 0x42ee29c0 >04-23 21:35:39.631: D/dalvikvm(23434): No JNI_OnLoad found in /data/app- >lib/org.iotivity.service.ssm-7/libcoap.so 0x42ee29c0, skipping init >04-23 21:35:40.026: D/dalvikvm(23434): Trying to load lib >/data/app-lib/org. >iotivity.service.ssm-7/liboctbstack.so 0x42ee29c0 >04-23 21:35:40.026: D/dalvikvm(23434): Added shared lib /data/app- >lib/org.iotivity.service.ssm-7/liboctbstack.so 0x42ee29c0 >04-23 21:35:40.026: D/dalvikvm(23434): No JNI_OnLoad found in /data/app- >lib/org.iotivity.service.ssm-7/liboctbstack.so 0x42ee29c0, skipping init >04-23 21:35:40.356: D/dalvikvm(23434): Trying to load lib >/data/app-lib/org. >iotivity.service.ssm-7/liboc.so 0x42ee29c0 >04-23 21:35:40.361: E/dalvikvm(23434): dlopen("/data/app- >lib/org.iotivity.service.ssm-7/liboc.so") failed: dlopen failed: cannot >locate symbol "_ZNKSt8__detail20_Prime_rehash_policy11_M_next_bktEj" >referenced by "liboc.so"... > > > >Could you check the branch ? > > > >We are behind schedule so need urgent help. > > > > > >Best Wishes > >JK > > > >| Jee Hyeok, Kim | IoT Solution Lab, SW Center | Mobile) +82-10-9168-3641 >| > > > > >[http://www.samsung.net/pt_images/C10/securityimage/MSI_20140516060336843. >gi >f] > > > >
