Wait, eventually you will need a custom configuration for Xcode: $ swift package generate-xcodeproj \ Here is a necessary modification: $ swift package generate-xcodeproj \Ī bit more text but this still can be remembered. What about more arguments though? Let’s assume we need to enable code coverage. Not easy to remember but after 3-5 times you can type these words without looking into your Terminal history. To create a project for editing this package in Xcode, we should run a short command like this: $ swift package generate-xcodeproj Let’s imagine a standard package like this: ├── Package.swift
Thanks to modern Swift tools, each library can live in its own repository and can be edited as a separate Xcode project. Today I’d like to share one simple trick which helps to switch between internal packages fast and easily.
This nice setup allows for developing embedded libraries and their tests independently of the main app. NativeConnect for Mac is 100% Swift, and it includes three frameworks built with Package Manager: NativeKit, NativeUI, and NativeData.