Bob Friesenhahn <> wrote: > On Tue, 8 Jan 2008, Ralf Wildenhues wrote: >> >> General question before fixing this: on w32, should even plugins have >> their DLLs go to $bindir?
Yes, i'd agree to this... ;o) If you try to load a library by yourself, you will have to know what you're doing. If the DLL is linked to the executable, you have no (easy) way to influence what is done by the loader... Of course there may still be problems if there are dependencies between plugins, that are installed in different directories, since loading one plugin will load all libraries this dll is linked to. If those are plugins themselves, they will have to be in PATH to be found (or in the same directory, etc.). The easiest solution is using parity ;) but thats self-advertisement again, sorry... Cheers, Markus > > Plugin modules should be installed adjacent to the .la files in the > directory the user specifies since the plugin module should be loaded > directly without need to consult the PATH. Of course the .la file > needs to correctly reference the location of the plugin module. Only > general-purpose DLLs need to be installed in the executable search > path. > > Bob > ====================================== > Bob Friesenhahn > [EMAIL PROTECTED], > http://www.simplesystems.org/users/bfriesen/ GraphicsMagick > Maintainer, http://www.GraphicsMagick.org/ > > > > _______________________________________________ > http://lists.gnu.org/mailman/listinfo/libtool -- 19. - 21. Februar 2008 Salomon Automation auf der LogiMAT 2008, Neue Messe Stuttgart, Deutschland Halle 6, Stand 527 23. - 27. Februar 2008 MoveRetail auf der EuroShop 2008 in Dusseldorf, Deutschland Halle 6, Stand C50 Salomon Automation GmbH - Friesachstrasse 15 - A-8114 Friesach bei Graz Sitz der Gesellschaft: Friesach bei Graz UID-NR:ATU28654300 - Firmenbuchnummer: 49324 K Firmenbuchgericht: Landesgericht fur Zivilrechtssachen Graz _______________________________________________ http://lists.gnu.org/mailman/listinfo/libtool
