Android studio ndk error

Android Studio NDK built has mixed end error results during build and apk execution #543

Comments

cmeng-git commented Oct 13, 2017 •

Description

Android Studio NDK built has mixed end error results during build and apk execution

I am using Windows 7 64-bit system and Ubuntu 16.04 64-bit system, both installed with Android Studio 2.3.3 and android-sdk/ndk version 15.2.4303891 (see below for details)

Most of time, I am using Windows 7 environment for android application development i.e. aTalk-android.
aTalk-android uses either JNI share libraries built from source or pre-built static libraries downloaded from online if available. The aTalk is using couples of native JNI build libraries including
a. libvpx — Standalone-chaintool on ubuntu (1.6.1+ i.e. master repository dated 10/12/2017)
b. opus — AS with NDK from source (v1.2.1)
c. openssl — standalone-chaintool on ubuntu (sourc -v1.0.2l) and pre-built static library (v1.0.2k online)
d. speex — AS with NDK from source (v1.2rc1)

Both opus and libvpx seem to be independent of the problems experienced as reported below.
The observed problem for

openssl:

Using tool downloaded from https://github.com/leenjewel/openssl_for_ios_and_android
and source 1.0.2l from https://www.opus-codec.org/downloads
using standalone-chain running on ubuntu 16.04
I found that I have to set APP_PLATFORM = android-23 to build; otherwise facing problem with many undefined symbols e.g. stderr, stdin, stdout, atof, signal, tcsetattr , tcgetattr etc with api

The text was updated successfully, but these errors were encountered:

DanAlbert commented Oct 13, 2017

cmeng-git commented Oct 13, 2017

Many thanks for the link and the information. I have checked my configuration setting against your provided link. Yes it did explain the problem for speex but not for other problems that I have encountered.

As for the openssl static library built using standalone toolchain on ubuntu, I just cannot set api

enh commented Oct 13, 2017

Here’s how stdin/stdout/stderr work on Android:

so if you build >= M you’ll get references to stdin/stdout/stderr. if you build = has both stdin/stdout/stderr and __sF.

btw, openssl is a real bastard to build. libressl builds out of the box.

i’ll try speex later today, but i have to run to the dentist now 🙂

enh commented Oct 13, 2017

speex 1.2.0 builds out of the box for me for API level 15.

cmeng-git commented Oct 13, 2017

Many thanks to all for the information to enlightened me on the NDK built. Actually I have already spent more than 3 weeks struggling to get info online and built JNI shared libraries with various API settings. The information provided are really helpful.

Below are the latest test results on aTalk-android.

libvpx (v1.6.1+/master)

Able to build static library with API-15 using standalone toolchain running on Ubuntu

speex (v1.2rc1)

NDK build within Android Studio with API-15 is OK

openssl (1.0.2l) — aTalk openssl java wrapper is only compatible with v1.0.2x

Build static library with API-15 using standalone toolchain running on Ubuntu failed with following linkage errors (only with API >=23 is ok):

Using v1.0.2k pre-built static libraries releases (https://github.com/ahnan4arch/OpenSSL-for-Android-Prebuilt-1) failed to build the shared library linking in java wrapper on AS when API-15 is used.

I have to set AS NDK to API-21 in order to get it to build the shared library without error. Look likes the online openssl static library v.1.0.2k may had built with API-21.

Conclusion

Wtih the NDK built for openssl support disabled on aTalk apk build; and using libvpx and speex shared/static libraries built with API-15, both the codec’s i.e. speex and vpx are tested working on both the Note 3 and Samsung SII (- previously not working when build with api-21) .

In order to get openssl support on aTalk, I really need to build the static library from source on ubuntu with API-15.

enh,
Thanks for the explanation. my understanding from your previous comment is that it explains on how android internally handle case for some of the stadlib references etc. There is no actual solution given for the undefined symbols for openssl static library built with API-15.

Appreciate if you or someone is able to offer some solution to build openssl static library with API-15.

cmeng-git commented Oct 19, 2017

Finally resolved all the problems and got the openssl source to compile and build the shared library with NDK under Android Studio 2.3 environment and with API-15

a. With the source downloaded from the following link:
https://github.com/aosp-mirror/platform_external_openssl/tree/android-5.1.1_r38
b. unzip the source into AS project sub-directory jni
c. Modified all the .mk files so it builds the static libraries for libcrypto.a and libssl.a
I also merged the various -32.mk/-64.mk files of the same into one file for easy future maintenance.
d. Build shared library with the java API wrapper together with the two static *.a libraries.

However I have to perform the build with Android Studio 2.3 running under ubuntu 16.04. When build under Windows 7, I faced the following problem:
NDK builds libssl.a without problem. However it throws the following error when linking libcrypto.a i.e. Error 87. I believe it is the NDK argument list too long when run under Windows 7.

So I add the option to crypto.mk i.e.
LOCAL_SHORT_COMMANDS := true
However after 1 hours of building, it throws error. Actually the OPENSSLDIR is defined in jni/android.mk as OPENSSL_DIR := openssl.

When build under Ubuntu, I do not have to set the option LOCAL_SHORT_COMMANDS := true and the build took only

Look like I may have to switch my android studio development environment to run under ubuntu.

Источник

Install and configure the NDK and CMake

To compile and debug native code for your app, you need the following components:

• The Android Native Development Kit (NDK): a set of tools that allows you to use C and C++ code with Android.
• CMake: an external build tool that works alongside Gradle to build your native library. You do not need this component if you only plan to use ndk-build.
• LLDB: the debugger Android Studio uses to debug native code. By default, LLDB will be installed alongside Android Studio.

This page describes how to install these components automatically, or by using Android Studio or the sdkmanager tool to download and install them manually.

Install NDK and CMake automatically

Android Gradle Plugin 4.2.0+ can automatically install the required NDK and CMake the first time you build your project if their licenses have been accepted in advance. If you’ve already read and agree to the license terms, then you can pre-accept the licenses in scripts with the following command:

Install the NDK and CMake

When you install the NDK, Android Studio selects the latest available NDK. For most projects, installing this default version of the NDK is sufficient. If your project needs one or more specific versions of the NDK, though, you can download and configure specific versions. Doing so helps you ensure reproducible builds across projects that each depend on a specific version of the NDK. Android Studio installs all versions of the NDK in the android-sdk /ndk/ directory.

To install CMake and the default NDK in Android Studio, do the following:

With a project open, click Tools > SDK Manager.

Click the SDK Tools tab.

Select the NDK (Side by side) and CMake checkboxes.

Figure 1: The SDK Tools window showing the NDK (Side by side) option

Click OK.

A dialog box tells you how much space the NDK package consumes on disk.

Click OK.

When the installation is complete, click Finish.

Your project automatically syncs the build file and performs a build. Resolve any errors that occur.

Configure a specific version of CMake

The SDK Manager includes the 3.6.0 forked version of CMake and version 3.10.2. Projects that don’t set a specific CMake version are built with CMake 3.10.2. To set the CMake version, add the following to your module’s build.gradle file:

Groovy

Kotlin

If you want to use a CMake version that is not included by the SDK Manager, follow these steps:

1. Download and install CMake from the official CMake website.
2. Specify the CMake version you want Gradle to use in your module’s build.gradle file.

Either add the path to the CMake installation to your PATH environment variable or include it in your project’s local.properties file, as shown. If Gradle is unable to find the version of CMake you specified in your build.gradle file, you get a build error.

If you don’t already have the Ninja build system installed on your workstation, go to the official Ninja website, and download and install the latest version of Ninja available for your OS. Make sure to also add the path to the Ninja installation to your PATH environment variable.

Install a specific version of the NDK

To install a specific version of the NDK, do the following:

With a project open, click Tools > SDK Manager.

Click the SDK Tools tab.

Select the Show Package Details checkbox.

Select the NDK (Side by side) checkbox and the checkboxes below it that correspond to the NDK versions you want to install. Android Studio installs all versions of the NDK in the android-sdk /ndk/ directory.

Figure 2: The SDK Tools window showing the NDK (Side by side) options

Click OK.

A dialog box tells you how much space the NDK package(s) consumes.

Click OK.

When the installation is complete, click Finish.

Your project automatically syncs the build file and performs a build. Resolve any errors that occur.

Configure each module with the version of the NDK you want it to use. When using Android Studio 3.6 or higher, if you do not specify the version, the Android Gradle plugin chooses a version that it is known to be compatible with.

Configure specific versions of the NDK in your project

You may need to configure the version of the NDK in your project if one of the following is true:

Your project is inherited and you need to use specific versions of the NDK and the Android Gradle plugin (AGP). For more information, see Configure the NDK for the Android Gradle plugin.

You have multiple versions of the NDK installed and you want to use a specific one. In this case, specify the version using the android.ndkVersion property in the module’s build.gradle file, as shown in the following code sample.

Groovy

Kotlin

Default NDK version per AGP version

Before release, each AGP version is thoroughly tested with the latest stable NDK release at that time. For AGP version 3.6 and above, that NDK version will be used to build your projects if you do NOT specify an NDK version in the build.gradle file. The default NDK version is documented inside the AGP release notes. The current default NDK versions are listed in the following table:

Android Studio/Gradle Plugin Version
7.0	4.2	4.1	4.0	3.6	3.5	3.4
Default NDK version specified for the version of AGP	21.4.7075529	21.4.7075529	21.1.6352462	21.0.6113669	20.0.5594570	No default specified

Content and code samples on this page are subject to the licenses described in the Content License. Java is a registered trademark of Oracle and/or its affiliates.

Источник

NDK is not configured issue in android studio

My Application is built successfully on Eclipse but fails to Build on android studio. It returns the error code Ndk is not Configured. Then I’ve added ndk path to build.gradle then its showing the following error:

Answers

This is the problem faced by Android studio users in Windows environment. First for NDK not Configured problem

Go to local.properties file and give ndk path. for ex :

Then for the Next Problem or Error.

Goto JNI Folder and create an empty c file by any name. Then your problem will be solved.

Some Quick links about this are http://ph0b.com/android-studio-gradle-and-ndk-integration/ And https://code.google.com/p/android/issues/detail?id=66937

One

Copy yours *.SO libraries on your libs folder and put that on Build.gradle :

Two

Make a new folder on src/main/jniLibs and write that on your Build.gradle :

There

Make a new folder on src/main/jniLibs and write that on your Build.gradle :

You need to setup OpenCV librairies for your project. You can follow the instruction here.

This issue is fixed by removing the android:defaultValue tag.

Then Rebuild Project after making changes.

Here Is Your Solution :

transient is a variables modifier used in serialization. At the time of serialization, if we don’t want to save value of a particular variable in a file, then we use transient keyword. When JVM comes across transient keyword, it ignores original value of the variable and save default value of that variable data type.

So, it uses quite rare in order to say to your compiler that this variable is not a part of serializable mathod.

Источник