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

Require swift, add LDFLAG path #5

Closed
wants to merge 2 commits into from
Closed

Require swift, add LDFLAG path #5

wants to merge 2 commits into from

Conversation

BenjaminHCCarr
Copy link
Contributor

You may want to sit on this until I get 8.0 command line, if swift is shipped by default in it. Apple's swift git tree, still doesn't have 3.0 even on HEAD.

If we need to compile swift, this should do it.

Just tried to build the new version. Swift isn't installed by default. So to brew it you need the:

'depends_on "swift"'

line. You already had swift as you develoe in it, I needed to grab the Homebrew.
Homebrew swift isn't setup to build packages by default:

'''
This formula is keg-only, which means it was not symlinked into /usr/local.

Apple's CLT package contains Swift.

Generally there are no consequences of this for you. If you build your
own software and it requires this formula, you'll need to add to your
build variables:

    LDFLAGS:  -L/usr/local/opt/swift/lib
'''
@SpencerMichaels
Copy link
Owner

As mentioned in issue #4, there actually is no CLT 8.0, so until Brew updates its Swift package, those without Xcode.app may have to use swiftenv or manually install Swift 3.0 themselves. Should we do depends_on "swift" => 3.0 here?

@BenjaminHCCarr
Copy link
Contributor Author

I haven't tested that but am willing too.

It doesn't really matter how one acquires swift, but it doesn't look like CLT8 is coming any time soon. Happy to try.

@BenjaminHCCarr
Copy link
Contributor Author

CLT are out!

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

Successfully merging this pull request may close these issues.

2 participants