So, my understanding on reading
http://msdn.microsoft.com/en-us/library/ms682586%28v=vs.85%29.aspx
is that there isn't a way to skip/override searching first in
"The directory from which the application loaded." which I believe means
that...
PATH=/local/bin:/path/to/solver/bin && /path/to/solver/bin/cppunit
something
will cause efforts by something to use LoadLibrary to actually search
first in "/path/to/solver/bin/" seeing as that's where cppunit
physically lives, and not first in "/local/bin" for any .dll "something"
might want to load subsequently.
Which I reckon means that cppunit tests the old "delivered" .dll in
those circumstances and not the local, just-built one. Which is where
failures windows people see that non-windows people don't see are likely
often coming from.
Its a bit of a nuisance, anyone know a good workaround/fix. What comes
to mind for me is to deliver cppunit not into the normal solver/bin dir,
but into e.g. solver/bin/other or something so that it isn't in the same
dir as the delivered .dlls and so will have to rely on PATH to find
them, and so get the expected ones.
Thoughts from the windows people ?
C.
Context
- [Libreoffice] windows dll search order and cppunit · Caolán McNamara
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.