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

Support for non-standard mono installation path #179

Open
puremourning opened this issue Feb 9, 2015 · 1 comment
Open

Support for non-standard mono installation path #179

puremourning opened this issue Feb 9, 2015 · 1 comment

Comments

@puremourning
Copy link

Due to various version compatibilities and standard server builds I was not able to get a system mono installation on RHEL 6 which can support OmniSharpServer.

So, following the instructions on mono's web page I built mono from source and installed it in a custom location (e.g. $HOME/opt/mono). However, OmniSharpServer was unable to start. This is because OmniSharpServer contains hard-coded paths to search.

I have a local modification to Project::FindAssembly this which checks for the presence of a hierarchy of environment variables (OMNISHARP_LIBRARY_PATH, LD_LIBRARY_PATH,DYLIB_FALLBACK_LIBRARY_PATH) and appends a series of suffixes (mono/4.5, mono/4.0, etc.) to search for the requested assembly. This allowed me to use mono in a non-standard path by following the instructions on mono's website (they suggest setting LD_LIBRARY_PATH).

Has this come up before? Would you be interested in this as a pull request?

@nosami
Copy link
Contributor

nosami commented Feb 10, 2015

Yes, it has come up before, and yes, I would be interested in a pull request!!

Bear in mind though that this project is almost obsolete (to be replaced with https://github.com/OmniSharp/omnisharp-roslyn). I think your problem isn't an issue there.

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