[TIMOB-6566] Android: V8: Use dynamic linking / loading of stlport_shared to avoid symbol conflicts in modules

GitHub Issue	n/a
Type	Bug
Priority	Critical
Status	Closed
Resolution	Fixed
Resolution Date	2012-01-10T11:06:49.000+0000
Affected Version/s	Release 1.8.0.1
Fix Version/s	Sprint 2011-49, Release 1.8.0.1, Release 2.0.0
Components	Android
Labels	branch-v8, module_build, qe-testadded, verified-1.8.0.1
Reporter	Marshall Culpepper
Assignee	Marshall Culpepper
Created	2011-12-11T21:49:32.000+0000
Updated	2012-01-11T15:29:12.000+0000

Description

The NDK docs specify that apps should link against stlport_shared if they intent to load multiple shared libraries as part of the application. Since our 3rd party modules are loaded the same way our kroll-v8 shared lib is, we should change to compiling against / loading stlport_shared in our runtime.

Comments

Marshall Culpepper 2011-12-12

To test this fix, verify that stlport_shared is now bundled and loaded in a Titanium app: * Verify libstlport_shared.so is bundled in both armeabi/armabi-v7a dirs by looking at the APK:

   $ unzip -l build/android/bin/app.apk | grep libstlport_shared.so
      393956  12-11-11 23:46   lib/armeabi/libstlport_shared.so
      394256  12-11-11 23:46   lib/armeabi-v7a/libstlport_shared.so

* Verify the Titanium app loads libstlport_shared.so at bootup. This message may vary from device to device, but on my Galaxy Tab it looks like this:

   D/dalvikvm( 1169): Trying to load lib /data/data/com.arcaner.test3/lib/libstlport_shared.so 0x40871430
   D/dalvikvm( 1169): Added shared lib /data/data/com.arcaner.test3/lib/libstlport_shared.so 0x40871430

Michael Pettiford 2011-12-19

Tested with studio version 1.0.7.201112152014 Ti Mob SDK 1.8.0.1.RC3 OSX Lion Galaxy Tab 7in OS 2.X Verified expected behavior based on Marshall's comments *Note keeping open to confirm against 1.9.0 before closing
Dustin Hyde 2012-01-10

Added Label: qe-testadded.
Wilson Luu 2012-01-11

Closing bug. Already verified fix on 1.8.0.1

JSON Source