You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The dependencies are then importable via the import Swift statement using the names specified in the dependencies map of the swiftmodule.json file.
Using packages without a swiftmodule.json file
If a package does not include the swiftmodule.json file, the including package can specify the source file directory of the dependency in its swiftmodule.json.
SWM can also build the actual app (the root module). If a source directory is specified in the swiftmodule.json file, all .swift files inside that subtree are compiled into a binary.
$ swm build
Note that swm install also runs this internally.
Code Signing
Once the app is built, it needs to be code-signed for distribution using a certificate obtained from Apple. SWM makes this dead simple by listing the available certificates and provisioning profiles.
There are two signing modes:
store – should be used for signing for the App Store or other distribution
device – should be used for signing for development and testing purposes; this adds a provisioning profile to the app package.
$ swm sign store
Certificate:
1) CF826998D43332…499C595FCE980F20 "iPhone Developer: … (…)"
1
Signature for device
Certificate: CF826998D43332…499C595FCE980F20
Provisioning Profile: (none)
ok
The command prompts for the certificate number (1 in the case above).