Re: [xslt] [PATCH] xslt extensions as modules/dso's

[Joel Reed <joelwreed comcast net>]

On Tue, Dec 21, 2004 at 10:15:41PM -0800, Mark Vakoc wrote:

<snip>

> One of the problems I've always faced is win32 apps that decide it is proper to
> install their DLLs to the windows or windows\system32 directory, automatically
> pushing those higher in the LoadLibrary search path than I'd like.  (Note:  the
> LoadLibrary path lookup is complex and very OS dependent). 

<snip>

I would like to address this issue specifically. it seemed to me
that most projects with plugins or modules, have one or two application
specific directories from which they will load such plugins or modules.
this path is determined at compile time.

for example: 
  /usr/lib/gimp/2.0/modules/
  /usr/lib/apache/1.3/
 
i was planning on win32 to hack configure.js such that if you enable
modules, you would be warned/reminded that the "prefix" setting takes on
much greater importance in that it is used to construct the path from
which plugins or modules are loaded. i was envisioning perhaps even
requiring prefix to be set if you enable modules on win32.

jr