nicolasgagnon | 24 Jul 16:52 2014
Picon

Async bulk transfer question

Hi all,

I am currently using the async API to transfer bulk data.

My problem is that I don`t know the size of the data that i`ll be receiving.
Thus the last portion of my data is never sent because the buffer is never
full (requested size is never matched).

I am wondering if there is a way to retrieve the data contained in the
buffer when the request hits the timeout, like the synchronous bulk read
does.

Thanks for the help.

Nicolas 

--
View this message in context: http://libusb.6.n5.nabble.com/Async-bulk-transfer-question-tp5713466.html
Sent from the LibUSB Dev - Win32 mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds
Kevin Cain | 20 Jul 07:23 2014

Libusb-win32 code to control Ricoh Theta

Hello, listeros,


I’ve received a Ricoh Theta (https://theta360.com/en/), a fairly new 'one shot' panoramic camera which I want to control via USB from a (Windows) PC.


There is no manufacturer API to control this unit, but like almost all digital cameras it supports Universal Plug and Play for discovery and Picture Transfer Protocol (PTP and PTP/IP) for data.  Therefore, the Theta can be controlled through various camera capture libraries, such as libgPhoto2 (Linux).  One example of controlling a Theta with PTP instructions in Linux is here:  http://mimosa-pudica.net/ricoh-theta.html.


As I'm running Windows 8.1, my first step was to replace the Theta's device’s USB driver in Windows, in order to avoid the process of managing a UPnP connection with the Theta under Windows via radio.  I used Zadig for its demonstrated compatibility with Win8.1:  http://zadig.akeo.ie/ (see: http://chdk.setepontos.com/index.php?topic=6231.msg106526#msg106526).


After launching Zagig, I changed the default ‘WinUSB’ selection to ‘libusb-win32’:



I had no trouble compiling libusb-win32 test code in MSVC++ 2013, including the single .h and linking the single .lib from libusb-win32.


When I run the program below, I am able to find the device (\\.\libusb0-0001--0x05ca-0x0364) and 'usb_control_msg' correctly returns 64, the number of bytes I'm sending. Based on PTP instructions successfully sent to the Ricoh Theta via GPhoto (http://mimosa-pudica.net/ricoh-theta.html), I gather that 'trigger-capture' is the keyword I'd need to use to fire the camera.


Unfortunately the camera is not taking a picture. Can anyone have a look at my simple code below so see if there is an obvious error, or suggest next steps?


Thanks,


-Kevin


---

// USB_Device_Communication.cpp : Defines the entry point for the console application. // #include "stdafx.h" #include "lusb0_usb.h" #include <iostream> // std::cout #include <string> // std::string using namespace std; int _tmain(int argc, _TCHAR* argv[]) { // Initialize USB Device communication struct usb_bus *busses; cout << "Initializing USB..." << endl; usb_init(); cout << "Finding USB busses..." << endl; usb_find_busses(); cout << "Finding devices..." << endl; usb_find_devices(); busses = usb_get_busses(); struct usb_bus *bus; int c, i, a; cout << "busses dir: " << busses->dirname << endl; // Iterate through all busses for (bus = busses; bus; bus = bus->next) { struct usb_device *dev; cout << "bus: " << bus->location << endl; // Iterate through all devices // Find the libUSB device: \\.\libusb0-0001--0x05ca-0x0364 for (dev = bus->devices; dev; dev = dev->next) { std::string str(dev->filename); std::string str2("libusb0-0001--0x05ca-0x0364"); std::size_t found = str.find(str2); if (found != std::string::npos) { cout << "device number: " << dev->devnum << endl; cout << "device vendor ID: " << dev->descriptor.idVendor << endl; cout << "device filename: " << dev->filename << "\n" << endl; /* Open the device, claim the interface and do your processing */ cout << "Opening device..." << endl; //usb_dev_handle *usb_open(); struct usb_dev_handle *devHandle; devHandle = usb_open(dev); //usb_dev_handle *usb_open(struct usb_device *dev); cout << "Claiming the interface..." << endl; usb_claim_interface(devHandle, 0); Sleep(200); // Wait for USB Interface (perhaps not needed?) cout << "Triggering camera" << endl; //"theta --trigger-capture",0,0); unsigned char buffer[64]; memset(buffer, 0, 64); buffer[0] = 't'; buffer[1] = 'r'; buffer[2] = 'i'; buffer[3] = 'g'; buffer[4] = 'g'; buffer[5] = 'e'; buffer[6] = 'r'; buffer[7] = '-'; buffer[8] = 'c'; buffer[9] = 'a'; buffer[10] = 'p'; buffer[11] = 't'; buffer[12] = 'u'; buffer[13] = 'r'; buffer[14] = 'e'; int result = usb_control_msg(devHandle, 0x21, 9, 0x2, 0x0, (char*)buffer, 64, 100); if (result == 64) cout << "Successfully sent all bytes to camera" << endl; } } } cout << "Exiting..." << endl; return 0; }
------------------------------------------------------------------------------
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds
_______________________________________________
Libusb-win32-devel mailing list
Libusb-win32-devel <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
Angelo Di Chello | 18 Jul 01:24 2014
Picon

CDC drivers for a modem in windows 98SE

Hi,
I should deliver drivers CDC ECM and ACM for a new modem connected to the host pc using usb.
Actually I already have linux, android, win xp, win 7, and win 8 drivers, but I need to deliver also drivers for windows 98 SE.
My question(a request for good suggestion, actually) is what would be the best option to have win98SE drivers with these functionalities.
I am thinking I could port them using libusb-win32(or equivalent) as an intermediate layer. Is that feasible in your opinion? Apart from the data throughput speed loss because win98SE uses usb 1.0/1,1, do you see any other possible functionality loss?


Actually, I have also read somewhere that in the past someone tried to modify some sys/inf file to make the usb port behave as a com/modem port on win98SE , like in here:

http://forums.codeguru.com/showthread.php?311881.html

, but they also obtained a BSOD when trying a disconnect-connect sequence. Maybe this solution is faster, but a bit too "dirty". Am I wrong?

Best regards,
ADC.
------------------------------------------------------------------------------
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds
_______________________________________________
Libusb-win32-devel mailing list
Libusb-win32-devel <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
邱宥惠 | 10 Jul 05:26 2014
Picon

Question about the libusb package

Dear :
         I am a user of libusb-win32-bin-1.2.6.0 package, it is a good solution about the USB device, but I got some trouble in it.
My computer OS is wondows7 x86,and I used the package on Visual Studio 2010.
I used the package to get iManufacturer number of USB camera module. I can get the number after install the inf-wizard.exe(I cannot get anything from the USB, if without installing the inf-wizard.exe). 
When I install the inf-wizard.exe, the USB camera module become a disk on my computer, I cannot use the USB camera module as a camera, how can I do?

my c code show as follow:

#include "stdafx.h"
#include "lusb0_usb.h"
#include <string.h>
#include <stdio.h>
#include <Windows.h>


int main( ) 
struct usb_bus *bus; 
struct usb_device *dev; 

usb_init(); 
usb_find_busses(); 
usb_find_devices(); 

for (bus = usb_busses; bus; bus = bus->next) 
for (dev = bus->devices; dev; dev = dev->next) 
int ret; 
char string[256]; 
usb_dev_handle *udev; 
udev = usb_open(dev); 

if (udev==NULL)
{
printf("can find device");
system("pause");
return -1;
}
if (udev)
if (dev->descriptor.iManufacturer)
ret = usb_get_string_simple(udev, dev->descriptor.iManufacturer, string, sizeof(string)); 
if (ret > 0)  
printf("Manufacturer : %s\n", string); 

if (dev->descriptor.iProduct) 
ret = usb_get_string_simple(udev, dev->descriptor.iProduct, string, sizeof(string)); 
if (ret > 0) 
printf("Product : %s\n", string); 
system("pause");
usb_close (udev); 
}  
system("pause");
return 0; 

}

------------------------------------------------------------------------------
Open source business process management suite built on Java and Eclipse
Turn processes into business applications with Bonita BPM Community Edition
Quickly connect people, data, and systems into organized workflows
Winner of BOSSIE, CODIE, OW2 and Gartner awards
http://p.sf.net/sfu/Bonitasoft
_______________________________________________
Libusb-win32-devel mailing list
Libusb-win32-devel <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
Siju Samuel | 24 Jun 22:28 2014
Picon

[LIBUSB] Find the filter attached device list

Hi,

I installed libusb filter on 32 bit windows 7 machine [ libusb-win32-devel-filter-1.2.6.0.exe downloaded as per http://sourceforge.net/p/libusb-win32/wiki/Home/]

1)
How can I find the list of  USB devices with filter attached. 

2)
When  I installed the above exe,  first it installed  libusb-win32 and then a filter gui  wizard came up to  attach the filter.   Now how I get the same gui-wizard,  if I want to remove teh filter.  Clicking teh above .exe just prompt for installing lib-win32 again.

Thanks,
SijU Samuel
------------------------------------------------------------------------------
Open source business process management suite built on Java and Eclipse
Turn processes into business applications with Bonita BPM Community Edition
Quickly connect people, data, and systems into organized workflows
Winner of BOSSIE, CODIE, OW2 and Gartner awards
http://p.sf.net/sfu/Bonitasoft
_______________________________________________
Libusb-win32-devel mailing list
Libusb-win32-devel <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
kuov | 17 Jun 06:37 2014

libusbK bsod

Hi:
     There is a bsod when I use libusbK's windows bankend with
libusb-1.0.dll .first I insert a usb cam(composite device),and do something
operation,after that,suddenly unplug the device,the BSD occur,followings are
some debug msg:

NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000b9c0b8
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80003ee6f31 rsp=fffff80000b9bde0 rbp=fffff800040530a8
 r8=0000000000000000  r9=0000000000000000 r10=fffffa8009d18e80
r11=0000000000000006 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!IopQueueThreadIrp+0xb1:
fffff800`03ee6f31 48897808        mov     qword ptr [rax+8],rdi
ds:69a0:0008=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80003fb9d92 to fffff80003eca490

STACK_TEXT:  
fffff800`00b9b398 fffff800`03fb9d92 : 00000000`00000008 fffff800`04052cc0
00000000`00000065 fffff800`03f0e178 : nt!RtlpBreakWithStatusInstruction
fffff800`00b9b3a0 fffff800`03fbab7e : 00000000`00000003 00000000`00000000
fffff800`03f0e9d0 00000000`0000000a : nt!KiBugCheckDebugBreak+0x12
fffff800`00b9b400 fffff800`03ed2744 : fffff880`019c69a0 fffffa80`0b17d554
fffffa80`0afb0700 fffff800`03e7c790 : nt!KeBugCheck2+0x71e
fffff800`00b9bad0 fffff800`03ed1be9 : 00000000`0000000a 00000000`00000008
00000000`00000002 00000000`00000001 : nt!KeBugCheckEx+0x104
fffff800`00b9bb10 fffff800`03ed0860 : fffffa80`0b284010 fffff880`018930a6
fffffa80`0b694380 fffff800`04052cc0 : nt!KiBugCheckDispatch+0x69
fffff800`00b9bc50 fffff800`03ee6f31 : fffffa80`09d38788 fffff800`03ec883e
fffffa80`0a30a3a0 00000000`00000000 : nt!KiPageFault+0x260
fffff800`00b9bde0 fffff800`041b6b04 : fffff800`00b9c0b8 fffff800`00b9bff0
00000000`00000000 fffffa80`0af4c1a0 : nt!IopQueueThreadIrp+0xb1
fffff800`00b9be40 fffff880`0541f618 : 00000000`00220013 fffffa80`0af4a050
00000000`00000000 fffffa80`0af4bc02 : nt!IoBuildDeviceIoControlRequest+0x114
fffff800`00b9beb0 fffff880`0542064d : fffff800`00b9c0c0 fffffa80`0af4c050
fffffa80`0af4c050 00000000`00000063 : usbhub!UsbhSyncSendInternalIoctl+0x70
fffff800`00b9bf40 fffff880`0541ec88 : fffff800`00b9c0c0 fffff800`00b9c0c4
00000000`0007c0c8 fffff880`016a6bb4 :
usbhub!UsbhFdoCheckUpstreamConnectionState+0x25
fffff800`00b9bf80 fffff880`05431702 : fffff800`00b9c170 fffffa80`0af4c050
00000000`00000000 fffff800`00b9c0c4 : usbhub!UsbhSyncSendCommand+0x50
fffff800`00b9c060 fffff880`05420143 : fffffa80`0bb01590 fffffa80`0bb01440
fffffa80`0af7d000 fffffa80`0b9d5390 : usbhub!UsbhQueryPortState+0x10a
fffff800`00b9c100 fffff880`054205a1 : fffffa80`0af4c050 fffffa80`0bb01440
fffffa80`0b9d5538 fffffa80`00000000 :
usbhub!UsbhFdoValidateConnectionPdo+0xaf
fffff800`00b9c160 fffff880`05450d8f : 00000000`00000000 00000000`00000000
fffffa80`0bb01440 fffff800`00b9c360 : usbhub!UsbhFdoUrbPdoFilter+0x119
fffff800`00b9c190 fffff880`0541efb7 : fffff880`00eae7c0 fffffa80`0a6bd630
00000000`00000005 fffff800`00b9c360 :
usbhub!UsbhPdoInternalDeviceControl+0x373
fffff800`00b9c1e0 fffff880`00e350c2 : 09b009ec`09ec0a10 fffff800`00b9c2f0
fffffa80`0a6bd630 fffff880`00eb8310 : usbhub!UsbhGenDispatch+0x57
fffff800`00b9c210 fffff880`00e36e73 : 0000057f`f59429c8 00000000`00000000
fffffa80`0b221010 fffffa80`0a6bd630 : Wdf01000!FxIoTarget::SubmitSync+0x24a
fffff800`00b9c2c0 fffff880`00e3d0d8 : fffffa80`0b221010 00000000`00000000
fffffa80`0b221010 00000000`00000000 :
Wdf01000!FxIoTarget::SubmitSyncRequestIgnoreTargetState+0xa3
fffff800`00b9c310 fffff880`0305d448 : fffffa80`0b9b0bd0 fffffa80`0b6d6060
00000000`00000000 fffff800`04044e80 :
Wdf01000!imp_WdfUsbTargetPipeResetSynchronously+0x2c8
fffff800`00b9c580 fffff880`03060f68 : 0000057f`f466ffd8 00000000`00000018
fffffa80`0b9901b0 00000000`00000002 : libusbK!Xfer_ReadBulk+0x134
[d:\work\usb-redirection\libusbk-3.0.7.0-src\src\sys\drv_xfer_bulk.c  <at>  202]
fffff800`00b9c5f0 fffff880`00e6ff90 : fffffa80`0b990020 0000057f`f464f428
fffffa80`0b221010 fffffa80`0b9b0bd0 : libusbK!PipeQueue_OnIoControl+0x13c
[d:\work\usb-redirection\libusbk-3.0.7.0-src\src\sys\drv_queue_pipe.c  <at>  83]
fffff800`00b9c620 fffff880`00e6f99f : fffffa80`0b9f7c02 fffffa80`0b990020
fffffa80`0b9b0bd0 00000000`00000001 :
Wdf01000!FxIoQueue::DispatchRequestToDriver+0x4b8
fffff800`00b9c6a0 fffff880`00e58c66 : fffffa80`0b9f7c30 fffffa80`0ba75002
00000000`00000000 00000000`00000000 :
Wdf01000!FxIoQueue::DispatchEvents+0x4df
fffff800`00b9c710 fffff880`00e58a71 : 00000000`00000000 fffffa80`0b9b0b02
fffffa80`0b9b0bd0 00000000`00000001 :
Wdf01000!FxRequest::PostProcessCompletion+0x1b2
fffff800`00b9c760 fffff880`00e4913e : 00000000`00000000 00000000`00000001
fffffa80`0b149800 fffffa80`0ba75010 :
Wdf01000!FxRequest::CompleteInternal+0x665
fffff800`00b9c810 fffff880`0305d8ad : 00000000`00000000 fffffa80`0b9f7c30
fffffa80`0a387df8 fffffa80`0b9f7dc0 :
Wdf01000!imp_WdfRequestCompleteWithInformation+0x1aa
fffff800`00b9c880 fffff880`00e5f22b : fffffa80`0b9f7c30 00000000`00000000
fffffa80`0a6bd630 00000000`00000002 : libusbK!Xfer_ReadBulkComplete+0x259
[d:\work\usb-redirection\libusbk-3.0.7.0-src\src\sys\drv_xfer_bulk.c  <at>  404]
fffff800`00b9c8e0 fffff880`00e35c9b : fffffa80`0a6bd630 fffffa80`0a6bd630
fffffa80`0a6bd640 fffffa80`0ba75001 :
Wdf01000!FxRequestBase::CompleteSubmitted+0x177
fffff800`00b9c960 fffff880`00e35dc4 : fffffa80`0baff002 ffffffff`c0000011
00000000`00000000 fffff800`03e0c7d8 :
Wdf01000!FxIoTarget::RequestCompletionRoutine+0x1cb
fffff800`00b9c9d0 fffff800`03ebee75 : fffffa80`0b9719a0 fffff800`03ffdfbd
fffffa80`0bb1c9a8 fffff800`03e0b354 :
Wdf01000!FxIoTarget::_RequestCompletionRoutine+0x3c
fffff800`00b9ca00 fffff800`03ed5a91 : fffffa80`0ba751bb 00000000`00000000
fffffa80`0b558880 00000000`000007ff : nt!IopUnloadSafeCompletion+0x55
fffff800`00b9ca40 fffff880`05266631 : fffffa80`0a928050 fffffa80`0a387e00
ffffffff`c0000011 00000000`00000000 : nt!IopfCompleteRequest+0x3b1
fffff800`00b9cb20 fffff880`05266b0f : fffffa80`0baff002 fffffa80`0ba75010
00000000`ffffffff fffffa80`0a928eb0 :
USBPORT!USBPORT_Core_iCompleteDoneTransfer+0xa15
fffff800`00b9cc00 fffff880`0526466f : fffffa80`0a928eb0 fffffa80`0a9281a0
fffffa80`0a929050 00000000`00000000 :
USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x3a7
fffff800`00b9cc60 fffff880`05255f89 : fffffa80`0a928050 00000000`00000000
fffffa80`0a928e02 fffffa80`0a928eb0 :
USBPORT!USBPORT_Core_UsbIocDpc_Worker+0xf3
fffff800`00b9cca0 fffff800`03eddb1c : fffff800`04044e80 fffffa80`0a928eb0
fffffa80`0a928ec8 00000000`00000000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
fffff800`00b9ccd0 fffff800`03eca36a : fffff800`04044e80 fffff800`04052cc0
00000000`00000000 fffff880`05255db0 : nt!KiRetireDpcList+0x1bc
fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000
fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a

STACK_COMMAND:  kb

FOLLOWUP_IP:
libusbK!Xfer_ReadBulk+134
[d:\work\usb-redirection\libusbk-3.0.7.0-src\src\sys\drv_xfer_bulk.c  <at>  202]
fffff880`0305d448 413bc6          cmp     eax,r14d

FAULTING_SOURCE_CODE:  
   198: 	}
   199:
   200: 	// handle pipe reset scenarios: ResetPipeOnResume, AutoClearStall
>  202: 	mXfer_HandlePipeResetScenarios(status, queueContext,
> requestContext);
   203:
   204: 	// Handle special case scenario where read length = 0
   205: 	if (!queueContext->Xfer.Length)
   206: 	{
   207: 		// if AllowPartialReads complete successfully for 0 bytes

   So ,Is libusbK.sys have bugs? could someone give me some sugguestion and
how to finish this. 

    Thanks!

--
View this message in context: http://libusb.6.n5.nabble.com/libusbK-bsod-tp5713373.html
Sent from the LibUSB Dev - Win32 mailing list archive at Nabble.com.

------------------------------------------------------------------------------
HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
Find What Matters Most in Your Big Data with HPCC Systems
Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
Leverages Graph Analysis for Fast Processing & Easy Data Exploration
http://p.sf.net/sfu/hpccsystems
Yuri Rellosa | 12 Jun 05:25 2014
Picon

Re: USB filter and project deployment

Hello LibUSBDotNet Team

I have a Linux Mass Storage device that windows detects normally.
It appears on the device manager and explorer.
Unless I apply the "device filter" via Filter Wizard on it, I cannot find the device with the function 
"UsbDevice.OpenUsbDevice(MyUsbFinder);" on my c# application
Neither does it appear on "UsbDevice.AllDevices;"

Does this mean that if I deploy this project on another computer,
that computer also has to apply the same filter?
What steps do I have to take so my device gets detected on another computer?

Best Regards

------------------------------------------------------------------------------
HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
Find What Matters Most in Your Big Data with HPCC Systems
Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
Leverages Graph Analysis for Fast Processing & Easy Data Exploration
http://p.sf.net/sfu/hpccsystems
_______________________________________________
Libusb-win32-devel mailing list
Libusb-win32-devel <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
Sid Price | 4 Jun 18:16 2014

New user questions

Hello, please forgive this very basic question but I am new to LibUSB-Win32 and trying to get started making my application.

 

I am using the Filter driver and that is installed and appears to be working, I have run the wizard to create the filtered driver for my USB device and the test program shows my USB device.

 

Now I am ready to start to develop the interface from my application using Visual Studio 2010 and ‘C’. I have looked at the files in the “libusb-win32-bin-1.2.6.0.zip” and I see “.lib” files, am I correct to link my x86 application using “libusb-win32-bin-1.2.6.0\lib\msvc\libusb.lib?”

 

Second, I need to find the header files required to build my application. In the benchmark application I see “lusb0_usb.h”, is this the only header file I need?

 

Thanks,

Sid.

 

Sid Price,

Software Tools for Embedded Systems Development.

Desktop Software Design.

User Interface Design.

 

------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their 
applications. Written by three acclaimed leaders in the field, 
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/NeoTech
_______________________________________________
Libusb-win32-devel mailing list
Libusb-win32-devel <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
Xiaofan Chen | 1 Jun 11:32 2014
Picon

Trac wiki removed, please use Wiki instead

Sourceforge will finally remove Trac for all the hosted projects. Therefore
I have disabled the Trac Wiki and move all the content to project Wiki.
I have also redirected the project web page to the project Wiki. Please
refresh your web browser if you have problems to access the project
web page.

Wiki:
https://sourceforge.net/p/libusb-win32/wiki/Home/

Project web (used to link to the Trac Wiki)
http://libusb-win32.sourceforge.net/

--

-- 
Xiaofan

------------------------------------------------------------------------------
Time is money. Stop wasting it! Get your web API in 5 minutes.
www.restlet.com/download
http://p.sf.net/sfu/restlet
Xiaofan Chen | 26 May 03:18 2014
Picon

Re: Building libusb-win32 source for version 1.2.5

On Sun, May 25, 2014 at 1:43 PM, Jason Micklewright <sconyj <at> yahoo.com> wrote:
> Hi Xiaofan,
> Thanks for the reply.
> Firstly, I don't want to build it myself.  I have to document how it's done
> for work purposes (long story).  I can't just refer to the libusb doc, I
> have to actually get it building.

Okay.

> I did get the WDK 7.1.0 but can't get past the setenv.bat call that the make
> calls somehow.  The make halts because setenv.bat is not called with any
> parameters. How do parameter get passed into setenv.bat from the make call?
> Is it something to do with running in a MinGW shell because I realize I'm
> not doing that.
> Thanks!

No, the WDK build of libusb-win32 (almost) has nothing to do with
MinGW, let alone MSys. Unless you want to build the MinGW
import library, you do not need MinGW.

In the ddk_make directory, edit make.cfg file to suit your
build environment. Quite some of them are optional and
are used to build the installer. You can safely comment
out them.

After that, run make.cmd under the command prompt (no
need to under the WDK command prompt) to know the build
options, choose the one you want.

--

-- 
Xiaofan

------------------------------------------------------------------------------
The best possible search technologies are now affordable for all companies.
Download your FREE open source Enterprise Search Engine today!
Our experts will assist you in its installation for $59/mo, no commitment.
Test it for FREE on our Cloud platform anytime!
http://pubads.g.doubleclick.net/gampad/clk?id=145328191&iu=/4140/ostg.clktrk
Jason Micklewright | 25 May 05:36 2014
Picon

Building libusb-win32 source for version 1.2.5

libusb 1.2.5 seem to want a really old version of the DDK.  At least it's certainly not WDK 8.0 or 8.1.
Has anyone been able to build it and if so what version of the WDK/DDK did you use and how did you obtain it.

I'm currently stuck at the point where make all wants a setenv.bat in the DDK for 8.0/8.1 there isn't one.

This is driving me nuts so any info at all would be helpful

Thanks,
Jason
------------------------------------------------------------------------------
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos.
Get unparalleled scalability from the best Selenium testing platform available
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net/sfu/SauceLabs
_______________________________________________
Libusb-win32-devel mailing list
Libusb-win32-devel <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel

Gmane