11

I have a large C/C++ library that I need to use as part of an Android NDK project. This library needs to be able to intelligently process UTF8 strings (for example, conversion to lowercase/uppercase).

The library has conditional compilation to punt to an OS API to do the conversion, but there don't seem to be any Android APIs for UTF8. (mbstowcs, etc)

This thread says to use JNI methods to do it (!), which is a rather heavy-weight solution.

I was thinking about building ICU, but as it uses GNU Autotools I'm not sure I can make it work with the NDK toolchain. :/

Has anyone else confronted this problem and done something other than use JNI?

EDIT: My attempts to get ICU to compile fail at the configure step:

checking wchar.h usability... no
checking wchar.h presence... yes
configure: WARNING: wchar.h: present but cannot be compiled
configure: WARNING: wchar.h:     check for missing prerequisite headers?
configure: WARNING: wchar.h: see the Autoconf documentation
configure: WARNING: wchar.h:     section "Present But Cannot Be Compiled"
configure: WARNING: wchar.h: proceeding with the preprocessor's result
configure: WARNING: wchar.h: in the future, the compiler will take precedence
checking for wchar.h... yes
checking for library containing wcscpy... none required
checking size of wchar_t... 0
configure: error: There is wchar.h but the size of wchar_t is 0
Steven R. Loomis
  • 4,228
  • 28
  • 39
paleozogt
  • 6,393
  • 11
  • 51
  • 94

1 Answers1

11

We are using ICU in the NDK. Follow the steps in the ICU cross building instructions and you'll be OK. Basically you'll have a ICU native directory (for example Windows or Linux), a ICU Cygwin (if using such) and yet another for ICU Android (ARM). Sounds crazy, but it works!

Here are the steps for building under Cygwin. I am using the 'CrystaX' NDK r4, but it should build with the out of the box NDK as well. ICU version 4.4, but has worked with previous versions as well.

  1. Patches:

  2. Build your host version of ICU (e.g. Windows) as per normal. (We'll call this $HOST_ICU)

  3. Build Cygwin ICU:

    • Create a icu-cygwin directory (We'll call this $ICU_CROSS_BUILD)
    • From icu-cygwin dir, run '$HOST_ICU/source/runConfigureICU Cygwin'
    • make

  4. Build NDK version of ICU:

    • Create a icu-android directory
    • From icu-android dir: '$HOST_ICU/source/configure' with appropriate command line options. --with-cross-build=$ICU_CROSS_BUILD and --host=arm-eabi is required.
    • make

I use something like this for passed in (to step #4) CPPFLAGS/CXXFLAGS/CFLAGS:

-I$NDK_ROOT/build/platforms/android-8/arch-arm/usr/include/ -O3 -fno-short-wchar -DU_USING_ICU_NAMESPACE=0 -DU_GNUC_UTF16_STRING=0 -fno-short-enums -nostdlib

And for LDFLAGS:

-lc -Wl,-rpath-link=$NDK_ROOT/build/platforms/android-8/arch-arm/usr/lib/ -L$NDK_ROOT/build/platforms/android-8/arch-arm/usr/lib/

And additional configure params:

--enable-extras=no --enable-strict=no --enable-static --enable-shared=no --enable-tests=no --enable-samples=no --enable-dyload=no --enable-tools=no --host=arm-eabi --with-data-packaging=archive

I haven't done this manually for a while, it's currently all in a custom Python based build script. If you run into any other troubles, I can probably tell you what the issue is.

Good luck!

paleozogt
  • 6,393
  • 11
  • 51
  • 94
NuSkooler
  • 5,391
  • 1
  • 34
  • 58
  • I edited the question to show what happens when i try to build ICU with the NDK. – paleozogt Oct 17 '10 at 14:16
  • interesting patches, you should think about filing a ticket with them to contribute them – Steven R. Loomis Oct 20 '10 at 05:02
  • I certainly will. My real hope is that the Android devs decide to just expose a full pre-installed ICU since it's used on the devices already. – NuSkooler Oct 21 '10 at 01:38
  • 1
    No updates yet, but it still works even with newer versions of the NDK or ICU. I have been holding off on submitting anything to ICU yet as they have been changing their build system quite a bit to make stuff like this easier. In the near future I plan on upgrading some projects to the latest ICU and will try to implement something a bit cleaner and submit it. – NuSkooler Feb 07 '12 at 17:17
  • @NuSkooler Are the patches still necessary? – tofutim Feb 09 '12 at 15:56
  • The patches are still required in 4.6 as far as I remember. In 4.8+ is where things start to change and may not require them or need something else all together. My next update will probably be at 4.8 or 4.9 but I'm not there yet so I can't say for sure. – NuSkooler Feb 09 '12 at 16:45
  • At 4.8.1.1 right now. Looks like I need to make at least some patches so that I can have "enable-tools=no". – tofutim Feb 09 '12 at 16:58
  • checking for arm-eabi-gcc... no – tofutim Feb 09 '12 at 17:01
  • NuSkooler, any tips on getting the right compiler for Android? – tofutim Feb 09 '12 at 17:41
  • In the $NDK_ROOT toolchains directory, I see ar-linux-androideabi-4.4.3 - should I be using that? – tofutim Feb 09 '12 at 17:43
  • I tried to do this.. i downloaded `icu4c-49_1_2-src.tgz` gzipped tar archive for Unix and other platforms. I compiled for Linux (HOST) as per this answer make make install worked. Since I was not on windows I skipped the Cygwin Portion and I went to build NDK version of ICU but i did not get anything for host So i did `../configure --host=arm-linux` After which I still fail to understand where to find the ICU.so for Android? – Nathan Jul 31 '12 at 08:33
  • Seems like `--enable-tools=no` is no longer available with 51.1 :( – abergmeier Apr 21 '13 at 10:36
  • @abergmeier were you ever able to get it to compile with 51.1 or 51.2? I've been trying with no success: http://stackoverflow.com/q/18235428/560722 – Shlomo Zalman Heigh Aug 19 '13 at 15:44
  • Sadly no - the build system is pretty messy. Might try again in the future. – abergmeier Aug 19 '13 at 18:16
  • 1
    @tofutim just committed this patch, finally. It will be in ICU 52. http://bugs.icu-project.org/trac/ticket/9211 – Steven R. Loomis Aug 30 '13 at 20:48