I emailed the list before concerning a compile error that occurred in the srclib directory when cross-compiling the areadlink.c module for an Android ARM V7 platform. But I discovered that the static library libiconv.a built successfully in the lib/.libs directory. I’m not sure what the srclib and src subdirectories are for (both these subdirectories fail to build) but since I have the library (libiconv.a) that I need is it OK to use this library as it is in my applications? It looks like the src and srclib produce some executables since both these directories contain modules with a main() function in them. So I’m wondering if I can go ahead and remove the src and srclib subdirectories from the top-level Makefile.in, and configure, make, make install that way?
Dominique Van Rafelghem