> Can someone tell me why when I build GLIB 2.12, it creates libraries of > version 2.0?!? What do you mean with "version 2.0"? The "2.0" that is part of the shared library file name is not a "version" of the file. It's just part of the file's name. Sure, the "2.0"of course is inspired by a version, but it is not as strictly coupled to the version of the source code as you seem to think. It could just as well be the string "two", for instance. (In fact, it might have been a good idea to avoid the "2.0" part of the shared library file names, and use something more subtle like "two" instead, exactly to avoid misunderstandings like yours.) > Now, correct me if I'm wrong, but shouldnt the version numbers be 2.1.2, not 2.0? Nope. The part of the file name up to the ".so" on ELF systems (on Windows the whole file name of the DLL) stays the same for all versions that maintain backward API and ABI compatibility. And the GTK+ stack takes API and ABI stability seriously. That means, if some executable has been built against GLib 2.10, for instance, and links to the shared library libglib-2.0-0.dll (on Windows, as an example), it will work as well against builds of GLib 2.12, 2.14, 2.16 and (the upcoming) 2.18, which all provide an identically named shared library. --tml _______________________________________________ gtk-list mailing list gtk-list@xxxxxxxxx http://mail.gnome.org/mailman/listinfo/gtk-list
