Skip to content
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

Swift 4 Migration #36

Open
1 of 3 tasks
youming-lin opened this issue Aug 21, 2017 · 2 comments
Open
1 of 3 tasks

Swift 4 Migration #36

youming-lin opened this issue Aug 21, 2017 · 2 comments

Comments

@youming-lin
Copy link
Collaborator

youming-lin commented Aug 21, 2017

  • SPM is changing executable location again. BasePath.project will be removed along with implicit Xcode support.
  • Update Package.swift to Swift 4 format.
  • Add new APIs to support Codable.
@svanimpe
Copy link

@youming-lin I am using BasePath.project to load project files. What should I use instead?

@youming-lin
Copy link
Collaborator Author

@svanimpe Depends on your use case, but I lean towards .pwd now. It is the method least affected by changes in build process. As it is currently,swift build --build-path can break .project as .project assumes the existence of a Package.swift somewhere in a parent folder of the executable.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants