[fpc-devel]Just joined

[Michael A. Hess]

> > You can't do that. The new Win32 GTK libraries that you indicate
> > above are the latest versions for Win32. They are interdependent
> > and require that they maintain the names they currently have. The
> > only way to use these new libraries is to build a new version of
> > the GTK unit in the FCL to look for these new library names.
> 
> :/
> 
> The ever-present library versioning and naming problems :/
> What is the logic behind naming it g*k-0.dll if the version is 1.3 ??
> Probably they don't want these libs in production - so only people
> compiling everything anew should use these libs ?
> 
> It means that existing programs cannot enjoy the benefits of newer,
> fixed libraries ? Nice going  :/  Even Microsoft doesn't do that !
> (Well, not often ;))

Here is the statement right from the GTK+-Win32 site.


GLib 2.0 has been released. GIMP and GTK+ thus now depend on those 
DLLs. The GLib 2.0 DLL names will not change, even if GLib 2.0.1, 2.0.2 
etc are released, as these releases will be binary compatible. (The 
GLib 1.3.x series were development versions, and thus by definition 
without any promise of binary compaibility, which has meant that each 
version has had differently named DLLs.) 



--
==== Programming my first best destiny! ====

Michael A. Hess      Miracle Concepts, Inc.
mhess at miraclec.com   http://www.miraclec.com