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
I can recall a point in time where all one needed to do was run
$ utils/build-script --llbuild --swiftpm
and that would pick up the just-built host tools and use xcrun to fill in the gaps. Recently, we've begun forming paths to swiftc relative to a toolchain dir, which implies that the bootstrap script wants you to actually run with the necessary install flags turned on in build-script. This seems like a step backwards in terms of functionality. Unless asked to install swiftpm, we should form paths to the just-built tools and invoke the bootstrap script that way.
The text was updated successfully, but these errors were encountered:
Additional Detail from JIRA
md5: 8fdb8e0f2edb72cddd364992c2175186
Issue Description:
I can recall a point in time where all one needed to do was run
$ utils/build-script --llbuild --swiftpm
and that would pick up the just-built host tools and use xcrun to fill in the gaps. Recently, we've begun forming paths to swiftc relative to a toolchain dir, which implies that the bootstrap script wants you to actually run with the necessary install flags turned on in build-script. This seems like a step backwards in terms of functionality. Unless asked to install swiftpm, we should form paths to the just-built tools and invoke the bootstrap script that way.
The text was updated successfully, but these errors were encountered: