You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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 settingLD_LIBRARY_PATH
).Has this come up before? Would you be interested in this as a pull request?
The text was updated successfully, but these errors were encountered: