Ühel kenal päeval, K, 19.09.2018 kell 08:58, kirjutas David Haller: > Hello, > > On Wed, 19 Sep 2018, Andrew Udvare wrote: > > Curiosity: what is the reason for wxGTK:3.0 and wxGTK:3.0-gtk3 ? > > wxGTK:3.0 uses gtk+-2 and wxGTK:3.0-gtk3 uses gtk+-3.
That, and we couldn't do it with just flipping it to gtk3 in 3.0 SLOT, because some wxWidgets apps could be doing conditional direct GTK+ code as well, to go above the lowest common denominator toolkit support that wxWidgets provides. Or some might just be wrongly linking directly to gtk2 explicitly. Or had too much trouble with gtk3 in the less used parts of wxGTK while wxGTK gtk3 support hadn't quite matured yet. You can't have a program load in (link to) both gtk2 and gtk3 - it will abort to not go completely runtime crazy and crash due to same function names. Kind of like wxWidgets itself aborts if the library and app are using different C++ ABI (however that's less of a problem with todays relevant C++ ABI updates, unlike the gcc4 to 5 days). Therefore it was just a separate parallel installable SLOT with which we could move things over gradually and have the more maintained apps benefit before everything is working with it. Mart
signature.asc
Description: This is a digitally signed message part
