17.1 Delivering for iOS

The Lisp part of the application needs to be delivered using one of three special images:

• lispworks-8-0-0-arm64-darwin-ios which build runtimes for both the iOS Simulator and for a real iOS device when creating them on Apple silicon Macs. Or:
• lispworks-8-0-0-amd64-darwin-ios which builds runtimes for the iOS Simulator, running on macOS on Intel based Macs. Or:
• lispworks-8-0-0-arm64-linux-ios which builds runtimes for a real iOS device when creating them on Intel based Macs. To do this, you run the QEMU emulator on macOS and tell it to run the lispworks-8-0-0-arm64-linux-ios image.

There is an example script examples/ios/run-lw-ios.sh which can be used to invoke the correct images depending on the type of Mac you are using.

These images do not contain the GUI part of LispWorks, but do contain all the non-GUI parts.

There are no iOS-specific Lisp functions required to build the Lisp part of an application: you use deliver in the normal way. There are three differences compared to a desktop application:

• The file passed to deliver should have a ".o" extension.
• deliver will append the architecture and platform name at the end of the name component of file.
• When running on an Apple silicon Mac, deliver will create two files, one for the iOS Simulator and one for real iOS devices.
• The generated files will be iOS object files that must be linked with the other parts of the application using Xcode. Generation of shared libraries is not supported (this is a limitation of iOS).

  To include the delivered object file in an Xcode project, you should add the following to the Xcode project's "Other Linker Flags":

  filename-${CURRENT_ARCH}-${PLATFORM_NAME}.o
  

  where filename is the &FILE argument to deliver without the .o extension.

Compatibility note: In previous versions of LispWorks, you needed to conditionalize the filename passed to deliver based on the platform. This is now done automatically and conditionalization should be removed.