Since I have a copy, I compiled 1.0.12 with the Intel Compiler. I turned
off the zero length array and unreferenced parameter warnings. This is
what is left:
Building with Intel(R) C++ Compiler 12.1
ClCompile:
***** ClCompile (Win32 - Intel C++)
All outputs are up-to-date.
core.c
..\libusb\core.c(860): warning #188: enumerated type mixed with another type
ep_type = ep->bmAttributes & 0x3;
^
..\libusb\core.c(1742): warning #188: enumerated type mixed with another
type
enum libusb_capability cap = capability;
^
..\libusb\core.c(1886): warning #188: enumerated type mixed with another
type
enum libusb_error error = error_code;
^
descriptor.c
poll_windows.c
threads_windows.c
windows_usb.c
..\libusb\os\windows_usb.c(161): warning #181: argument is incompatible
with corresponding format string conversion
safe_sprintf(err_string, ERR_BUFFER_SIZE, "[%d] ", error_code);
^
..\libusb\os\windows_usb.c(2124): warning #111: statement is unreachable
usbi_dbg("ERROR: broken timer thread");
^
..\libusb\os\windows_usb.c(3519): warning #188: enumerated type mixed with
another type
&& (HidP_GetValueCaps(j, value_caps, &size[j],
preparsed_data) == HIDP_STATUS_SUCCESS)
^
All outputs are up-to-date.
io.c
sync.c
FWIW, Intel also have a warning level 5... you probably don't want to see
the whining that produces ;)
Orin.
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
libusbx-devel mailing list
libusbx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libusbx-devel
