-
-
Notifications
You must be signed in to change notification settings - Fork 33
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
Support OSX #187
Comments
See also #141 |
Since the Slack discussion may not be accessible to everyone (e.g., any open-source contributors who might find this), here's the important parts from the discussion: Relevant code from source/icu.net/NativeMethods/NativeMethods.cs:
Relevant comment from Slack discussion:
It looks like #142 was an attempt to fix this issue, but didn't completely solve it. sillsdev/TheCombine#927 is probably caused by this as well. |
@rmunn I was hoping to try out a fix on my mac: master...imnasnainaec:icu-dotnet:mac ...but I'm not sure how to build on/for macOSX to test it out. (Attempting: #188) |
@ermshiperete What is the state of this issue? |
At least for its use in The Combine, the current hurdle is getting |
One issue I've discovered is that depending on how you installed icu4c, the installed One thing that might help is https://github.com/sickcodes/Docker-OSX which builds off the work done by https://github.com/kholia/OSX-KVM. Running Mac OS in a Docker container might allow automated testing, so we can make sure icu.net can find the libraries in all common install scenarios. |
For Platform.Bible we bundle in the icu4c libraries along with our application builds so we don't have to worry about this. Since OSX doesn't provide them we assume we can't rely on them being anywhere in the path. |
macOS uses
dylib
files instead ofso
and the file pattern islibicuuc.[version].dylib
instead oflibicuuc.so.[version]
, so our current approach for loading unmanaged ICU doesn't work.The relevant code is in
source/icu.net/NativeMethods/NativeMethods.cs
.See discussion on Slack.
The text was updated successfully, but these errors were encountered: