[swift-build-dev] SwiftPM platform-specific build folders
Daniel Dunbar
daniel_dunbar at apple.com
Mon Jun 19 17:49:38 CDT 2017
(CC'ing a couple people I know have worked on build packs in the past.)
Thanks David!
For those only on the mailing list, we discussed this plan on the SwiftPM Slack channel, and I think making this change in the Swift 4 timeframe is right, even though it may break some things.
One of the main goals of the compatibility work is to make sure that we don't break any of the existing deployment workflows people have built on top of SwiftPM (for example PaaS buildpacks). We don't have time for a full "make install" type workflow which buildpacks could use, but my hope was that SR-5259 would be something existing build packs could migrate to to avoid having to hard code certain paths.
We'd love feedback on whether this seems like a reasonable plan.
- Daniel
> On Jun 19, 2017, at 3:19 PM, David Hart via swift-build-dev <swift-build-dev at swift.org> wrote:
>
> Hello mailing-list,
>
> I’m implementing SR-3583 <https://bugs.swift.org/browse/SR-3583> that builds SwiftPM products into platform-specific sub-folders. For example, on macOS, a default build will no longer build products into .build/debug but instead in .build/macosx-x86_64/debug.
>
> To alleviate this breaking change, several solutions have been planned:
>
> SE-0179 <https://github.com/apple/swift-evolution/blob/master/proposals/0179-swift-run-command.md>: A new swift run tool to allow users to run executable products without knowing their exact location.
> SR-3583 will create a symlink after each build pointing from the old to the new build folder for backwards compatibility.
> SR-5259 <https://bugs.swift.org/browse/SR-5259>: A new —bin-path option for the swift build command to print the build folder for 3rd party tools to use.
>
> Of the above, only SE-0179 is currently fully implemented in master.
>
> What does everybody think about this change and the solutions put into place to support it?
>
> Regards,
> David.
> _______________________________________________
> swift-build-dev mailing list
> swift-build-dev at swift.org
> https://lists.swift.org/mailman/listinfo/swift-build-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-build-dev/attachments/20170619/9ab23210/attachment.html>
More information about the swift-build-dev
mailing list