I dont know if this relates to ur case but i have faced a similar problem with cmake in the past. This is a general behaviour of make in which the binaries generated in build tree will always have hardcoded absolute paths to shared libraries. But if one runs make install and then uses those binaries, they have relative paths. The binaries generated by make install are the ones meant to be finally used and run on the target system.
Did u also copy the binaries from an intermediate directory ? Hope this helps. -- -- You received this message because you are subscribed to the "Android Building" mailing list. 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-building?hl=en --- You received this message because you are subscribed to the Google Groups "Android Building" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
