On Tue, Apr 27, 2010 at 4:05 PM, Guy Harris <[email protected]> wrote: > > On Apr 27, 2010, at 12:37 PM, Jeff Morriss wrote: >> But: would the header files have to be different? Linux and Solaris >> seem get away with one set of header files for both the 32- and 64-bit >> libraries. > > I'm not sure how they handle 32-bit vs. 64-bit GLib, given that the 64-bit > /usr/local/lib/glib-2.0/include/glibconfig.h installed on my machine has > #defines and typedefs such as
My FC 10 system has multiple copies of that file in different directories: /usr/lib/glib/include/glibconfig.h /usr/lib/glib-2.0/include/glibconfig.h /usr/lib64/glib/include/glibconfig.h /usr/lib64/glib-2.0/include/glibconfig.h > but you couldn't handle the GLIB_SIZEOF_ definitions without #ifdefs. They > might either manually, or with a tool that makes "fat" versions of header > files given two different versions of the header file for different > platforms, do it with #ifdefs, or they might have different include > directories for 32-bit and 64-bit. OS X doesn't support different include > directories for 32-bit and 64-bit, so that option isn't open to OS X. ... but apparently that won't work with OS X. ___________________________________________________________________________ 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
