* Bob Rossi wrote on Fri, Mar 28, 2008 at 12:47:25AM CET: > > I want to copy /c/mingw/bin/mingwm10.dll to my bin dir yes. After I do > the make install, I will then use something like NSIS to take the > install dir and make some sort of installation package for windows. > > > Why in the world would you want to do that? And if you really want > > to copy that file somewhere, why do you not just keep it as part of > > your distribution tarball? > > The problem is, you can't run a mingw application on windows that > does not have mingwm10.dll installed if the mingw application uses > threads and exceptions.
That doesn't explain why you aren't just shipping mingwm10.dll along with you distribution tarball, and copying it from there. > > And yes, apart from it looking like a weird thing to try in the first > > place, here's a bunch more reasons against the above: > > I hope it doesn't seem wierd now. I have to give the user the > mingwm10.dll, so, I think it should be installed. Or simply list a MinGW installation as dependency of your package. > > - on my w32 system, mingwm10.dll lives in another place (in fact, it > > happens not to, but it easily could), > > I know, I don't know what to do about this, besides write a macro to > find it, that will come next if needs be. See above, you could just ship it. > > - on my GNU/Linux, the library does not exist, but there is an import > > library libmingw32.a which I think can be linked against, > > My linux version of this program does not need the library, as I simply > use the normal gcc, not the mingw version. Perhaps the version on linux > you are looking for is for cross compiling? Yes, I meant cross-compiling. Sorry for not stating that up front. Cheers, Ralf
