[swift-build-dev] [swift-evolution] SwiftPM Xcode Integration
Andrew Bennett
cacoyi at gmail.com
Fri Feb 19 19:01:27 CST 2016
Excellent news!
At the moment I have a workflow that uses xcconfig files and XCake:
https://github.com/jcampbell05/xcake
XCake sounds similar to zewo, by the sounds of it, I think its author is
active on this list.
The main reason for my workflow is because it makes it much easier to make
new modules, copy configuration, and resolve merge conflicts.
In that context, I have a few questions:
* Is it intended that the generated Xcode project will be checked-in?
* Will the project duplicate information that SwiftPM specifies? file
references? configuration?
* Will the rebuild clobber project configuration that SwiftPM can't
specify? This is probably fine. Maybe Xcode should make configuration
read-only in generated projects.
On Saturday, 20 February 2016, Max Howell via swift-evolution <
swift-evolution at swift.org> wrote:
> What kind of target will be made in the Xcode project? Specifically, will
> it be a static library or a framework?
>
>
> Frameworks.
>
> The folks behind Zewo made a tool to help us manage our large dependency
> graph that generates complete xcode projects with subprojects and targets
> (it also does a few other things, but those aren't important). As a side
> effect it also supports modulemaps with no extra configuration. It
> generates frameworks (not static libraries) for the reasons described
> earlier, but I'm sure it would be trivial to change it to work the other
> way.
>
> The tool can be found here: https://github.com/zewo/zewo-dev.
> Unfortunately it had to be made in ruby because of the xcodeproj gem but I
> believe it could still be a useful reference.
>
>
> Thanks for the link, a very interesting project.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-build-dev/attachments/20160220/ad26f725/attachment.html>
More information about the swift-build-dev
mailing list