Native Development Kit for Android
We offer CrystaX NDK - a widely used, open-source product that has been used by numerous commercial and open-source projects for years. Why not use Google's Android NDK? Because CrystaX NDK is better than Google's while remaining compatible. Basically, CrystaX NDK is a drop-in replacement for Google's NDK, allowing developers to use it in the same manner as Google's NDK but offering many added features and improvements.
Following are the main goals of CrystaX NDK:
- Better standard compatibility
- Easy porting of existing code to Android
- New features for Android native development
Look interesting? See in more detail what CrystaX NDK offers Android developers!
In the previous article, we described how to build a simple Android executable, which uses Boost C++ libraries. This is good example to see how the process works and to understand the internals; however, for practical purposes we need to know how to build ready-to-use Android applications which can be submitted to Google Play Store, for example.Read more
Do you have code that uses Boost C++ libraries? Do you want to easily port this code to Android? Or maybe you just want start a new Android-targeted project and would like to use Boost from the beginning? With CrystaX NDK 10.1.0, you get both an Android native development kit and Boost C++ libraries out of the box!Read more
By definition, good applications must look good for users. Besides many other things, that means good applications must talk with users in their language. But just translation of words and phrases to another language is not enough - many other elements differs from one culture to another, including the format of dates, money values, rules for capitalization, etc. All such specific information in computing defined through locales.
The way locale-specific input and output should be handled is standardized by ISO C and ISO C++ standards, so usually it's enough to just follow standards to properly localize your application. Unfortunately, this approach doesn't work on Android for software written in C/C++. Android libc (Bionic) has no native support for locales, so the only way to use localized input/output in native code is to implement localization in Java and refer to it through JNI. Obviously, such an approach adds significant run-time overhead, but it's the only choice if you're using Google's Android NDK.Read more
We're glad to announce the release of CrystaX NDK 10.1.0! In this release, you can find several great features and improvements, such as better standards compatibility, etc.Read more