At 01:33 AM 10/24/2001 -0700, Andrew Begel wrote:
module-load-path works for finding the dll that load-module() loads,
but
doesn't handle any dependent DLL libraries that are linked into the dll.
Basically, our project has an XEmacs DLL external module which is
dependent on a few DLLs that we provide; but we need to put these DLLs
into the PATH so that the dlopen() of the external module DLL succeeds.
Otherwise you get a nice dialog box from Windows stating that it couldn't
find such-and-such.dll in the PATH.
We could modify setenv to take an optional boolean arg that would indicate
whether this change affects the Xemacs process, or just subprocesses.
Default would be false, and just affect the subprocesses (the current
behavior). True would cause a change to the XEmacs process as well as
causing XEmacs to reload that environment variable into the lisp variable
for the environment.
One of the things I've been considering for a while is writing lisp
primitives that allow you to manipulate the windows registry. This would
then allow you to muck with AppPaths under windows which I think would
achieve what you want. Windows-specific though...
andy