On Sun, 2008-10-26 at 15:25 +0100, Armin Burgmeier wrote: [snip] > > > I checked. I was wrong. When running out of the IDE, the PATH variable > > > doesn't need to be set to the gtkmm DLL directory. It's only required > > > when running it outside the IDE. > > > > I thought we were all sure that the DLLs were found by them being in the > > same directory as the executable? I am now confused. > > The executable is only in the same directory as the gtkmm DLLs when the > application is distributed with an installer or a zip file. This works > without problems. > > However, by default, when building an application, the executable is > created into debug/ and release/ subdirectories in the project's > directory, where the gtkmm DLLs normally aren't. Running it from that > location does not work when running it from outside the IDE.
I think that's OK. I think we should just document that. So, I think we can remove the PATH stuff from the installer. ]snip]h > > > So if we want to avoid the PATH change, should we just drop the runtime > > > installer? I thought we needed the runtime installer to provide the stripped mingw DLLs. > Or, should we only set the PATH variable in the runtime > > > installer, but not in the development one, without further asking the > > > user? I don't think we should set it in either one. Relying on PATH settings is just an invitation to confusing problems. I'd rather just have a .zip file containing those stripped MinGW DLLs and not have an actual runtime installer. -- Murray Cumming [EMAIL PROTECTED] www.murrayc.com www.openismus.com _______________________________________________ gtkmm-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/gtkmm-list
