-
Notifications
You must be signed in to change notification settings - Fork 420
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
Fix build on macOS Sierra #644
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👎 No good. It still breaks in the same way as before this change was applied.
really? hmmm... |
i think i see where it's failing. |
@wjk: I'm installing Sierra now. Want to try again after my last tweak? |
nevermind. this won't fix it yet. The problem is that OmniSharp is using |
OK. Fingers crossed. Works on my (macOS Sierra) machine. |
d524b68
to
cb15553
Compare
Note: Adding all of the runtimes to the test projects (+ an extra one for AppVeyor) feels just awful. Does anyone have any better ideas here? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 Works great! Builds on my macOS Sierra machine with no issues.
Thanks, that fixes my issue! 😸 ❤️ |
It turned out that the OmniSharp.Tests was defined incorrectly. It was a netcoreapp1.0, but wanted to act like a library.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Without a mac I can't say it works for me (:sheep:) but changes look good.
Fixes #643
This should fix builds on macOS Sierra.
There were a couple of problems that needed fixing due to runtime packages not being available for macOS Sierra (osx.10.12-x64).
dotnet restore --infer-runtimes
. Since there aren't runtime packages for macOS Sierra, it failed. We actually don't to specify this any longer, so I removed the flag.dotnet publish
needs to specify a runtime on macOS Sierra. Otherwise, it will specify the current runtime (osx.10.12-x64), which doesn't exist. So, the build script now detects the current RID by looking at the output ofdotnet --info
. Then, in the publish step, the build script checks to see if the current RID isosx.10.12-x64
when attempting to publish for "default" and usesosx.10.11-x64
instead.