Was the binary you were trying to start in "bin"? DLL search path on Windows: https://msdn.microsoft.com/en-us/library/7d83bc18.aspx https://msdn.microsoft.com/en-us/library/windows/desktop/ms682586(v=vs.85).aspx (see Standard Search Order for Desktop Applications section)
Just leaving it in "lib" won't let the app find it unless "lib" is in %PATH%. I am not aware of a search path being embeddable into the .exe like on other platforms; safest bet is to ship the DLL right next to the executable. We might be able to hack something together for Vista+ systems and SetDefaultDllDirectories(), but it's probably not worth it. On Sun, Nov 19, 2017 at 1:10 PM Riccardo Mottola <riccardo.mott...@libero.it> wrote: > Hi, > > On 12/11/2017 20:15, Fred Kiefer wrote: > > Version 52 had issues, By trying version 55 I was able to compile base ! > > However, when launching any app, I get a popup saying that "icuin55.dll is > missing from your computer". > > But it successfully linked without any additional flags... hmm? What could be > the trick? > > That sounds like the lib file needed for linking is present but the dll using > when running is missing or corrupt. > > > I "fixed" the issue by copying the .dll from "lib" to "bin" and things > work again. I noticed that the old 46 ICU I had had DLLs in bin. > I wonder if this is a change in ICU's build system or already back then > our install was "tricked". > > This means however that at least a partial update of our MSYS evironment > can be planned, the tricky part will be put things together and make an > installer. > > > Riccardo > _______________________________________________ > Gnustep-dev mailing list > Gnustep-dev@gnu.org > https://lists.gnu.org/mailman/listinfo/gnustep-dev >
_______________________________________________ Gnustep-dev mailing list Gnustep-dev@gnu.org https://lists.gnu.org/mailman/listinfo/gnustep-dev
