The way I have managed to work around this trouble is to run the configure script with right cross compilation variables so that a config.h matching my Android system gets built and then writing Android.mk files which would simply use the Android build system. So how does one build an open source library for Android? Solution:
#Android ndk r9d for android#
Thus config.h would probably differ if it is somehow generated for Android with the one generated on a build system. Simply copying a config.h file from a run of configure script on another build system wouldn’t really work as the header files and other libraries present on Android may not match with the header and libraries present on the build system. #ifdef HAVE_CONFIG_H #include “config.h” #endif One cannot simply generate Android.mk files using autotools.įourth, even if one gets to write Android specific Makefiles, the build would most probably fail as during the build it would look for a file config.h included in the fashion shown below, while no such file would exist as it is generated by the configure script. Thus there is a gap that while your autotools would generate the Makefiles while Android build system requires its own styled Makefiles in the form of Android.mk.
#Android ndk r9d code#
This is provided so that people can build their code easily without having to deal with usual cross compiling issues. Third, in case of Android, it provides its own build system which are essentially some Makefile definitions and rules. Second, the build system for most cross compiler tools have their own quirks which need passing some extra flags.
In cross compiling scenario some of these probe should be done on the target system and not on the build system. By build time probe I mean checking for things like if a header, library or a tool is present or not. The first problem is that the Autools generate some configuration headers based on build time probe of the system. Most Open Source libraries use GNU autotools and its friends for building. #else Provide some other mechanism or report error to user or do whatever you want #endif The problem? #ifdef HAVE_XXXX Call some function which is declared in the header The code uses the generated config.h in the following fashion: #ifdef HAVE_XXXX #include #endif …. > generates -> config.hĪlso Makefile.am –> input to automake –> generates –> Makefile.in –> input to –> configure script –> generates Makefile configure.ac -> input to –> autoreconf –> generates -> configure script –> checks host system for headers, libraries etc.
and generates a config.h which contains definitions like #define HAVE_XXX 1 and also generates Makefiles after reading in the Makefile.in files which in turn is generated using Automake by reading in Makefile.am. Configure script test the build system for headers, libraries etc. You write a configure.ac file, which is read in by Autoreconf and generates a configure script. The way autootool and friends work is this: Having scrambled through a NDK documentation and a lot of hit and trials and experimentation, finally I could figure out how could one build (even though partially) Open Source libraries with Android NDK.
0 kommentar(er)
