Not that I am trying to squash the use of dlls here, but I'm not sure you
are following me.
Why would the dll in the directory with the php5ts.dll take precedence
over another version of the lib somewhere else?
For instance, under apache, some other module is loaded first that also
happens to use libxml2.dll (and happens to include it within its
directory). If this module gets loaded before PHP, what would the search
order for the dll be then. I assume its own directory and then the windows
directories. PHP would then end up using the other dll (already being
loaded into the apache space) and not the one in its own directory. Same
would then hold true for the iconv, etc.. CLI on the other hand would (at
least should) always use the one within the PHP directory.
Rob
That was happening for me with the mysql extension. I had the mysql dir in
the path and php was loading the libmysql.dll from there. The result? a nice
crash on startup.
This happened because the mysql dir was before of the php dir on the path.
Anyway, I might see the need to move some librarys to dlls.
Nuno
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
