-
Notifications
You must be signed in to change notification settings - Fork 26
Using a relocated Mono #27
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
Comments
This web page
describe the C API functions from |
Contributions are welcome. The project that does the loading of libmono is https://github.com/pythonnet/clr-loader. The loading is implemented in https://github.com/pythonnet/clr-loader/blob/master/clr_loader/mono.py, if you need additional API functions you can add their signature in https://github.com/pythonnet/clr-loader/blob/master/clr_loader/ffi/mono.py. |
OK, I will endeavor to do this. I am wondering if setting an environment variable to the relocated mono is the way to go. If that environment variable is set, call the mono C API routines for setting up mono for its new location, and if not, don't call those routines |
If I see this correctly, this is really just a matter of calling |
Agreed, I had determined that using |
Environment
Details
mono
I built from source (in preparation for embeddingmono
in a product) and got thisMy understanding is
mono
can be relocated, but it requires invoking their C API to set the assembly paths, etc...It would be nice if
clr-loader
could enable this by calling the right functions fromlibmono-2.so
I found this problem after relocating
mono
by runningecho "import clr" | python3
The text was updated successfully, but these errors were encountered: