Skip to content

Conversation

@NikolaMilosavljevic
Copy link
Member

Fixes: #398

Native projects are failing due to compiler mismatch between object file produced in the build and dependent lib file produced by runtime. Per @MSLukeWest these projects can be disabled. If we ever need to build them again, it will be easy to re-enable them. Historically, compiler mismatch only existed during short period around .NET GA timeframe.

Additionally I've updated the Signing.props file to allow empty sign list as there won't be any artifacts for signing in x86/arm64 builds. This follows existing pattern in runtime and aspnetcore.

@ViktorHofer
Copy link
Member

ViktorHofer commented Oct 23, 2024

Just wondering, could this break the VMR or aren't we using the native projects in the product graph anywhere?

@NikolaMilosavljevic
Copy link
Member Author

Just wondering, could this break the VMR or aren't we using the native projects in the product graph anywhere?

Native projects (NetCoreCheck tool) aren't building in VMR as there are no consumers of this tool.

@NikolaMilosavljevic NikolaMilosavljevic merged commit ceda306 into dotnet:main Oct 24, 2024
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[internal/main] Native NetCoreCheck projects are failing to build

4 participants