[gambit-list] Dynamically loadable libraries on iOS

Petersen, Chris CPetersen at cw.bc.ca
Thu Jul 3 20:13:49 EDT 2014

We encountered this problem years ago in the early development of LambdaNative. The first versions used
dynamically loadable modules, which turned out to be problematic on several platforms.  If memory serves
me we did have Gambit’s dynamic loading working on jailbroken iOS devices at one point. I don’t think Apple
makes any distinction between dynamic libraries and Gambit's loadable libraries though, and apps using it
are probably going to be rejected on the store anyway.


On Jul 3, 2014, at 4:05 PM, Álvaro Castro-Castilla <alvaro.castro.castilla at gmail.com<mailto:alvaro.castro.castilla at gmail.com>> wrote:


<sorry for resposting, I accidentally removed some text from the email>

Being aware that Apple doesn't allow apps with dynamic libraries (except for those provided by them), I'm trying to make Gambit's dynamically loadable libraries work in the platform.

I can make them work well on the iOS simulator, but on the iPhone/iPad devices don't work. The funny thing is that as soon as the (load) procedure is called...

- When running with Xcode connection, the app stalls with no output or crash at all.
- When running directly on the device without Xcode debugging connection, then it crashes.

All compiler and linker flags have been checked thoroughly. Compiling and linking work flawlessly, and the load procedure doesn't throw any error.

Is this an expected behavior? Any ideas of why this behavior might occur?

Best regards,

Gambit-list mailing list
Gambit-list at iro.umontreal.ca<mailto:Gambit-list at iro.umontreal.ca>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.iro.umontreal.ca/pipermail/gambit-list/attachments/20140703/470182ac/attachment.htm>

More information about the Gambit-list mailing list