On 01/17/03 Martin Baulig wrote: > > On 01/16/03 Martin Baulig wrote: > > > Such a libbfd.so doesn't depend on any non-shared libraries and thus it can be > > > dlopen()ed - that's what the debugger needs. > > > > Why can't the debugger link directly to the library? > > Because that'd require the JIT being linked statically against -liberty.
Bzzzt, wrong answer! :-) Why should the rest of the world adapt to the needs of the debugger? Do the simple thing instead. What if the debugger becomes an unmanaged application? It can embed the mono runtime and continue using C# code for the interface and it would have no problem linking with static libiberty and libbfd (the functions there would be exposed to the managed world with internalcalls). And you wouldn't need to build and distribute three dynamic libraries (libmonodebuggerbfdglue, libmonodebuggerglue and libmonodebuggerserver). Less dependencies and easier build setup: looks like a net win to me. lupus -- ----------------------------------------------------------------- [EMAIL PROTECTED] debian/rules [EMAIL PROTECTED] Monkeys do it better _______________________________________________ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
