Basically, we have an usbi_dbg("") during libusb_init, which we could
put to good use to ensure that, if we ask our users for console debug
output through setting LIBUSB_DEBUG=4 during troubleshooting, we will
also get an explicit libusbx version report.
Regards,
/Pete
>From 552315e56c34e251d8926def95eefceeffa5f7e6 Mon Sep 17 00:00:00 2001
From: Pete Batard <[email protected]>
Date: Wed, 6 Jun 2012 13:49:41 +0100
Subject: [PATCH] Core: Display libusbx version in libusb_init's debug output
---
libusb/core.c | 3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/libusb/core.c b/libusb/core.c
index d4ff789..a286da0 100644
--- a/libusb/core.c
+++ b/libusb/core.c
@@ -1650,7 +1650,8 @@ int API_EXPORTED libusb_init(libusb_context **context)
usbi_dbg("created default context");
}
- usbi_dbg("");
+ usbi_dbg("libusbx v%d.%d.%d.%d", libusb_version_internal.major,
libusb_version_internal.minor,
+ libusb_version_internal.micro, libusb_version_internal.nano);
if (usbi_backend->init) {
r = usbi_backend->init(ctx);
--
1.7.10.msysgit.1
------------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/libusbx-devel
