This repository has been archived by the owner on Mar 9, 2023. It is now read-only.
Fix Darwin builds #32
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Make HOME_BREW location configurable in Darwin
rwhitby
changed the title
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
[Originally from https://github.com/rwhitby/pull/2 by https://github.com/jrrk2]
The location of the clang compiler in home-brew seems to vary between Darwin versions. This patch pins it down so that it can be determined automatically. I use the command:
brew --prefix llvm
which on my machine evaluates to:
/opt/homebrew/opt/llvm
[end of PR from jrrk2]
Also, the PRJXRAY build on Darwin requires C++11, so ensure that is used.
Also, the python build for NextPNR fails on macOS (boost cmake problem), and is not required, so simply disable it.