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

[release/8.0-staging] [workloads] Don't load mono librarymode targets if PublishAot is set #103817

Merged

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Jun 21, 2024

Backport of #103777 to release/8.0-staging

/cc @steveisok

Customer Impact

  • Customer reported
  • Found internally

Customers who want to create native static or shared libraries (aka library mode) for nativeaot targeting ios and android are blocked by an msbuild check in the mono workload target. This check assumes if you set the NativeLib property that you want mono's version of library mode and it will error out telling you to install a specific workload.

The fix adds an additional check for PublishAot != 'true' to prevent the error message from appearing when the customer wants nativeaot.

Regression

  • Yes
  • No

[If yes, specify when the regression was introduced. Provide the PR or commit if known.]

Testing

Tested a local project that was able to produce a native library

Risk

Low

IMPORTANT: If this backport is for a servicing release, please verify that:

  • The PR target branch is release/X.0-staging, not release/X.0.

  • If the change touches code that ships in a NuGet package, you have added the necessary package authoring and gotten it explicitly reviewed.

This change removes the incorrect error message when you using NativeAOT library mode
on mobile and you have `<NativeLib>` set. Previously, it would only detect if `<NativeLib>` was
set and error out if you didn't install the library builder workload. That only applies if mono
is your target.
Copy link
Contributor

Tagging subscribers to this area: @directhex, @matouskozak
See info in area-owners.md if you want to be subscribed.

@steveisok steveisok added the Servicing-consider Issue for next servicing release review label Jun 21, 2024
Copy link
Member

@jeffschwMSFT jeffschwMSFT left a comment

Choose a reason for hiding this comment

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

lgtm. we will take for consideration in 8.0.x

@jeffschwMSFT jeffschwMSFT added this to the 8.0.x milestone Jul 2, 2024
@rbhanda rbhanda modified the milestones: 8.0.x, 8.0.8 Jul 2, 2024
@rbhanda rbhanda added Servicing-approved Approved for servicing release and removed Servicing-consider Issue for next servicing release review labels Jul 2, 2024
@steveisok steveisok merged commit 3391cba into release/8.0-staging Jul 2, 2024
24 of 31 checks passed
@steveisok steveisok deleted the backport/pr-103777-to-release/8.0-staging branch July 2, 2024 17:56
@github-actions github-actions bot locked and limited conversation to collaborators Aug 2, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants