[CI] Add an "OSX .NET Core" build. #655
Merged
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.
Adds a
Mac - .NET Corebuild to Azure Pipelines.Some notable changes:
Preparetarget on Mac (.NET Core only) to move closer to what Windows uses, with the eventual goal of all systems being identical.Microsoft.NETFramework.ReferenceAssembliesNuGet package to all assemblies that targetnet472. This allows them to be built on .NET Core, which does not havenet472framework assemblies.<Exec>tasks. Mono will fix these for us,dotnetwill not.jnienv-genlogic to handle runningjnienv-gen.dllondotnetin more places.Note Mono is still used in the following cases:
make prepare-coreuses Mono/MSBuild to buildBootstrapTasks.dllto runJdkInfo.props.mono jnienv-gen.exeis used when it is run from a project build targetingnet472.libjava-interop.dylib.Eventually these first 2 uses of
monocould probably be removed, But this gets us started.