Skip to content

Conversation

@ViktorHofer
Copy link
Member

Replaces #109619

We made a similar change recently in arcade to not use the TFM but a normalized value of the TargetFrameworkIdentifier property for tools packages.

Replaces #109619

We made a similar change recently in arcade to not use the TFM but a normalized value of the TargetFrameworkIdentifier property for tools packages.
@dotnet-policy-service
Copy link
Contributor

Tagging subscribers to this area: @dotnet/area-infrastructure-libraries
See info in area-owners.md if you want to be subscribed.

@am11
Copy link
Member

am11 commented Nov 8, 2024

Nice! It'll also need am11@fd067c5.

@ViktorHofer
Copy link
Member Author

Oh right, we don't need that with this change anymore. Perfect :)

@ViktorHofer
Copy link
Member Author

ViktorHofer commented Nov 8, 2024

@am11 I tried to directly apply your patch to keep you as the committer but git didn't let me (corrupt file at L...). So I manually applied it.

@am11
Copy link
Member

am11 commented Nov 8, 2024

No worries. I'm just happy to see another hardcoded platform list going away. 🙂

@ViktorHofer
Copy link
Member Author

Oh damn. Locally in runtime we don't use the package layout but the build output.

@am11
Copy link
Member

am11 commented Nov 8, 2024

Another piece of the puzzle: main...am11:runtime:patch-19

Copy link
Member

@sbomer sbomer left a comment

Choose a reason for hiding this comment

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

Nice, thank you!

@akoeplinger
Copy link
Member

/ba-g wasm failures are note related to the ILLink changes

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