Android ndk R7 installation and Problems

The ndk R7 was released a few days ago. I'm so excited that it can be used directly after the download ..

PS: Don't look at some of the descriptions in the ndk. Some of the descriptions are too old, not that you didn't find them, but that something is gone. R7 can be used directly after being downloaded, without the need to install

Whether it is an open-source or commercial app, I think that if ndk can be used wherever possible, at least so file disassembly is not what the average person can do. If commercial apps leave performance problems behind, interface encryption is not a problem. At least I like so files. I hope that the app will be noticed that it is not a good thing to decompile the APK. The APK should be mixed during export. When mixing packets, note that the reflection should not be mixed. Otherwise, it will be a tragedy.

PS; although I did not understand the work, I still had to study the technology. I continued to study the decompilation. After studying it for a whole morning, I basically got it done. The result is that I will add the code to CPP and let you decompile it.

Decompress the package directly after the download. Env detection after Configuration

Thinkinbunny @ Rene :~ $ Ndk-build
/Home/thinkinbunny/android-ndk-r7/prebuilt/linux-x86/bin/awk: 1: Elf: not found
/Home/thinkinbunny/android-ndk-r7/prebuilt/linux-x86/bin/awk: 4: syntax error: Word unexpected (expecting ")")
Android ndk: Host 'awk' tool is outdated. Please define host_awk to point to gawk or nawk!
/Home/thinkinbunny/android-ndk-r7/build/CORE/init. mk: 258: *** Android ndk: aborting .. Stop.

Tragedy: ndk-build cannot be used. Then the problem continues. After ccache is installed, we will continue to study the problem. The awk computer is also the latest. It is strange that the awk prompts you to fix the problem.

Well, it is said that it is a face in/pre-build. just delete it directly. The old awk should be deleted and the ndk will call the system, after several days, the problem finally came to an end.

Thinkinbunny @ Rene :~ // Android-ndk-r7/samples $ CD hello-neon/
Thinkinbunny @ Rene :~ /Android-ndk-r7/samples/Hello-neon $ ls
Androidmanifest. xml build. properties default. properties JNI res SRC
Thinkinbunny @ Rene :~ /Android-ndk-r7/samples/Hello-neon $ ndk-build
Compile thumb: helloneon <= helloneon. c
Compile thumb: cpufeatures <= cpu-features.c
Staticlibrary: libcpufeatures.
Sharedlibrary: libhelloneon. So
Install: libhelloneon. So => libs/armeabi/libhelloneon. So
Compile thumb: helloneon <= helloneon. c
Compile thumb: helloneon <= helloneon-intrinsics.c
Compile thumb: cpufeatures <= cpu-features.c
Staticlibrary: libcpufeatures.
Sharedlibrary: libhelloneon. So
Install: libhelloneon. So => libs/armeabi-v7a/libhelloneon. So
Thinkinbunny @ Rene :~ /Android-ndk-r7/samples/Hello-neon $

Excellent.

The reason may be: I just received an email from Google groups. foreign friends said that the awk in prebuild is 64-bit. In short, it is still a version problem. I don't know what the situation is in windows, I have not studied it. It seems that I have been busy with my work recently. who has studied it? Otherwise, I will study it in a few days.