I think for the different Linux distributions it does not make sense to build it, as the developers there will probably write a C/C++ application and can built IoTivity by themselves. The ?normal? Android developer is mostly used to write Java applications in his IDE, there it would help a lot to have precompiled *.aar for the common architectures (x86, x86_64, arm, arm64) and the jar.
Later we could see if this is also needed for other operating systems, but doing this for the 1.1.1 final release should be pretty easy for the practical point, I haven?t looked at the legal side. Hauke From: Shivam Verma [mailto:[email protected]] Sent: Wednesday, July 20, 2016 9:53 AM To: Mats Wichmann <mats at osg.samsung.com> Cc: maxi wu <maxi.wu at u-media.com.tw>; iotivity-dev <iotivity-dev at lists.iotivity.org>; Mehrtens, Hauke <hauke.mehrtens at intel.com> Subject: Re: [dev] IoTivity binary release for Android Completely agree with you Mats. I just wanted to point out to Maxi that it's possible to have an IoTivitiy SDK. Different aars for different archs. -Shivam On Wed, Jul 20, 2016 at 3:48 PM, Mats Wichmann <mats at osg.samsung.com<mailto:mats at osg.samsung.com>> wrote: But you can't actually get those anywhere, can you? Anybody who wants them has to build from the code first. I'm not sure it currently makes sense to build "out of tree" but at some point that's got to become an objective, whether for IoTivity itself or for someone who repackages it (Linux distribution, for example)... to have an "sdk like" setup for building stuff. On 07/20/2016 04:22 PM, Shivam Verma wrote: > There's an aar file for the android apis that is generated after the build > process. > > It contains everything you need to write a client side application. > > -Shivam > > On Wed, Jul 20, 2016 at 3:10 PM, maxi wu <maxi.wu at > u-media.com.tw<mailto:maxi.wu at u-media.com.tw> <mailto:maxi.wu at > u-media.com.tw<mailto:maxi.wu at u-media.com.tw>>> wrote: > > I would like to have a .jar, but the current situation, I would say I > couldn?t see this coming any soon. > Because, the .jar is just a binding layer over C++ object files. Which > means it does nothing without those C++ files. > And those C++ files is built depending on ARCH, for example ARM. > > That means, the source code we have is not cross-platform. You need > different C++ object files for different platform. > > *From:*iotivity-dev-bounces at > lists.iotivity.org<mailto:iotivity-dev-bounces at lists.iotivity.org> > <mailto:iotivity-dev-bounces at > lists.iotivity.org<mailto:iotivity-dev-bounces at lists.iotivity.org>> > [mailto:iotivity-dev-bounces at > lists.iotivity.org<mailto:iotivity-dev-bounces at lists.iotivity.org> > <mailto:iotivity-dev-bounces at > lists.iotivity.org<mailto:iotivity-dev-bounces at lists.iotivity.org>>] *On > Behalf Of *Mehrtens, Hauke > *Sent:* Wednesday, July 20, 2016 1:15 AM > *To:* iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at > lists.iotivity.org> <mailto:iotivity-dev at > lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org>> > *Subject:* [dev] IoTivity binary release for Android > > It would be nice to have IoTivity binaries (the shared libs and the jar) > for Android. This way a normal Android developer who wants to do something > with IoTivity does not have to compile some C code, but can just use the > precompiled binaries and build an Android app around it. > I think having to use scons is a barrier for new developers and you can > build an Android app with just using Java if we would ship the android > binaries. > It would be nice to have this for the next release. > > *Hauke Mehrtens* > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160720/ddd3f32d/attachment.html>
