I have the same issue Using libc++_shared.so in the NDK results in the symbols looking for std::__ndk1 whereas linking to a HAL implementation ends up searching for std::__1
thus preventing the linker from finding the symbols Any way around this? On Wednesday, November 21, 2018 at 5:55:08 PM UTC-8, Dan Cape wrote: > > I have a library that was built with cmake using the NDK libc++_shared. I > want to use that library in a HAL that I'm working on. From what I have > seen, android sees some of its functions as incompatible due to one being > built by the NDK and the HAL being being built with the AOSP libc++. Some > function definitions don't line up. One is prefixed by std::__1 and the > other has std::__ndk1. Is there some way to reconcile this? > > Thanks > -- -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting --- You received this message because you are subscribed to the Google Groups "android-porting" group. To unsubscribe from this group and stop receiving emails from it, send an email to android-porting+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/android-porting/b5f92cf1-7b54-41e4-9c9f-a4d23a972408%40googlegroups.com.
