GTK+ depends on GLib, but not the other way around. The 64-bit OS X development packages currently ship with GLib and Qt but not GTK+.
On 11/3/13 1:53 PM, Roland Knall wrote: > I agree, but glib is still part of gtk. And as of now, the normal way > of installing glib would be to install gtk onto the system. So > basically you have two frameworks, and you will need both to develop > for ws from now on. I am not trying to change anything here, and I > accept that as of right now, no change is necessary. But as long as > new dissectors are integrated, new code is being written, everything > in the main libraries is being based on glib. And gradually changing > something from here on out seems to be a petter plan than to change > anything later in a rather short time-span. > > btw, I do not suggest changing to c++, I honestly do not know what the > target should be. > > regards, > Roland > > p.s.: I am fine with glib staying. Depend on some of the functionality > for my dissectors anyway. > > On Sun, Nov 3, 2013 at 10:42 PM, Gerald Combs <ger...@wireshark.org> wrote: >> On 11/3/13 12:54 PM, Roland Knall wrote: >>> Hi >>> >>> Just a short question. If the long-term goal is to switch to Qt, what >>> ist the long-term plan for glib? As of now, many dissectors use the >>> data types, tables, etc. >>> >>> Should they be replaced with Qt calls, default datatypes (e.g. guint16 >>> => uint16_t, ...) ? >>> >>> What is the course here? >> >> I don't think GLib will go away any time soon. It provides a lot of >> useful functionality and as you point out Wireshark uses it all over the >> place. It also doesn't require switching anything outside of ui/qt to C++. >> ___________________________________________________________________________ >> Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org> >> Archives: http://www.wireshark.org/lists/wireshark-dev >> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev >> mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe > ___________________________________________________________________________ > Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org> > Archives: http://www.wireshark.org/lists/wireshark-dev > Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev > mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe > ___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org> Archives: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe