|
Hi,
Is the following comment an
issue?
"For
software developers I would suggest that unless you need to use 2.6-only
features, you continue to build against GLib and GTK+ 2.4 headers and
libraries, even if the run-time environment will be 2.6. Only if you use
2.6-only API build against 2.6, and in that case, remember to use the
gstdio wrappers: replace all fopen() calls with g_fopen(), etc."
Otherwise I
tink it's probably a good idea as I think some of the known bugs are solved
there.
Brg
Anders
List,
I would like to request that we move to GTK 2.6 in our Windows builds.
The reason for this is compatibility with newer GTK themes which rely on GTK
2.6 or higher. By moving to this version we can allow Windows users to easily
change the default GTK theme. All users would need to do is download the
desired theme and then copy the files to the /share and /lib
directories.
Moving forward this functionality could be added through configuration
settings in Ethereal to allow better customization of the GUI. Or even perhaps
custom skins?
I have tested the latest SVN on Windows with the following updated
packages and have not experienced any issues. Comments?
atk-1.9.0.zip
atk-dev-1.9.0.zip
glib-2.6.5.zip
glib-dev-2.6.5.zip
gtk+-2.6.8.zip
gtk+-dev-2.6.8.zip
pango-1.8.0.zip
pango-dev-1.8.0.zip
Greg
| 
