Re: Standarization WAS: gtk-devel & gtk-runtime:InnoSetup packages for MinGW/Win32
"Bill Nalen" <[email protected]> Mon, 27 Jan 2003 09:17:52 -0500
| Newsgroups | gmane.comp.video.gimp.windows.devel |
|---|---|
| Message-ID | <OF80B29144.C5E3FE93-ON85256CBB.004E40DA-85256CBB.004E8A75@towers.com> |
>>and to provide >>a windows register mechanism that allows the gtk dependent application >>to dynamically link to their preferred version. >... but this sounds like a call for breaking it. Why put stuff into >the registry when every Gtk+ DLL does find itself and related >configuration from the place where it is located ? The GTK+ dll's will find each other from the relative directories. However it's finding the top level bin and lib directories that is the problem. I'd rather not have to add those two directories to my path. You can set a registry key for an application specific path addition though. That's what I do in my installer. It just looks in the registry for the GTK item and retrieves the path it was installed to. It then uses this path to set additional path items for the bin and lib directories for my application. The GTK+ installation only adds two keys to the registry, one for the version and one for the path. They are not used by the GTK+ dll's as far as I can tell. It's only a way for other applications to find the GTK+ installation directory. Bill