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
[5.9] Add templates for build tool plugins and command plugins (#6352)
Adds templates for build tool plugins and command plugins, allowing them to be created from the `swift package init` command. The packages are set up to vend the plugins via plugin product declarations, so they can be used by other packages. The initial code for each each plugin type is minimal, but for the build tool plugin type it shows how to create and return a build command for each source file of a particular type, since that's the most common use of build tool plugins.
rdar://107288352
Co-authored-by: Anders Bertelrud <anders@apple.com>
(cherry picked from commit f25e138)
Co-authored-by: Boris Bügling <bbuegling@apple.com>
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
@@ -3,6 +3,10 @@ Note: This is in reverse chronological order, so newer entries are added to the
3
3
Swift Next
4
4
-----------
5
5
6
+
*[#6111]
7
+
8
+
Package creation using `package init` now also supports the build tool plugin and command plugin types.
9
+
6
10
*[#5728]
7
11
8
12
In packages that specify resources using a future tools version, the generated resource bundle accessor will import `Foundation.Bundle` for its own implementation only. _Clients_ of such packages therefore no longer silently import `Foundation`, preventing inadvertent use of Foundation extensions to standard library APIs, which helps to avoid unexpected code size increases.
0 commit comments