Windows x64 support
fridrich.strba at bluewin.ch
Thu Apr 29 10:13:35 PDT 2010
OK, this has just a sense for windows 64-bit and only for the
x86_64-*-mingw32 target, so whether there is stdint.h (which the
configure checks for already) or other header, that is more generic,
will not have a real impact on whether dbus will be buildable on LP64
On Thu, 2010-04-29 at 18:09 +0100, Simon McVittie wrote:
> On Thu, 29 Apr 2010 at 19:05:06 +0200, Thiago Macieira wrote:
> > Em Quinta-feira 29 Abril 2010, às 13:03:49, Ralf Habacker escreveu:
> > > stdint.h is not available on msvc < 2010
> > stdint.h is a C99 header, which Microsoft hasn't really decided to support.
> > How about inttypes.h?
> Replacing stdint.h with inttypes.h throughout is probably a good idea, assuming
> it exists on Windows:
> `inttypes.h' vs. `stdint.h'
> The C99 standard says that `inttypes.h' includes `stdint.h', so
> there's no need to include `stdint.h' separately in a standard
> environment. Some implementations have `inttypes.h' but not
> `stdint.h' (e.g., Solaris 7), but we don't know of any
> implementation that has `stdint.h' but not `inttypes.h'.
> -- autoconf.info, §5.6.1 "Portability of Headers"
> dbus mailing list
> dbus at lists.freedesktop.org
More information about the dbus