New JNI bindings

jni/Android.mk

Index: jni/Android.mk
diff --git a/jni/Android.mk b/jni/Android.mk
index 9d7f4f3cd7b1117f9f396d1e4c232f390e0a8577..a82437f0a8a606c0305827439998382b7c166493 100755
--- a/jni/Android.mk
+++ b/jni/Android.mk
@@ -25,6 +25,10 @@ include $(CLEAR_VARS)
 
 LOCAL_MODULE := abpEngine

[Felix Dahlke, 2014/03/28 17:36:23]

Me being pedantic, but I don't think "abpEngine" makes a lot of sense once we
got rid of AbpEngine.cpp et. al.

Let's keep it like this for now, but doesn't hurt to think of a suitable name. I
was thinking of something along the lines of "libadblockplusWrappers", but I'm
not sure if that's any good. What do you think?

[René Jeschke, 2014/03/31 09:10:38]

I think we should just call it 'libadblockplus' as this is exactly what it is
for Android/Java IMO (even if the wrapping part is quite heavy here).

[Felix Dahlke, 2014/03/31 10:43:23]

Trouble is, we actually have a module called "libadblockplus" (the actual
libadblockplus), see above. The code in the abpEngine module is really just
(going to be) the wrappers.

[René Jeschke, 2014/04/11 12:25:53]

Done.

 LOCAL_SRC_FILES := AbpEngine.cpp Utils.cpp AndroidLogSystem.cpp AndroidWebRequest.cpp
+LOCAL_SRC_FILES += JniJsEngine.cpp JniFilterEngine.cpp JniJsValue.cpp JniFilter.cpp 
+LOCAL_SRC_FILES += JniSubscription.cpp JniEventCallback.cpp JniLogSystem.cpp 
+LOCAL_SRC_FILES += JniWebRequest.cpp JniUpdaterCallback.cpp JniFilterChangeCallback.cpp
+LOCAL_SRC_FILES += JniCallbacks.cpp
 
 LOCAL_CPP_FEATURES := rtti exceptions
 LOCAL_CFLAGS += -std=gnu++0x