GNOME Bugzilla – Bug 587282
glade installer does not create a good shortcut
Last modified: 2011-01-14 19:17:03 UTC
The shortcut to glade3 executable does not set the current directory and the application fails to start because it does not find libglade library. Also regarding accessibility, the installer should add glade3 to the path or better to add an glade3.cmd to the python scripts directory that would start the glade3 from the command line. Other information:
Glade doesnt have an installer on win32. Moving this bug as a duplicate of the bug where we're currently tracking status on making a proper build script for win32 platform. (fyi, Glade binaries on win32 have been created by a handful of sources, just no real official build scripts for win32 are included in glade's repositories... yet). *** This bug has been marked as a duplicate of bug 634978 ***
Apologies for commenting on a closed bug report, but I get a feeling it was about the glade3 binary included in the PyGTK All-in-one installer. If you meant the glade3 installer on http://ftp.gnome.org/pub/GNOME/binaries/win32/glade3/3.6/, then I sorry for the noise... 1) shortcut working directory: if you meant it as a "hey, Gimp puts %USERPROFILE%" as the working directory for it's shortcut" then yeah, I seem to have overlooked that. Will be fixed in the next version of the PyGTK All-in-one installer :) If however you mean this as a fix for a broken windows installation (dll load failed errors) then I need to ask: did you put the GTK+ runtime/bin directory on PATH? Please don't do that and read 2) below. Fixing your system involves removing *all* directories that contain a (or parts of a) GTK+ runtime from your PATH environment variable. Dependency walker (depends.exe) can be a great help to hunt those down. 2) add glade3 to the path: I'll need to disappoint you as there is no need whatsoever to add a GTK+ runtime's bin directory to the PATH environment variable on a correctly configured windows system. It is even dangerous to do so as it introduces an uncontrollable environment: some badly written (in my opinion) windows specific software installers like Lua, Graphviz, GTK-sharp, etc. all rely on a specific (their own) GTK+ version's runtime bin directory to be on PATH. Adding ours (GTK+-2.22) to the mix would most likely break those packages as: - a lot of software out there still depends on GTK+-2.16 and - those packages rely on PATH to resolve GTK+ runtime dll's instead of correctly having both their executables and dll's in the same directory. Read http://msdn.microsoft.com/en-us/library/ms682586%28v=vs.85%29.aspx for more info on windows' dll search order. Everything that does not rely on option 1 (The directory from which the application loaded) from that page is simply broken. 3) glade3.cmd script in Python's Scripts dir: Thanks! Good idea, a glade3.cmd script will be available in Python's Scripts dir in the next version of the PyGTK all-in-one installer (2.22.6).