Furthermore, if a new target is added to a package’s manifest, Xcode will automatically pick that up and display that new target within its scheme selector (the caveat here being that, at the time of writing, you do need to manually create folders for each target’s source files). The contents of a Swift package is defined using a Package.swift manifest file, and editing such files has now been made a lot easier, thanks to proper autocompletion and syntax highlighting. Swift packages can now easily be created right from within Xcode. New packages can easily be created using a new Swift Package option in the File > New submenu, and Xcode is capable of opening any existing Swift package as well (without requiring an Xcode project file to be generated). Creating and building packagesįor Swift package authors (or anyone who wants to start modularizing their code base by moving things into frameworks), Xcode now offers complete support for creating and editing packages. Let’s take a first look at this new integration, and what sort of features that it currently offers.

While the new version of Xcode is only in an initial beta stage at this point - it already features an impressive amount of functionality when it comes to building, using, and managing Swift packages. One of the most exciting new features in Xcode 11 is that the Swift Package Manager is finally becoming a first class citizen within Apple’s IDE.

Swift package manager build time