On Mon, Sep 19, 2011 at 04:39:14PM -0400, Andrew Stitcher wrote: > On Mon, 2011-09-19 at 16:23 -0400, Darryl L. Pierce wrote: > > I've enabled building QMF2 on Windows, but am stopped ATM due to > > the ambiguous usage of uint32_t and uint64_t. Developer Studio isn't > > used if the declarations want to use the boost:: or the Windows types. > > IIRC the uint32_t and uint64_t types have to be specially defined for > windows because they are not in the system header files (at least for > Dev Studio 2008). Is it possible that somehow the QMF2 build is picking > them up from multiple places?
The error I see is that the usage is "ambiguous" since, at compile time, DevStudio is seeing uint32_t in both the boost namespace (which is being used in the code) and also in qpid/sys/windows/IntegerTypes.h. > > It's very odd, since the same basic classes, such as AgentSession, > > compile fine under for QMF on Windows. > > I'm fairly sure that the QMF (v1) C++ code has been building on windows > for some time. Which is why I'm trying to find what's different with QMFv2 vs v1. -- Darryl L. Pierce, Sr. Software Engineer @ Red Hat, Inc. Delivering value year after year. Red Hat ranks #1 in value among software vendors. http://www.redhat.com/promo/vendor/
pgp90k8I4sIAU.pgp
Description: PGP signature
