[Ves] Swig interface file used to generate Android Kiwi Wrappers

[Pat Marion]

Hi Dave,

The JNI functions in KiwiNative.cpp, which implements the KiwiNative.so JNI
library, were written by hand, not with SWIG.  The SWIG work is
experimental, you can find it on the swig branch of the stage remote:

git remote add stage git://vtk.org/stage/VES.git
git checkout swig

If you inspect the top commit of this branch, you'll see it adds a kiwi.i
file and a notes.txt file.  The notes.txt file explains how to generate
python and Java bindings, and how to run python and java examples.  All the
paths are hard coded for my machine, so you'll have to fix it for your
computer.  You might want to cherry-pick the commit onto your current
working branch rather than checkout the swig branch.

Pat




On Tue, Jun 25, 2013 at 12:58 PM, <DEB63 at pitt.edu> wrote:

> Hi
>
> During the webinar for Android app building with VES and Kiwi, it was
> mentioned that SWIG can be used to help automate the generation of the
> native code interface from Cpp to Android.    Was Swig used to generate
> the native interface for the Android KIWI viewer demo app?  If so, could
> you share the contents of the swig *.i interface file that was used to do
> this, as well as the SWIG build switches that were used to invoke swig?
>
> Thanks
>
> Dave Busch
>
>
> _______________________________________________
> Ves mailing list
> Ves at public.kitware.com
> http://public.kitware.com/cgi-bin/mailman/listinfo/ves
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/ves/attachments/20130625/f0a492d8/attachment-0001.html>