ANNOUNCEMENT: Live Wireshark University & Allegro Packets online APAC Wireshark Training Session
April 17th, 2024 | 14:30-16:00 SGT (UTC+8) | Online

Wireshark-dev: Re: [Wireshark-dev] SVN 23396 build failure on Windowswith epan/prefs.c

From: "Maynard, Chris" <Christopher.Maynard@xxxxxxxxx>
Date: Wed, 7 Nov 2007 21:29:33 -0500
I believe the gtk.h file on Windows comes from C:\wireshark-win32-libs\gtk2\include\gtk-2.0\gtk\gtk.h.  I was trying to find other dissectors or files that include gtk.h to see how they handle it, but a quick grep of gtk.h in epan\*.c produced only this single hit. 

________________________________

From: wireshark-dev-bounces@xxxxxxxxxxxxx on behalf of Stephen Fisher
Sent: Wed 11/7/2007 9:16 PM
To: Developer support list for Wireshark
Subject: Re: [Wireshark-dev] SVN 23396 build failure on Windowswith epan/prefs.c



On Wed, Nov 07, 2007 at 08:51:11PM -0500, Maynard, Chris wrote:

> prefs.c(54) : fatal error C1083: Cannot open include file:
> 'gtk/gtk.h': No such file or directory

Thanks for the notification, I see the Windows buildbot doesn't like
that line either.  I don't have a Windows development environment
anymore to test in, do you or anyone else have any idea why including
gtk/gtk.h from epan/prefs.c doesn't work on Windows?  I know it's
"unnatural" since it isn't in the gtk/ directory.  However, it works
fine on Unix.  I need GTK's gtk.h to use the GTK_CHECK_VERSION macro to
prevent the code from writing out a preference for the show toolbar
arrow when using GTK < 2.4.


Steve
_______________________________________________
Wireshark-dev mailing list
Wireshark-dev@xxxxxxxxxxxxx
http://www.wireshark.org/mailman/listinfo/wireshark-dev





-----------------------------------------
This email may contain confidential and privileged material for the
sole use of the intended recipient(s). Any review, use, retention,
distribution or disclosure by others is strictly prohibited. If you
are not the intended recipient (or authorized to receive for the
recipient), please contact the sender by reply email and delete all
copies of this message. Also, email is susceptible to data
corruption, interception, tampering, unauthorized amendment and
viruses. We only send and receive emails on the basis that we are
not liable for any such corruption, interception, tampering,
amendment or viruses or any consequence thereof.

<<winmail.dat>>