Review Request: Allow user Java/C++ interaction

[BogDan Vatra]

> On April 4, 2012, 6:39 p.m., BogDan Vatra wrote:
> > Please run the tests (android/runtests.pl) after your do the changes.
> >
> 
> Tyler Mandry wrote:
>     I tried running the tests, but quadruplor seems to be outdated, i.e. not even meant to work with alpha3. Maybe I'm wrong. But the plugin (libandroid-9.so) is registering native functions for classes that exist in the JAR but don't exist in quadruplor (which doesn't use the JAR at all.) Specifically, QtNativeInputConnection. This causes dalvik to abort the process.
>     
>     Does quadruplor need to be updated somehow? IMHO, it looks like it's going to be difficult to maintain in its current state. I updated it (and runtests.pl) to play nice with my changes to the plugin, but as for this problem I just described, I'm not sure what you want to do.

Strange ... I just use it a few days ago, plase make sure you are using alpha4 branch! If the problem still exists please send me the logs. 


- BogDan


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/104450/#review12173
-----------------------------------------------------------


On April 7, 2012, 7:38 a.m., Tyler Mandry wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> http://git.reviewboard.kde.org/r/104450/
> -----------------------------------------------------------
> 
> (Updated April 7, 2012, 7:38 a.m.)
> 
> 
> Review request for Necessitas and BogDan Vatra.
> 
> 
> Description
> -------
> 
> Allows interaction between user Java and user C/C++ (JNI) code, by loading the user's code in the main class loader.
> SF.net bug: 140
> 
> Details
> -------
> This removes everything in src/android/cpp. qtmain_android.cpp is no more and is now integrated into src/plugins/platforms/android/src/androidjnimain.cpp. It seemed fitting to integrate startQtApp() into the same file as pauseQtApp() and resumeQtApp(). (Additionally this removes redundant copied code, and simplifies how necessitas projects work and are built.)
> 
> Compatibility
> -------------
> New library should be fully compatible with apps *already built* with old versions (before this change.) To build against the new library, existing projects simply need to update their QtActivity.java file.
> 
> Other
> -----
> This doesn't support using JNI with bundled libs. We have to be careful to load certain bundled libs (maybe only the plugin .so) in the delegate class loader, so I could break certain apps by making such a switch. Need a way to categorize the type of bundled lib, in order to decide which class loader to use.
> 
> 
> Diffs
> -----
> 
>   android/quadruplor/src/org/kde/necessitas/industrius/QtActivity.java 4ecf3c8 
>   android/quadruplor/src/org/kde/necessitas/industrius/QtNative.java 3e82ce6 
>   android/runtests.pl 2e438fd 
>   mkspecs/android-g++/qmake.conf 5904ea1 
>   mkspecs/features/qt.prf a254437 
>   src/android/cpp/qtmain_android.cpp e5f5fc8 
>   src/android/jar/src/org/kde/necessitas/industrius/QtActivityDelegate.java 85add90 
>   src/android/jar/src/org/kde/necessitas/industrius/QtNative.java 24ebb5b 
>   src/android/java/src/org/kde/necessitas/origo/QtActivity.java fcbccef 
>   src/plugins/platforms/android/src/androidjnimain.cpp c8a5001 
> 
> Diff: http://git.reviewboard.kde.org/r/104450/diff/
> 
> 
> Testing
> -------
> 
> Tested on a Galaxy Nexus and a Nexus One.
> New libraries run both old and new apps.
> New libraries support JNI interaction.
> 
> 
> Thanks,
> 
> Tyler Mandry
> 
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/necessitas-devel/attachments/20120409/c5491868/attachment.html>