-
Notifications
You must be signed in to change notification settings - Fork 12
Description
This one adds to the discoveries made in #9
Some Goolgling indicates the following to be a rather huge problem.
While Modules can be "installed" on Android they invariably contain a "*.so" library file. These files get installed into a directory which is marked as noexec resulting in the library existing but not being loadable.
This is the reason that the deployment of libpython[ver].[subver].so is required in addition to the Python system files (which include 'noexec' another copy of the same file)
While extensions without a library should install and function properly those with a library can't run with the current deployment method (as they'll be noexec).
One solution to this issue would be to deploy 'extra copies' of the module libraries along with the main APK and use those instead of the module's library. Problematically this fragments the deployment strategies depending on OS, CPU and Architecture.
One particularly annoying issue is that this does rather preclude the ability to deploy ad-hoc libraries to Android as you'll need to package all libraries along with the main APK.
Research continues...