Petit Eric wrote: > 2008/4/16, StApostol <[EMAIL PROTECTED]>: > >> I sent an email on the very same topic a few days ago, but it seems it never >> arrived :/ >> >> >> >> What if the project is a class library? There's no startup script in that >> case, unless you move that burden to the consumers of your library (which is >> not really nice or developer friendly). >> >> > in fact i spoke about linux native library (.so) not windows/mono one (.dll) > Please re-read my email, it is talking about a native .so, too :-)
If I understand correctly, you suggest writing a script that sets LD_LIBRARY_CONFIG and then executes your Mono executable, correct? My objection is that this approach won't work when your Mono project is a class library and not an executable. The unmanaged dependency (.so) is still there, but there's no startup script to set the correct path in this case. Placing a dll.config in ~/.mono/assemblies could be a valid workaround - I'm going to test this a little more and report a bug (if indeed there is one). Any other suggestions? _______________________________________________ Mono-list maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-list
