Skip to content

Conversation

@ViktorHofer
Copy link
Member

@ViktorHofer ViktorHofer commented Dec 16, 2019

  • Remove dependencies.props favor of Versions.props
    Versions.props is the Arcade entry point to manage version which are
    being used throughout the repository.

  • Use Arcade Sdk.targets in coreclr/src/Common
    At the moment only Arcade Sdk.props are being imported in the common
    managed projects. Changing that to make sure that the same compiler is
    being used everywhere.

  • Consolidate managed properties to OSGroup, ArchGroup and ConfigurationGroup. With the ongoing work done by @Anipik which will allow multi-targeting by OS this will be cleaned-up further.

  • Packaging fixes to point to the right license and third party notices

  • A lot of cleanup

cc @janvorli

@ViktorHofer ViktorHofer self-assigned this Dec 16, 2019
@ViktorHofer ViktorHofer changed the title Core clr test fixes Use Microsoft.Net.Compilers.Toolset in coreclr/src/Common projects Dec 16, 2019
Versions.props is the Arcade entry point to manage version which are
being used throughout the repository.
At the moment only Arcade Sdk.props are being imported in the common
managed projects. Changing that to make sure that the same compiler is
being used everywhere.
Restore and Build targets shouldn't run in the same msbuild invocation as
that could cause issues with nuget auto-generated props/targets.
Intermediate paths are encoded wrong so that
MSBuildProjectExtensionsPath which defaults to
BaseIntermediateOutputPath is set wrong and the in-built msbuild Exists
check fails. This is because of a mixture of different slashes.
The restore and build target invocations need to happen in separate
msbuild task invocations and different global properties need to be
passed in to mitigate issues with caching the invocations. For more
context see dotnet/msbuild#2811.
@ViktorHofer ViktorHofer force-pushed the CoreClrTestFixes branch 3 times, most recently from 1742717 to 2507255 Compare January 14, 2020 14:07
@stephentoub
Copy link
Member

@ViktorHofer, what's the state of this? Thanks.

@stephentoub
Copy link
Member

@ViktorHofer, given this has been open for two months, hasn't been touched in a month, has a bunch of conflicts, and there's been no response in over a week about status, I'm going to close this. It can obviously be re-opened when you're ready to proceed with it. Thanks.

@ViktorHofer
Copy link
Member Author

I've been working on this over the weekend but am still not in a state to push an update. Closing is fine, I'll reopen when this is ready again.

@stephentoub
Copy link
Member

Thanks.

@ghost ghost locked as resolved and limited conversation to collaborators Dec 11, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants