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

Simplify usage of the installer and shared framework SDKs based on improvements in the tooling #109710

Merged
merged 2 commits into from
Dec 20, 2024

Conversation

jkoritzinsky
Copy link
Member

@jkoritzinsky jkoritzinsky commented Nov 11, 2024

@jkoritzinsky jkoritzinsky marked this pull request as ready for review December 19, 2024 19:24
@jkoritzinsky jkoritzinsky requested review from a team and NikolaMilosavljevic December 20, 2024 02:43
@ViktorHofer ViktorHofer merged commit ec1e561 into dotnet:main Dec 20, 2024
78 checks passed
ViktorHofer added a commit that referenced this pull request Jan 10, 2025
… VMR (#110676)

* Add a new crossgen2 build variant for a published crossgen2 targetting the host OS

* Remove the .NET-hosted in-build crossgen2 and just use the published in-build host-targeting crossgen2.

* Extract crossgen2 sfxproj changes from #109710

* Extract the properties and targets that will be shared into a separate props file.

* Add a "host crossgen2" project

* Add the crossgen2 host package to Subsets.props for the correct scenarios.

* Fix crossgen-corelib to work with the new in-build crossgen2

* Publish the in-build crossgen2 as single file to avoid having to adjust the AOT-in-build logic to handle AOT-ing for the host.

* AOT on Windows only

* Don't set Platform for the shared framework projects. It's not necessary and it breaks the new crossgen2 host package

* Forward ShortStack down so we don't build the host crossgen2 when runtime is the last repo.

* Add os-only RID to portable RID graph in source-build to enable crossgen2 tasks in the SDK to discover the target OS from the source-build target RID

* Publish the host crossgen2 as a "Vertical" visibility asset.

* Cleanup crossgen2 infra, add comment about workaround, and adjust publishing to publish packages as packages.

* Deduplicate artifacts

* Add back the Update, somehow this got lost.

* Don't forward down ShortStack

* Use new "update" functionality to specify which artifacts are vertical visibility

* Revert changes to Signing.props

* Remove workaround now that the VMR has a bootstrap SDK with a new enough version.

---------

Co-authored-by: Viktor Hofer <viktor.hofer@microsoft.com>
@github-actions github-actions bot locked and limited conversation to collaborators Jan 20, 2025
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.

2 participants