New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[SR-2718] Xcode generated projects in custom locations have incorrect path to project in scheme file; causes broken refs to buildables #5211
Comments
Yes, this is clearly wrong. Also, is it expected that there should be schemes for each of the modules, independently, or should there just be the one Zewo scheme? It looks like the old project generator generated just the one scheme. |
Related to https://bugs.swift.org/browse/SR-2719, most likely. |
In the case of not passing `--output`, the project is found correctly. But it's possible that the `ReferencedContainer` key needs to have the relative path of the project in the custom-output location case. |
So I don't think this is the same as https://bugs.swift.org/browse/SR-2719, though it's related. |
BTW, the scheme is always being created at the right location; it's a question of a problem with the paths in it so it can still find the project container even when it's in a custom location. |
Changing `ReferencedContainer` to be a relative or an absolute path from the source directory to the project path fixes the top-level entry so that it's not showing up as broken (just a gear) any more. But for some reason Xcode is still autogenerating additional schemes (one for each framework) when the generated Xcode project lives somewhere else (it doesn't do that when the project is in the default location). There's nothing different about the generated scheme file, just how Xcode reacts to it. |
This was fixed here: a23ddbc |
Attachment: Download
Additional Detail from JIRA
md5: b941fcc64fbbb37af9fd4d16dfc71f51
Issue Description:
Using DEVELOPMENT-SNAPSHOT-2016-09-20-a if I create a directory called Xcode on the root of a Swift package and run:
swift package generate-xcodeproj --output Xcode
SwiftPM generates the Xcode project, but the package scheme is not configured correctly. See screenshot attachment for reference.
The text was updated successfully, but these errors were encountered: