You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Allow sources anywhere in ./Sources when only one target is present
After getting some feedback about the added `path` argument for executable
packages generated with `swift package init` (#6144), this change allows a
target's sources to occupy the entire sources directory when there is only one
target in the package. All package types can benefit from this.
When there is more than one target in a package, the existing requirements for
target sources still apply.
This change should be compatible with existing layouts as well. If there is
only a single target in a package, then sources can of course continue to exist
in `./Sources/<target>`.
Amend the `executable` template's generated manifest to not include the `path`
argument anymore.
rdar://106829666
Copy file name to clipboardExpand all lines: CHANGELOG.md
+4Lines changed: 4 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -20,6 +20,10 @@ Swift Next
20
20
Swift 5.9
21
21
-----------
22
22
23
+
*[#6294]
24
+
25
+
When a package contains a single target, sources may be distributed anywhere within the `./Sources` directory. If sources are placed in a subdirectory under `./Sources/<target>`, or there is more than one target, the existing expectation for sources apply.
26
+
23
27
*[#6114]
24
28
25
29
Added a new `allowNetworkConnections(scope:reason:)` for giving a command plugin permissions to access the network. Permissions can be scoped to Unix domain sockets in general or specifically for Docker, as well as local or remote IP connections which can be limited by port. For non-interactive use cases, there is also a `--allow-network-connections` commandline flag to allow network connections for a particular scope.
0 commit comments