swift-xcode
swift-xcode copied to clipboard
SwiftXcode
Use Swift Package Manager directly from within Xcode, w/o the cmdline
This is with the /usr/local x86 Homebrew: ``` arch -x86_64 brew install swiftxcode/swiftxcode/swift-xcode-wo ... ==> Installing swiftxcode/swiftxcode/swift-xcode-wo dependency: swiftxcode/swiftxcode/swift-progress ==> make all ... clang: error: the clang compiler does not...
When creating projects in Xcode 10.1, they end up as Swift "4" (4.0) in the Xcode build settings. My best guess is that Xcode itself peeks into the Package.swift file...
# Summary Running `swift xcode link-templates` when homebrew is installed somewhere other than `/usr/local` will cause the link to fail. In my case, my homebrew is installed in `~/.homebrew` so...
… might be unrelated, but besides that, there's not much special. Xcode: Version 10.1 (10B61), default toolkit [Build MicroExpress_2018-11-29T15-21-11.txt](https://github.com/SwiftXcode/SwiftNIO_XcodeImage/files/2629479/Build.MicroExpress_2018-11-29T15-21-11.txt)
I have a iOS project setup with the swift-code standard template and the imports work fine but in the test target I get a `No such module` error.
You can use `#file` to locate resources stored alongside your sources in packages. Since we are building images in a different location from their final location, this may not work...
When moving swift-xcode projects to a new location, they won't build anymore if they contain modmaps. This is due to the absolute links in them. We can fix this by...
Image compilation can take a moment. Speed that up by prebuilding bottles. Ideally in an automatic way using Travis.
Metadata
Owner
Metadata
Use Swift Package Manager directly from within Xcode, w/o the cmdline