I would be careful in replacing all the PULONG as "guint32 *" (and all the 
other P... types).
PULONG is defined with a typedef as something like

typedef unsigned long *PULONG;


If you have line like this

PULONG a, b;

the sostitution would return

guint32 *a, b;

which is wrong.

Also, HANDLE and HMODULE can be safely defined as void pointers, not 
pointers to pointers.

Hope it helps
GV


----- Original Message ----- 
From: "Joerg Mayer" <[email protected]>
To: <[email protected]>
Sent: Monday, May 11, 2009 11:55 AM
Subject: [Wireshark-dev] Making wireshark compile with have_airpcap


> Hello,
>
> I've finished making Wireshark compile and Link  on Linux 
> with --enable-airpcap
> Most of the stuff has already been committed, except for the type 
> conversions.
> As I'm no expert on Windows types, Ive decided to attach the script that 
> I'm
> using to fix the following files:
> airpcap_loader.c
> airpcap_loader.h
> airpcap.h
> gtk/airpcap_dlg.c
>
> Please have a lok at these conversions and let me know how they should 
> actually
> look like.
>
> Thanks
>        Joerg
> -- 
> Joerg Mayer                                           <[email protected]>
> We are stuck with technology when what we really want is just stuff that
> works. Some say that should read Microsoft instead of technology.
>


--------------------------------------------------------------------------------


> ___________________________________________________________________________
> Sent via:    Wireshark-dev mailing list <[email protected]>
> Archives:    http://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
>             mailto:[email protected]?subject=unsubscribe 

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <[email protected]>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:[email protected]?subject=unsubscribe

Reply via email to