Closed #138.
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/issues/138
--
Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master cu
Ok, thanks. You should add that to the wiki documentation on hotplug.
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/issues/138#issuecomment-23470250
--
Learn the latest--Visual S
On Tue, Aug 27, 2013 at 11:10 PM, Cody Vaudrin wrote:
> Hello all, I was wondering if there's a way to test a given
> libusb_device_handle for validity? I have a situation where a device handle
> could be corrupted, and when a corrupted (invalid) device handle is passed to
> the libusb_reset_de
Hello all, I was wondering if there's a way to test a given
libusb_device_handle for validity? I have a situation where a device handle
could be corrupted, and when a corrupted (invalid) device handle is passed to
the libusb_reset_device() function, libusbx crashes. I'm wondering if there's a
w
Ok, so this is not a bug. You need to call libusb_handle_events to get hotplug
callbacks.
As for the hotplugtest program shutting down. It exits after 2 events:
while (done < 2) {
libusb_handle_events (NULL);
}
Each callback in the example increments done. If you
Hi All,
I'm very happy to announce libusbx-1.0.17-rc1.
2013-08-28: v1.0.17-rc1
* Hotplug callbacks now always get passed a libusb_context, even if it is
the default context. Previously NULL would be passed for the default context,
but since the first context created is the default context,
No, I'm not. One interesting thing about the hotplugtest program is that it
shuts down on the second event (unplug). I expect that it should keep running
while I plug in and unplug the device?
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/issues/138#is
Closed #122.
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/pull/122
--
Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master curr
fingolfin, I think you misunderstand how ELF shared library versioning works
under at least Linux, you can either bump the LIBTOOL version macros claiming
to be backward compatible, at which point the filename would change from the
current libusb-1.0.so.0.1.0 to ie libusb-1.0.so.0.2.0, but the s
Closed #127.
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/issues/127
--
Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master cu
IMHO we should not be making our configure script more complicated to handle
corner cases like this. Fedora used to have libusb in /lib with the headers in
/usr/include without needing special configure support for this. Packagers
which want this can simply move some files around after make inst
11 matches
Mail list logo
