David Given wrote:
[...]
> Perhaps I should avoid libc completely where possible and do direct
> syscalls instead? It's awfully ugly. Unless there's a set of Official
> Header files somewhere that I've missed, which I could compile against...
Thanks to the magic of Unix textutils, I've managed to put together a
workaround:
($(OBJDUMP) -T libc.so && \
$(OBJDUMP) -T libm.so) | \
awk '$$2=="g" { print $$6 }' | sort > libsymbols
$(OBJDUMP) -T $(LIBNAME) | \
awk '$$3=="*UND*" { print $$5 }' | sort > mysymbols
diff mysymbols libsymbols | grep '<'
You need to pull the libraries you're interested in off the device with
adb pull; then the above will collect the list of symbols in the
libraries, the list of symbols in your shared library $(LIBNAME), and
report all symbols that aren't there. What you should get is no output.
Hope this is of use to someone...
--
David Given
[EMAIL PROTECTED]
--~--~---------~--~----~------------~-------~--~----~
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]
Announcing the new M5 SDK!
http://android-developers.blogspot.com/2008/02/android-sdk-m5-rc14-now-available.html
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~----------~----~----~----~------~----~------~--~---
