I was under the mistaken impression that SetDllDirectory *added* additional paths, not just replace a single path. I will need to potentially add multiple search paths, so I don't think SetDllDirectory() will work anyway.
In light of that, do you think adding each path to the PATH (or LD_LIBRARY_PATH) evn var is the right way to handle this? On Fri, Jul 31, 2009 at 11:01 AM, Rom Walton <[email protected]> wrote: > There isn't an API at the moment that does that. > > Although it does sound like a good idea, the diagnostics framework > already makes use of SetDllDirectory() for finding the desired DLLs for > dumping call stacks. Any additional calls to it without adding the > original paths to it would break the diagnostic framework. > > ----- Rom > > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of Jeremy Cowles > Sent: Friday, July 31, 2009 1:54 PM > To: [email protected] > Subject: [boinc_dev] Setting DLL search paths > > I'm looking for something that would either call SetDllDirectory() or > add > the given path to the LD_LIBRARY_PATH. > > Does the BOINC API expose such a function? > > My motivation is this: while attempting to automatically load Python > modules, I have a bunch of directories where libs(dll/so/pyd) are > placed. > These files can't be dumped into the executable directory because of > possible file name collisions. > > Thanks, > Jeremy > _______________________________________________ > boinc_dev mailing list > [email protected] > http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev > To unsubscribe, visit the above URL and > (near bottom of page) enter your email address. > _______________________________________________ boinc_dev mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
