From: Michael P. <mic...@gm...> - 2010-04-02 15:41:51
|
stdint.h causes a BUNCH of errors. The first set is fixable, but I'm not sure how you want to fix them. "error C2632: 'long' followed by 'long' is illegal" The first couple examples are (there are 8, not 2, lines like this) : typedef long long int64_t; typedef unsigned long long uint64_t; which probably ought to be (for _MSC_VER): typedef __int64 int64_t; typedef unsigned __int64 uint64_t; Not sure how you want to handle that. Worse, the following macro in stdint.h doesn't work: #define UINT64_C(val) val##ULL This is used in windows_usb.c. I'm not sure what the correct suffix is for MSVC. Michael -----Original Message----- From: Pete Batard [mailto:pb...@gm...] Sent: Friday, April 02, 2010 8:04 AM To: lib...@li... Subject: Re: [Libusb-devel] binary snapshots for the Windows backend On 2010.04.02 12:31, Kustaa Nyholm wrote: > I've not seen (bothered to look at) the stdint.h in question, > but if it is anything like the standard stdint.h I'm very doubtful > that a single header file like that is actually copyrightable, no matter > how many copyright notices the authors put on it. Alright, I have now replaced the stdint.h and inttypes.h by slightly modified PUBLIC DOMAIN versions that I picked up from MinGW-w64 (r236) Seems to work well enough with VS2008 and DDK, and I think it should work fine with earlier versions of MSVC, but this needs to be tested. Regards, /Pete ---------------------------------------------------------------------------- -- Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Libusb-devel mailing list Lib...@li... https://lists.sourceforge.net/lists/listinfo/libusb-devel |