On Fri, Jun 15, 2012 at 11:08 AM, Pete Batard <p...@akeo.ie> wrote:
> All,
>
> It is my pleasure to announce the release of libusbx v1.0.12.
>
> In terms of bugfixes and new features, this new version brings the
> following improvements:
> * Fix a potential major regression with pthread on Linux
> * Fix missing thread ID from debug log output on cygwin
> * Fix possible crash when using longjmp and MinGW's gcc 4.6
> * Add topology calls: libusb_get_port_number(), libusb_get_parent() &
> libusb_get_port_path()
> * Add toggleable debug, using libusb_set_debug() or the LIBUSB_DEBUG
> environment variable
> * Define log levels in libusb.h and set timestamp origin to first
> libusb_init() call
> * All logging is now sent to to stderr (info was sent to stdout previously)
> * Update log messages severity and avoid polluting log output on OS-X
> * Add HID driver support on Windows
> * Enable interchangeability of MSVC and MinGW DLLs
> * Additional bug fixes and improvements
>
> The v1.0.12 source tarball can be downloaded at:
> https://sourceforge.net/projects/libusbx/files/latest/download?source=files
>
> For additional information or downloads, you are also invited to visit
> http://libusbx.org.
>
> Also note that you can always check our roadmap at
> https://sourceforge.net/apps/trac/libusbx/roadmap, for information about
> future releases, and you are of course welcome to submit improvement
> suggestions or bug reports on the libusbx-devel mailing list.
>
Pete,
I compiled at warning level 4 with Visual Studio 2010. There is a lot of
noise...
For future releases, you might want to look into this one :
1>c:\projects\isync\ultrasyncii\libusbx-1.0.12\libusb\os\windows_usb.c(1346):
warning C4701: potentially uninitialized local variable 'dev_info_data' used
I think it's a false alarm.
You might also want to add the following warning disable/reenable pairs in
libusb.h and libusbi.h:
#if defined(_MSC_VER)
#pragma warning(disable:4200)
#endif
#if defined(_MSC_VER)
#pragma warning(default:4200)
#endif
I always compile my code at warning level 4 and the spray of warnings from
libusb.h is irritating.
For the record, disabling 4200 leaves you with:
1>..\libusb\os\poll_windows.c(672): warning C4100: 'buf' : unreferenced
formal parameter
1>..\libusb\os\poll_windows.c(707): warning C4100: 'buf' : unreferenced
formal parameter
1> sync.c
1> threads_windows.c
1>..\libusb\os\threads_windows.c(30): warning C4100: 'attr' : unreferenced
formal parameter
1>..\libusb\os\threads_windows.c(85): warning C4100: 'attr' : unreferenced
formal parameter
1> windows_usb.c
1> Generating Code...
1>c:\projects\isync\ultrasyncii\libusbx-1.0.12\libusb\os\windows_usb.c(1337):
warning C4706: assignment within conditional expression
1>c:\projects\isync\ultrasyncii\libusbx-1.0.12\libusb\os\windows_usb.c(1346):
warning C4701: potentially uninitialized local variable 'dev_info_data' used
1>c:\projects\isync\ultrasyncii\libusbx-1.0.12\libusb\os\windows_usb.c(458):
warning C4706: assignment within conditional expression
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
