On 04/03/14 17:23, Edward Ned Harvey (mono) wrote:
From: mono-devel-list-boun...@lists.ximian.com [mailto:mono-devel-list-
boun...@lists.ximian.com] On Behalf Of Andrés G. Aragoneses
As far as I understand, LD_LIBRARY_PATH is a system setting that mono
doesn't modify.
Thanks for your
On 02/03/2014 13:54, Zoltan Varga
wrote:
Hi,
mono requires an existing mono installation to work, and
will only fall back to monolite if it is missing. If you want
it to use monolite, then remove the existing mono
From: mono-devel-list-boun...@lists.ximian.com [mailto:mono-devel-list-
boun...@lists.ximian.com] On Behalf Of Andrés G. Aragoneses
Right, LD_LIBRARY_PATH may be simply a fallback. But the thing is, you
don't need LD_LIBRARY_PATH when installing libs in standard prefixes
like /usr or
On 05.03.2014 15:31, Edward Ned Harvey (mono) wrote:
It is a safe conclusion to draw, that *whatever* is specified by
--libdir=DIR, the binary should be linked against libraries in that
directory. (If not specified, libdir is derived from
--exec-prefix=EPREFIX, which is derived from
Yes, this should probably not change on windows due to .net.
On Tue, Mar 4, 2014 at 3:12 PM, Charlie Poole char...@nunit.com wrote:
Can I assume this only applies to Linux? In the past, when I used
Process.Create
from a Mono app on Windows, the secondary process ran under MS .NET.
From: mono-devel-list-boun...@lists.ximian.com [mailto:mono-devel-list-
boun...@lists.ximian.com] On Behalf Of Robert Jordan
Non-default Mono installations still need LD_LIBRARY_PATH, otherwise
p/invoke of Mono libraries (libgdiplus, libMonoPosixHelper) won't
work because p/invoke is
From: mono-devel-list-boun...@lists.ximian.com [mailto:mono-devel-list-
boun...@lists.ximian.com] On Behalf Of Edward Ned Harvey (mono)
So ... http://blog.tremily.us/posts/rpath/
Actually, the answer is right there - Thank you, Trevor and Emily (tremily).
This works perfectly:
export
