Adding Swift 3 packages to Xcode 8 using the Swift package manager

Question

I am new to Swift and Xcode. I am running macOS Sierra and Swift 3.

For my first forays in Swift, I am developing a simple command line tool. There are a couple of Swift packages that I want to use and the installation instructions for both packages on GitHub says to use the Swift package manager by simply adding them as dependencies in the package manifest file.

What I can't figure out is how to do this in Xcode. Do I just create a 'package.swift' file in the root of my project? Doing this and then running the project doesn't seem to work as the required packages don't seem to be added to my project.

Am I doing something wrong?

Install it via cocoapods! See cocoapods website for installation guide — Do2
– Do2, Commented Sep 26, 2016 at 18:04
@Do2 The question is clearly about Swift packages. Answering someone (in comments, no less) by telling them to use something else is unhelpful. — Joshua Nozzi
– Joshua Nozzi, Commented Mar 31, 2018 at 15:35

jscs · Accepted Answer · 2016-09-26 18:13:31Z

42

Xcode and the SPM can work together, but as far as I can tell you do need to take one step on the command line.

Put your package manifest file into the same directory as the Xcode project, and then invoke swift package generate-xcodeproj

The package manager will pull down your dependencies and rewrite the .xcodeproj file to refer to them.

It will preserve any existing source, but the directory structure will be reconfigured to SPM's preferred arrangement:

PROJECT_DIR
├── Sources
│   └── ProjectName
│       ├── YourCode.swift
│       └── YourOtherCode.swift
├── Dependencies
│   └── SomeDependency
│       ├── DependencyCode.swift
│       └── OtherDependencyCode.swift
└── Package.swift

N.B., I haven't tested this extensively on a live project; given the fact that SPM docs still say WIP, please make sure you've made a recent commit.

answered Sep 26, 2016 at 18:13

jscs

64k13 gold badges155 silver badges200 bronze badges

Sign up to request clarification or add additional context in comments.

4 Comments

Garry Pettet Over a year ago

Thanks. Works a charm. +1 for the safety advice too!

Rehat Kathuria Over a year ago

Is there any way to force SPM not to change the directory structure inside the .xcodeproj file? I'm not too fussed about all my files being inside the Sources folder but I also have groups inside of the navigator that are pointing to the Sources folder and I'd like them to remain intact.

Pouria Almassi Over a year ago

A note to anyone who performs these steps then gets a "no module foo found" compiler error. As of version 9.2 Xcode provided me two recommended project changes, one of which was setting Swift 3 @objc Inference to default. After performing these changes my target recognised the external dependency module for import.

jscs Over a year ago

Thanks for the update, @Airuop. Haven't don this in a while; I've made myself a todo to try it and make sure the answer isn't missing anything else.

thSoft · Accepted Answer · 2016-12-15 23:49:18Z

0

In addition to running swift package generate-xcodeproj, I had to build my project in Xcode before I could use the installed packages.

answered Dec 15, 2016 at 23:49

thSoft

22.8k6 gold badges96 silver badges105 bronze badges

1 Comment

zirinisp Over a year ago

Makes total sense, as the package manager downloads the packages, then to use them you have to compile them.

Collectives™ on Stack Overflow

Adding Swift 3 packages to Xcode 8 using the Swift package manager

2 Answers 2

4 Comments

1 Comment

Linked

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

4 Comments

1 Comment

Linked

Related