Hi All, I have a use-case library having *.cpp files. And i made an application with *.c extension. I included the above said library as a shared library part of the Android.mk for building the application.
I am getting errors showing undefined reference to API's of use-case library that i used part of the application. But if i convert the application *.c to *.cpp with some additional effort of makiing changes fo avoid some typecasting errors .With this I dont get the undefined reference errors and my application builds. One more good example: I am integrating some user library "libmyusecase" for video post-processing. This library has source files with *.c extenstions. I have used the API's of this library in external\opencore\android\android_surface_output.cpp part of static library libandroidpv I have accordingly modified Android.mk of module libandroidpv to include the added library as part of LOCAL_SHARED_LIBRARIES := libmedia libvorbisidec libicuuc libmyusecase I compile libandroidpv which is a static library. No problem. When i compile module libopencore_player which includes the above said libandroidpv , i get errors indicating undefined reference of all the API's of libmyusecase which were added into the source code of android_surface_output.cpp. Please let me know if anybody has some idea why i get this undefined reference errors when i use an application with *.c having API's used from a library having *.cpp files. Do i need to always change the *.c to *.cpp or vice-versa based on the packages. And this is taking additional effort of resolving some type-casting errors which i observed so far. Thanks and regards, Sreedhar --~--~---------~--~----~------------~-------~--~----~ unsubscribe: [email protected] website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
