Skip to content

Commit 2b1201b

Browse files
authored
Merge pull request #62 from Pinwheeler/patch-1
Update buildingWithSPM.md
2 parents 680babf + 860ecaa commit 2b1201b

File tree

1 file changed

+1
-5
lines changed

1 file changed

+1
-5
lines changed

guide/buildingWithSPM.md

Lines changed: 1 addition & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -108,11 +108,7 @@ swift build
108108
This command will download any dependencies if they haven't been already acquired and attempt to build the project. If the build is successful, then the resulting executable will be placed in the (hidden) ```.build/debug/``` directory. When building the PerfectTemplate project, you will see as the last line of SPM output: ```Linking .build/debug/PerfectTemplate```. Entering ```.build/debug/PerfectTemplate``` will run the server. By default, a debug version of the executable will be generated. To build a production ready release version, you would issue the command ```swift build -c release```. This will place the resulting executable in the ```.build/release/``` directory.
109109

110110
```
111-
swift build --clean
112-
```
113-
114-
```
115-
swift build --clean=dist
111+
swift package clean
116112
```
117113

118114
It can be useful to wipe out all intermediate data and do a fresh build. Providing the ```--clean``` argument will delete the ```.build``` directory, and permit a fresh build. Providing the ```--clean=dist``` argument will delete both the ```.build``` directory and the ```Packages``` directory. Doing so will re-download all project dependencies during the next build to ensure you have the latest version of a dependent project.

0 commit comments

Comments
 (0)