Providing the full path to the library will permit compiling the program. However, it does not solve runtime problems. For example, if I move Qt.dll from into /tmp, "mcs -r:/tmp/Qt.dll test.cs" will succeed, but "mono test.exe" will fail because the runtime will not find the Qt.dll assembly.
Setting MONO_PATH=/tmp will permit the runtime to find the assembly. (I'm not recommending installing libraries in /tmp. It's just an example of moving a library to a place that the runtime does not normally check for libraries.) On Wednesday 07 July 2004 9:35 pm, Peter Williams wrote: > Fooling with MONO_PATH is one way to get this to work, but I think the > preferred solution is to give the /r: option a full path name. That is, > > mcs /r:/usr/local/lib/Qt.dll > > or whatever. This is, for example, what the gtk-sharp pkgconfig files > do. This method means path problems don't come up and multiple versions > of the same library are handled sanely. _______________________________________________ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
