strongswan-ext

Files

T

Tobias Brunner f3695d089b android: Change how initial log handler is registered

Previously, if the two utility functions were called while the VPN
connection was established (i.e. charon was initialized) the logger for
libstrongswan would get reset to the initial log handler.  So certain
log messages would not get logged to the log file after the TUN device
was created (one of the helpers is used to convert IPs there).

2020-06-02 14:07:06 +02:00

app

android: Change how initial log handler is registered

2020-06-02 14:07:06 +02:00

gradle/wrapper

android: Update Gradle plugin

2020-06-02 13:57:37 +02:00

.gitignore

android: Ignore build/ in project directory

2016-04-27 14:24:25 +02:00

build.gradle

android: Update Gradle plugin

2020-06-02 13:57:37 +02:00

gradle.properties

android: Migrate from support libraries to AndroidX

2019-08-26 11:20:48 +02:00

gradlew

android: Migrate to the Gradle build system

2015-11-12 14:11:37 +01:00

gradlew.bat

android: Migrate to the Gradle build system

2015-11-12 14:11:37 +01:00

README.ndk

android: Update README.ndk

2016-05-02 16:41:50 +02:00

settings.gradle

android: Migrate to the Gradle build system

2015-11-12 14:11:37 +01:00

README.ndk

To build this within the NDK the following things have to be done:

 - By default the strongSwan sources of the current Git tree are used. They have
   to be prepared first (see HACKING for a list of required tools):

     ./autogen.sh && ./configure && make && make distclean

   It is also possible to use the sources from a different directory (e.g. an
   extracted tarball) by setting strongswan_DIR in app/src/main/jni/Android.mk.

 - The OpenSSL or BoringSSL sources are expected in app/src/main/jni/openssl.
   Since the sources need to be changed to be built on Android (and especially
   in the NDK) we provide a modified mirror of the official Android repositories
   on git.strongswan.org.