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

Port xtro to use .NET instead of Mono #21573

Open
rolfbjarne opened this issue Nov 4, 2024 · 3 comments
Open

Port xtro to use .NET instead of Mono #21573

rolfbjarne opened this issue Nov 4, 2024 · 3 comments
Milestone

Comments

@rolfbjarne
Copy link
Member

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.

@dalexsoto
Copy link
Member

dalexsoto commented Nov 4, 2024

@rolfbjarne I could be wrong but wasn’t Sharpie self-contained? (About it using system mono)

@rolfbjarne
Copy link
Member Author

@rolfbjarne I could be wrong but wasn’t Sharpie self-contained? (About it using system mono)

I'm not sure I understand - Objective-Sharpie is self-contained, but our xtro tests consumes dylibs from Objective-Sharpie:

<LibClangMonoPath Condition="'$(SHARPIE)' == 'sharpie' or '$(SHARPIE)' == ''">/Library/Frameworks/ObjectiveSharpie.framework/Versions/Current/bin/libclang-mono.dylib</LibClangMonoPath>

and that won't work in .NET.

@dalexsoto
Copy link
Member

Ah right 🤦‍♂️ (needs more coffee)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants