We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
FWI I believe xtro's usage of objective-sharpie/Mono is the only reason we still need Mono during our build (ref: #21411).
This can probably only be done once Objective-Sharpie has been ported to .NET.
The text was updated successfully, but these errors were encountered:
@rolfbjarne I could be wrong but wasn’t Sharpie self-contained? (About it using system mono)
Sorry, something went wrong.
I'm not sure I understand - Objective-Sharpie is self-contained, but our xtro tests consumes dylibs from Objective-Sharpie:
xamarin-macios/tests/xtro-sharpie/xtro-sharpie/xtro-sharpie.csproj
Line 41 in 25fa00f
and that won't work in .NET.
Ah right 🤦♂️ (needs more coffee)
No branches or pull requests
FWI I believe xtro's usage of objective-sharpie/Mono is the only reason we still need Mono during our build (ref: #21411).
This can probably only be done once Objective-Sharpie has been ported to .NET.
The text was updated successfully, but these errors were encountered: