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

Update Mono to 6.8.0 #1697

Merged
merged 4 commits into from
Feb 5, 2020
Merged

Update Mono to 6.8.0 #1697

merged 4 commits into from
Feb 5, 2020

Conversation

JoeRobich
Copy link
Member

Mono 6.6.0 added a dependency on libintl that ships in the Mono pkg (mono/mono#18531). This dependency has been removed from later builds of 6.8.0.

Tested locally with 6.8.0.96 and saw failures. The stable MacOS release of 6.8.0.104 contains the fix. Linux builds use 6.8.0.96 as that is the released stable build.

Resolves #1693
Resolves dotnet/vscode-csharp#3545

@JoeRobich JoeRobich requested a review from filipw February 4, 2020 21:26
@filipw
Copy link
Member

filipw commented Feb 4, 2020

during the .NET Core 3.0 debacle with msbuild 16.3 the build script was updated to copy MSBuild from global mono at the build agent, instead of these zips. probably time to revert this 😁

@JoeRobich
Copy link
Member Author

probably time to revert this

You mean rely purely on the MSBuild zip files?

@filipw
Copy link
Member

filipw commented Feb 4, 2020

I am talking about this change #1612

would you mind reverting it as part of this PR?

otherwise we have older MSBuild in the released packages...

@JoeRobich
Copy link
Member Author

Ah, gotcha. Sure thing.

@filipw
Copy link
Member

filipw commented Feb 4, 2020

the alternative is to remove them from the JSON completely as they are not used at the moment and update build agents to 6.8.0 too so that it's in line with the bundled runtime when it comes to MSBuild

@filipw
Copy link
Member

filipw commented Feb 4, 2020

I somehow don't have access to that blob storage and when we needed to urgently update to MSBuild 16.3 due to the breaking changes in .NET SDK, and Ravi was unreachable, the best and quickest idea I had was to copy from the global Mono at build time instead 😅 that's the reason behind that change in the first place, in case you were wondering...

(sorry for slow responses, typing on mobile)

@JoeRobich
Copy link
Member Author

@filipw I think building it from the build script is probably the way to go. It looks like the build script was already augmenting the msbuild zips anyways,

@filipw
Copy link
Member

filipw commented Feb 4, 2020

OK makes sense to me. maybe let's just align the versions here https://github.com/OmniSharp/omnisharp-roslyn/blob/master/azure-pipelines.yml#L59 and https://github.com/OmniSharp/omnisharp-roslyn/blob/master/azure-pipelines.yml#L93 with the embedded runtime ones

Copy link
Member

@filipw filipw left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks!

@JoeRobich
Copy link
Member Author

In light of the way the Linux and MacOS legs failed. We may want to update this to the 6.8.0.105 version that just dropped.

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.

Omnisharp fails to load Omnisharp's mono tries to use system mono lib instead of bundled mono
2 participants