{"id":2617,"date":"2016-01-31T09:26:50","date_gmt":"2016-01-31T15:26:50","guid":{"rendered":"http:\/\/dev.iachieved.it\/iachievedit\/?p=2617"},"modified":"2016-02-04T13:45:48","modified_gmt":"2016-02-04T19:45:48","slug":"creating-new-packages-with-swiftpm","status":"publish","type":"post","link":"https:\/\/dev.iachieved.it\/iachievedit\/creating-new-packages-with-swiftpm\/","title":{"rendered":"Creating New Packages with SwiftPM"},"content":{"rendered":"

\"Swift<\/a> \"ISC\"<\/a><\/p>\n

Back in December I opened an enhancement request in the Swift JIRA<\/a> site, issue SR-353<\/a>, to add an npm init<\/code>-style invocation to swift build<\/code> for creating all of the boilerplate files needed for a complete Swift package. It wasn\u2019t too long after the request was added that Bastian Rinsche<\/a> and Tobias Landsberg<\/a> implemented the feature and had a pull request accepted<\/a>. Bastian has written up a great post<\/a> on his experience with opensource Swift and contributing to the community with the implementation of swift build --init<\/code>.<\/p>\n

Let’s look at how it works. First, create a new directory with mkdir<\/code> for your package or application. We’ll use helloworld<\/code> as an example: mkdir helloworld<\/code>. Now, cd<\/code> into your helloworld<\/code> directory and run swift build --init<\/code>.<\/p>\n

\n# cd helloworld\n# swift build --init\nCreating Package.swift\nCreating .gitignore\nCreating Sources\/\nCreating Sources\/main.swift\nCreating Tests\/\n<\/pre>\n
Let’s take a look at what swift build --init<\/code> generates:<\/p>\n