Just my observation. I was trying to use ogg in my project. Shared libvorbisfile uses static libogg. My final shared library uses libvorbisfile. For some reason it works on Galaxy S (Android 2.2) and doesn't on G1 (Android 1.6). So I had to merge libogg and libvorbisfile into one static library that is used by my shared library.
On 6 янв, 07:02, Dan <[email protected]> wrote: > I have a build setup that was ok with the r4 NDK, but STLPort and all > the other nifties of the r5 ndk tempted me to upgrade (despite the > "don't fix what ain't broke" rule.) > > The process builds a shared library, and it fails on r5 (where it > worked on r4) not finding a bunch of the symbols it should find. I > think I've tracked it down to LOCAL_SHARED_LIBRARIES not being > propagated as a dependency to the SharedLibrary .so creation, and was > wondering if the removal of the > > $(call module-add-shared-depends,$(LOCAL_MODULE),$ > (LOCAL_SHARED_LIBRARIES)) > > from build/core/build-binary.mk in the r5 ndk was intentional, and if > so, how should I be passing the other libraries that my shared library > depends on through so that the symbols are found? -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
