Xcode

From havefunsoft wiki
Revision as of 01:55, 6 December 2015 by Skalogryz (talk | contribs) (simutils)
Jump to: navigation, search

The Apple's default IDE is quite hostile to FPC, since it doesn't provide any source of "native" integration. In order for the compiler to be called a custom Run Script is needed to be used.

However it comes with some handy command-line tools that could be used for building projects. See Technical Note TN2339 for FAQ.

Command Line Utilities

xcodebuild

xcodebuild Man Page List all available SDKs

xcodebuild -showsdks

Build a project by it's (project directory) name and a specified sdk

xcodebuild -sdk iphonesimulator9.1 -project testProjGen.xcodeproj

instruments

The utility should only be ran via xcrun. Read manual page provided with Xcode command-line utilities installed.

The following command line runs Simulator booting the specified device. If the simulator is already running it would be rebooted with a the specified device, if it's different to the one already running.

xcrun instruments -w "%identifier%" -t "%template%"
  • %identifier% - is a part of the device name or ID.
  • %template% - if template is specified, then instruments doesn't return. If template is not specified (causes a warning on running) the instruments exists, leaving the device running.

simutils

An utility fo additional control over the simulator. Must be ran via "xcrun"

Lists all available devices in JSON format.

xcrun simctl list devices -j

Running without "devices" would list all devices. "-j" requests JSON format


Running an application on a booted device.

xcrun simctrl launch booted %bundle.id% 

"booted" can be replaced with an actual device id.


Running an application with waiting for a debugger (lldb).

xcrun simctrl launch -w booted %bundle.id%

The booted application will launch and pid for the application will return. For example:

bundle.id 1200

The pid is a normal process within OSX environment and should be attached via lldb debugger, i.e.

lldb attach %pid%

Run Script

  • in order to return an error, the (bash) script must use "exit" command with non-zero value. FPC returns a non-zero value when compiling failed.
  • do not specify "output files" of the script. Otherwise "Clean" will be required to make the script executed again