-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Introduces the new PIF builder for SwiftBuild #8405
Conversation
@swift-ci test |
Make sure you add the new files to the CMakeLists.txt file. |
@swift-ci test |
@swift-ci test |
@swift-ci test |
What's going on here? |
@swift-ci test |
@jakepetroules We had this duplicated |
@swift-ci test linux self hosted |
@swift-ci test macos smoke test |
@swift-ci please test macos |
@swift-ci test windows |
…8441) ### Motivation: The goal is to adopt the new `SwiftBuild.ProjectModel` API. This new API provides a *typesafer* and *modern* way of building PIFs programmatically. This continues the work I started in PR #8405, introducing now our new PIF builder for packages. ### Modifications: Replaces all `SwiftBuild.PIF` (aka, `SWBProjectModel.PIF`) API usage, in `PackagePIFBuilder`, with the new `SwiftBuild.ProjectModel` API instead. ### Result: `PackagePIFBuilder` is now modernized... but still not actually used. This will come in my next pull request. Tracked by rdar://147526957.
Introduces the new PIF builder for packages in
SwiftBuildSupport
.Motivation:
This continues the work started by PR 8271, introducing now our new PIF builder for packages. As expected, this will happen in the new
SwiftBuildSupport
target, introduced to support the just released Swift Build project.Modifications:
This 1st PR only includes the new code in the corresponding
SwiftBuildSupport/PIFPackageBuilder*.swift
source files. The code isn't actually being used (or unit tested) just yet.The code still uses the older
SWBProjectModel.PIF
API to build the PIF data model. In an upcoming PR, I will be migrating this over to the newerSwiftBuild.ProjectModel
API, and then finally replacing the original code to actually use the PIF builder to send package build information to Swift Build.PS. I did run
SwiftFormat
in all new code, as indicated by the contributors guide.Result:
This marks the start of our package PIF builder unification (i.e., between Xcode and SwiftPM).
Tracked by rdar://147767772.