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

Set UseNativeAotForComponents to false on bionic #103454

Merged
merged 3 commits into from
Jun 14, 2024

Conversation

MichalStrehovsky
Copy link
Member

This was enabled in #103273 but needs more work to actually build. Official builds are failing.

This was enabled in #103273 but needs more work to actually build. Official builds are failing.
@@ -18,6 +18,9 @@
<SysRoot Condition="'$(CrossBuild)' == 'true' and '$(HostOS)' != 'windows'">$(ROOTFS_DIR)</SysRoot>
<LinkerFlavor Condition="'$(CrossBuild)' == 'true' and '$(TargetsLinux)' == 'true'">lld</LinkerFlavor>
<CustomLinkerArgToolchainArg Condition="'$(CrossBuild)' == 'true' and '$(HostArchitecture)' == '$(TargetArchitecture)' and '$(HostOS)' != 'windows'">--gcc-toolchain=$(ROOTFS_DIR)/usr</CustomLinkerArgToolchainArg>

<!-- disable on linux-bionic, for now -->
<UseNativeAotForComponents Condition="'$(TargetsLinuxBionic)' == 'true'">false</UseNativeAotForComponents>
Copy link
Member

@am11 am11 Jun 14, 2024

Choose a reason for hiding this comment

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

Please move it next to

<UseNativeAotForComponents Condition="'$(NativeAotSupported)' == 'true' and '$(TargetOS)' == '$(HostOS)' and ('$(TargetOS)' != 'windows' or '$(TargetArchitecture)' != 'x86')">true</UseNativeAotForComponents>

The whole point was to control it centrally.

Copy link
Member Author

Choose a reason for hiding this comment

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

It's a local workaround for a problem in this project file, as opposed to global statement.

Publishing for bionic is supposed to be supported for components but this project needs to configure it, like it's doing in the lines above for other crossbuilds (at minimum, set PublishAotUsingRuntimePack). I could have tried to fix it but official builds are failing and it was blocked before #103273 so I don't feel bad just blocking it "for now".

I'll move it so it doesn't conflict with #103375 but it will be in the wrong spot now given the state of main and I haven't made my mind if it will be in wrong spot after that PR still (the workaround is too detached from where the problem is).

@dotnet-policy-service dotnet-policy-service bot added the linkable-framework Issues associated with delivering a linker friendly framework label Jun 14, 2024
@MichalStrehovsky MichalStrehovsky merged commit d901213 into main Jun 14, 2024
142 of 148 checks passed
@MichalStrehovsky MichalStrehovsky deleted the MichalStrehovsky-patch-2 branch June 14, 2024 08:55
MichalStrehovsky added a commit to MichalStrehovsky/runtime that referenced this pull request Jun 14, 2024
MichalStrehovsky added a commit that referenced this pull request Jun 15, 2024
* Revert "Do not set UseNativeAotForComponents for arm32 MUSL (#103469)"

This reverts commit f1f0750.

* Revert "Set UseNativeAotForComponents to false on bionic (#103454)"

This reverts commit d901213.

* Revert "Try fixing x86 Windows legs (#103411)"

This reverts commit 6927fea.

* Revert "Consolidate <NativeAotSupported definitions (#103273)"

This reverts commit b86c463.
@github-actions github-actions bot locked and limited conversation to collaborators Jul 16, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-Infrastructure-libraries linkable-framework Issues associated with delivering a linker friendly framework
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants