diff options
| author | Sven Gothel <[email protected]> | 2013-01-31 21:15:32 +0100 |
|---|---|---|
| committer | Sven Gothel <[email protected]> | 2013-01-31 21:15:32 +0100 |
| commit | b47d0d92dd222999bf38633de1cec8de6a7ad369 (patch) | |
| tree | 764afc7741b6cb5cf3a11f5d4a8d3c117b3b5f0e /src/java/com/jogamp/gluegen/procaddress | |
| parent | c8de8fbf5d080b674b509763fbb7374c21ee705b (diff) | |
Android: Cleanup ClassLoaderUtil/LauncherUtil - Using cached parent ClassLoader for SYS-Packages w/ native libs, and non cached child ClassLoader for USR-Packages
Android's Dalvik VM, like a JVM, cannot load a native library from one location by multiple ClassLoader.
Since we don't like to hardcode the system-packages, as it was before, i.e. "com.jogamp.common", "javax.media.opengl",
we need to either copy the libs or use parenting of cached ClassLoader.
The latter is chosen, since it's faster and uses less resources.
- System-packages are passed through from the user 'List<String> LauncherUtil.BaseActivityLauncher::getSysPackages()'
to the ActivityLauncher, which instantiates the ClassLoader.
- No more hard-reference the system-packages in ClassLoaderUtil ("com.jogamp.common", "javax.media.opengl"),
just use the new user provided system-packages.
- The system-packages denominate a hash-key for caching, a new ClassLoader is created and mapped
if it does not yet exist.
- A non-chached user-packages ClassLoader is created using the cached system-packages ClassLoader as it's parent.
Diffstat (limited to 'src/java/com/jogamp/gluegen/procaddress')
0 files changed, 0 insertions, 0 deletions