On Sun, Oct 26, 2008 at 3:25 PM, Armin Burgmeier <[EMAIL PROTECTED]> wrote: > On Sun, 2008-10-26 at 15:04 +0100, Murray Cumming wrote: >> On Sun, 2008-10-26 at 12:37 +0100, Armin Burgmeier wrote: >> > > > > > 1.2 >> > > > > > I thought that applications would find the DLLs because they are >> > > > > > in the >> > > > > > same directory. Why is something in the PATH environment variable >> > > > > > also >> > > > > > needed? I don't understand why MS Visual Studio would need it >> > > > > > either if >> > > > > > we are using these "property pages". >> > > > > >> > > > > MSVC++ does not need it to build stuff, but to run or debug from >> > > > > within >> > > > > the IDE. I'm not sure whether there is an option in MSVC++ to extend >> > > > > the >> > > > > DLL search path that the property pages could set, but I'll check. >> > > > >> > > > That sounds rather strange. Please do check. It would be nice to remove >> > > > the PATH change if possible. >> > >> > 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.
This is because Visual Studio runs the application with current directory = project directory (not the debug/release subdirectory). Regards, Michael _______________________________________________ gtkmm-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/gtkmm-list
