You can subscribe to this list here.
2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(5) |
Nov
(27) |
Dec
(9) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2004 |
Jan
(2) |
Feb
(19) |
Mar
(13) |
Apr
(15) |
May
(11) |
Jun
(17) |
Jul
(31) |
Aug
(45) |
Sep
(10) |
Oct
(40) |
Nov
(39) |
Dec
(45) |
2005 |
Jan
(113) |
Feb
(45) |
Mar
(38) |
Apr
(53) |
May
(11) |
Jun
(42) |
Jul
(56) |
Aug
(50) |
Sep
(32) |
Oct
(32) |
Nov
(47) |
Dec
(22) |
2006 |
Jan
(19) |
Feb
(32) |
Mar
(40) |
Apr
(40) |
May
(41) |
Jun
(44) |
Jul
(37) |
Aug
(51) |
Sep
(30) |
Oct
(30) |
Nov
(51) |
Dec
(20) |
2007 |
Jan
(7) |
Feb
(20) |
Mar
(17) |
Apr
(67) |
May
(13) |
Jun
(73) |
Jul
(16) |
Aug
(58) |
Sep
(29) |
Oct
(5) |
Nov
(74) |
Dec
(9) |
2008 |
Jan
(17) |
Feb
(12) |
Mar
(65) |
Apr
(22) |
May
(40) |
Jun
(32) |
Jul
(11) |
Aug
(8) |
Sep
(3) |
Oct
(41) |
Nov
(34) |
Dec
(12) |
2009 |
Jan
(44) |
Feb
(33) |
Mar
(16) |
Apr
(109) |
May
(11) |
Jun
(22) |
Jul
(21) |
Aug
(37) |
Sep
(5) |
Oct
(23) |
Nov
(7) |
Dec
(7) |
2010 |
Jan
(36) |
Feb
(40) |
Mar
(35) |
Apr
(45) |
May
(42) |
Jun
(104) |
Jul
(135) |
Aug
(50) |
Sep
(65) |
Oct
(110) |
Nov
(129) |
Dec
(75) |
2011 |
Jan
(105) |
Feb
(48) |
Mar
(93) |
Apr
(166) |
May
(169) |
Jun
(188) |
Jul
(106) |
Aug
(33) |
Sep
(85) |
Oct
(46) |
Nov
(102) |
Dec
(105) |
2012 |
Jan
(81) |
Feb
(115) |
Mar
(56) |
Apr
(93) |
May
(56) |
Jun
(77) |
Jul
(88) |
Aug
(52) |
Sep
(72) |
Oct
(16) |
Nov
(70) |
Dec
(70) |
2013 |
Jan
(23) |
Feb
(85) |
Mar
(38) |
Apr
(48) |
May
(40) |
Jun
(49) |
Jul
(33) |
Aug
(28) |
Sep
(66) |
Oct
(28) |
Nov
(28) |
Dec
(16) |
2014 |
Jan
(33) |
Feb
(58) |
Mar
(17) |
Apr
(50) |
May
(16) |
Jun
(24) |
Jul
(19) |
Aug
(32) |
Sep
(10) |
Oct
(10) |
Nov
(4) |
Dec
(10) |
2015 |
Jan
(11) |
Feb
(2) |
Mar
(4) |
Apr
(14) |
May
(1) |
Jun
(6) |
Jul
(16) |
Aug
(29) |
Sep
(6) |
Oct
(26) |
Nov
(10) |
Dec
|
2016 |
Jan
|
Feb
(20) |
Mar
(6) |
Apr
|
May
(3) |
Jun
(3) |
Jul
|
Aug
(16) |
Sep
(6) |
Oct
|
Nov
(15) |
Dec
|
2017 |
Jan
(1) |
Feb
(2) |
Mar
(4) |
Apr
|
May
(1) |
Jun
(3) |
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
(1) |
Dec
(1) |
2018 |
Jan
|
Feb
(8) |
Mar
(10) |
Apr
(16) |
May
|
Jun
(15) |
Jul
|
Aug
(3) |
Sep
(19) |
Oct
|
Nov
|
Dec
|
2019 |
Jan
|
Feb
|
Mar
(1) |
Apr
(2) |
May
|
Jun
|
Jul
|
Aug
|
Sep
(3) |
Oct
|
Nov
|
Dec
|
2020 |
Jan
|
Feb
|
Mar
|
Apr
(5) |
May
|
Jun
|
Jul
(7) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2021 |
Jan
(5) |
Feb
|
Mar
|
Apr
|
May
|
Jun
(5) |
Jul
(3) |
Aug
|
Sep
(6) |
Oct
(2) |
Nov
(4) |
Dec
|
2022 |
Jan
(1) |
Feb
(1) |
Mar
|
Apr
(1) |
May
|
Jun
(5) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2023 |
Jan
(5) |
Feb
(1) |
Mar
|
Apr
(3) |
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2024 |
Jan
|
Feb
(3) |
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Stephan M. <ste...@we...> - 2004-06-28 10:08:42
|
lib...@li... schrieb am 25.06.04 12:49:04: > > Hi everyone, > > I have a little problem. If an usb error occures e.g. when reading from a > bulk enppoint i want to get the exact error reason. This error reason is > important because the reaction of the program should depend on it. If a > timeout occures the program should only retry the operation but if a > severe error occures ( stall, etc. ) the program has to solve this by > clearing the stall condition or resetting the endpoint. > > My problem is that the function usb_strerror() returns an error string. I > dont want to parse this error string because it probably depends on the > language of the current system. So i am missing a function that simply > returns an error code. Or does anyone has an idea how to solve my problem > ? Maybe i am just blind for that simple situation. > Libusb's API currently hasn't any function to get the last error that occured. Errors are returned by the functions directly (return values < 0). The error codes returned are defined in 'errno.h' (part of your compiler). I just uploaded a new snapshot to the project's download site that includes better error handling. The following error values are currently used in the DLL: -EINVAL (-22): invalid argument -ETIMEDOUT (-116): request timed out -ENOMEM (-12): memory allocation error -EIO (-5): general I/O error -ENOENT (-2): no such file or directory Stephan > Bye, > > Thomas > > > ------------------------------------------------------- > This SF.Net email sponsored by Black Hat Briefings & Training. > Attend Black Hat Briefings & Training, Las Vegas July 24-29 - > digital self defense, top technical experts, no vendor pitches, > unmatched networking opportunities. Visit www.blackhat.com > _______________________________________________ > Libusb-win32-devel mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel ____________________________________________________ Aufnehmen, abschicken, nah sein - So einfach ist WEB.DE Video-Mail: http://freemail.web.de/?mc=021200 |
From: <dev...@si...> - 2004-06-25 07:28:45
|
Hi everyone, I have a little problem. If an usb error occures e.g. when reading from a bulk enppoint i want to get the exact error reason. This error reason is important because the reaction of the program should depend on it. If a timeout occures the program should only retry the operation but if a severe error occures ( stall, etc. ) the program has to solve this by clearing the stall condition or resetting the endpoint. My problem is that the function usb_strerror() returns an error string. I dont want to parse this error string because it probably depends on the language of the current system. So i am missing a function that simply returns an error code. Or does anyone has an idea how to solve my problem ? Maybe i am just blind for that simple situation. Bye, Thomas |
From: Linus W. <tr...@df...> - 2004-06-18 11:32:52
|
On Fri, 18 Jun 2004, Stephan Meyer wrote: > I created a snapshot section in the download area > (http://sourceforge.net/project/showfiles.php?group_id=78138) and released > a snapshot there (it's also in the CVS). This version should support all > control message types defined by the USB specifications (section 9.3). > If something still doesn't work, please let us know. Hey, everything magically works now! :-) Well done Stephan! Linus |
From: Stephan M. <ste...@we...> - 2004-06-18 10:31:57
|
lib...@li... schrieb am 18.06.04 01:21:23: > > On Thu, 17 Jun 2004, Stephan Meyer wrote: > > > > Then the problem occurs in usb_control_msg(): all > > > messages fail with a -1 return code and the following string from > > > usb_strerror(): > > > > > > "error sending control message: win error: The I/O operation has been > > > aborted because of either a thread exit or an application request." > > > > > > > This usually means that the device didn't respond to the request, i.e. a > > timeout occured. You are either sending or requesting wrong data, > > setting the timeout value too low, or the device firmware isn't working > > correctly or isn't fully complaint to the USB specifications. > > This is strange, what I'm porting is libnjb (libnjb.sf.net) and we have it > working 100% under Linux, BSD and MacOS X. Proprietary drivers for > Windows also work fine, that's what we based our code on. But I'll > investigate further. > I investigated libnjb's source code and now things become clearer. I figured out that the library uses vendor and class specific control messages. These vendor and class specific request have not been fully implemented in the 0.1.8.0 version. Another user already pointed me to that problem some weeks ago. So this is not a problem of libjnb, it's just a missing feature in libusb-win32. The reason for this is that the Windows kernel doesn't support generic control messages like Linux, BSD, or MacOS. This means that each control message has to be analyzed in the DLL, split up, and passed to the right function of libusb's kernel module and some of these message types are not implemented in the current release. I created a snapshot section in the download area (http://sourceforge.net/project/showfiles.php?group_id=78138) and released a snapshot there (it's also in the CVS). This version should support all control message types defined by the USB specifications (section 9.3). If something still doesn't work, please let us know. Before using this version uninstall the old one first. Hope this helps. Stephan > Anyone else had similar problems? (Now I'm asking at the *right* > mailinglist...) > > > BTW, there is are libusb-win32 related mailing list at > > <lib...@li...>, > > which might be a better place to ask these Windows related questions. > > Um, I was intending to use it, but must have had a short-circuit in my > brain. Now it's in the right place. > > Linus > > > ------------------------------------------------------- > This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference > Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer > Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA > REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND > _______________________________________________ > Libusb-win32-devel mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel _______________________________________________________ WEB.DE Video-Mail - Sagen Sie mehr mit bewegten Bildern Informationen unter: http://freemail.web.de/?mc=021199 |
From: Stephan M. <ste...@we...> - 2004-06-18 09:07:40
|
Thanks for reporting this bug. I'll include the patch in the next release. Stephan <br><br><table cellpadding="0" cellspacing="0" border="0"><tr><td bgcolor="#000000"><img src="http://img.web.de/p.gif" width="1" height="1" border="0" alt="" /></td></tr><tr><td style="font-family:verdana; font-size:12px; line-height:17px;">WEB.DE Video-Mail - Die E-Mail der nächsten Generation! <br>Jetzt testen: <A HREF="http://freemail.web.de/?mc=021198"><B>http://freemail.web.de/?mc=021198</B></A> </td></tr></table> |
From: Stephan M. <ste...@we...> - 2004-06-18 09:03:11
|
> >The lib/msvc folder of the binary packages contains an import library for > >the Microsoft compiler (libusb.lib). Linking against the gcc library won't work > >because the object file format of the two complilers aren't compatible. > > Okay, this works. > But how is this libusb.lib generated? > The .lib is generated from the makefile in the following way: - gcc builds the DLL with the '-Wl,--output-def,$(DLL_TARGET).def' option which produces the .def file 'libusb0.def'. This .def file contains all symbols exported by the DLL. - the command '$(DDK_ROOT_PATH)/bin/x86/lib.exe /machine:i386 /def:$(DLL_TARGET).def' builds the import library for Microsoft compilers. The makefile currently uses lib.exe provided by the DDK although any other lib.exe (from Visual C++, etc.) should work. Stephan > > Greetings > Juergen > -- > mailto:Jue...@ic... > Phone: +49/851/94412-14 > Fax: +49/851/40141 > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference > Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer > Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA > REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND > _______________________________________________ > Libusb-win32-devel mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel ________________________________________________________________ Verschicken Sie romantische, coole und witzige Bilder per SMS! Jetzt neu bei WEB.DE FreeMail: http://freemail.web.de/?mc=021193 |
From: <IC-...@t-...> - 2004-06-18 08:15:34
|
>MIME-Version: 1.0 >From: "Stephan Meyer" <ste...@we...> >To: lib...@li... >Subject: Re: [Libusb-win32-devel] Linking libusb with Visual C compiler? > >> has anyone succeeded in linking libusb.a to an application compiled with >> MS Visual C compiler? >> I tried this and got the following warning: >> > >The lib/msvc folder of the binary packages contains an import library for >the Microsoft compiler (libusb.lib). Linking against the gcc library won't work >because the object file format of the two complilers aren't compatible. Okay, this works. But how is this libusb.lib generated? Greetings Juergen -- mailto:Jue...@ic... Phone: +49/851/94412-14 Fax: +49/851/40141 |
From: Roger B. <ro...@ro...> - 2004-06-17 19:32:46
|
Linus Walleij wrote: > Anyone else had similar problems? (Now I'm asking at the *right* > mailinglist...) I can say that I have had no problems. My code talks to US CDMA cellphones on a bulk interface. Works fine on libusb-win32 as well as libusb on Linux and Mac. Roger |
From: Linus W. <tr...@df...> - 2004-06-17 18:50:32
|
On Thu, 17 Jun 2004, Stephan Meyer wrote: > > Then the problem occurs in usb_control_msg(): all > > messages fail with a -1 return code and the following string from > > usb_strerror(): > > > > "error sending control message: win error: The I/O operation has been > > aborted because of either a thread exit or an application request." > > > > This usually means that the device didn't respond to the request, i.e. a > timeout occured. You are either sending or requesting wrong data, > setting the timeout value too low, or the device firmware isn't working > correctly or isn't fully complaint to the USB specifications. This is strange, what I'm porting is libnjb (libnjb.sf.net) and we have it working 100% under Linux, BSD and MacOS X. Proprietary drivers for Windows also work fine, that's what we based our code on. But I'll investigate further. Anyone else had similar problems? (Now I'm asking at the *right* mailinglist...) > BTW, there is are libusb-win32 related mailing list at > <lib...@li...>, > which might be a better place to ask these Windows related questions. Um, I was intending to use it, but must have had a short-circuit in my brain. Now it's in the right place. Linus |
From: Stephan M. <ste...@we...> - 2004-06-17 16:35:53
|
> has anyone succeeded in linking libusb.a to an application compiled with= > MS Visual C compiler=3F > I tried this and got the following warning: >=20 The lib/msvc folder of the binary packages contains an import library for the Microsoft compiler (libusb.lib). Linking against the gcc library won't= work because the object file format of the two complilers aren't compatible. Stephan =20 > Verkn=FCpfen... > libusb.a(d000001.o) : warning LNK4078: Mehrfache '.text'-Abschnitte mit=20 > unterschiedlichen Attributen gefunden (E0000020) >=20 > When I start my application it crashes in the first call to a libusb fun= ction > (usally usb=5Finit() ). >=20 >=20 > Greetings > Juergen > --=20 > mailto:Jue...@ic... > Phone: +49/851/94412-14 > Fax: +49/851/40141 >=20 >=20 >=20 >=20 > ------------------------------------------------------- > This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference > Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer > Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA > REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND= > =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F > Libusb-win32-devel mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F Aufnehmen, abschicken, nah sein - So einfach ist=20 WEB.DE Video-Mail: http://freemail.web.de/=3Fmc=3D021200 |
From: <dev...@si...> - 2004-06-17 13:43:45
|
I don't know if this is already known but i think i found a bug in the filter driver in the file bulk_transfer.c . When a irq cancel routine is called the routine owns the CancelSpinLock automatically. So the CancelSpinLock mus be releases before calling IoCancelIrp() for the sub_irp because this call aquires the CancelSpinLock again. On some PC's with Hyperthreading processors this will cause a system crash when a timeout cancels the transfer. On most other PC's it is not harmful. Maybe the Windows 2000 / XP multiprocessor kernel needs stricter handling on SpinLocks. Whith the following changes the problems are gone : ( the modified lines are marked with" /***/ " ). typedef struct { URB urb; IRP *main_irp; IRP *sub_irp; /***/ KIRQL irql; libusb_remove_lock *remove_lock; } Context; NTSTATUS bulk_transfer(IRP *irp, libusb_device_extension *device_extension, int endpoint, MDL *buffer, int size, int direction) { ... /***/ IoAcquireCancelSpinLock(&context->irql); IoSetCancelRoutine(context->main_irp, on_bulk_cancel); /***/ IoReleaseCancelSpinLock(context->irql); ... } void on_bulk_cancel(DEVICE_OBJECT *device_object, IRP *irp) { Context *context = (Context *)irp->Tail.Overlay.DriverContext[0]; /***/ IoReleaseCancelSpinLock(context->irql); IoCancelIrp(context->sub_irp); } Best regards, Thomas |
From: <IC-...@t-...> - 2004-06-17 12:12:56
|
Hallo, has anyone succeeded in linking libusb.a to an application compiled with MS Visual C compiler? I tried this and got the following warning: Verkn=FCpfen... libusb.a(d000001.o) : warning LNK4078: Mehrfache '.text'-Abschnitte mit=20 unterschiedlichen Attributen gefunden (E0000020) When I start my application it crashes in the first call to a libusb functi= on (usally usb_init() ). Greetings =09Juergen --=20 mailto:Jue...@ic... Phone: +49/851/94412-14 Fax: +49/851/40141 |
From: <IC-...@t-...> - 2004-06-16 12:26:47
|
> >Version 0.1.8.1?? Did you mean 0.1.8.0, which is the latest? Yes, it was 0.1.8.0 with your patch for DDK 3790 from 5.5.2004 "Build question..." > >> >> Hallo, >> >> I have an USB 2.0 device which works with libusb and USB 2.0. >> >> in this order and it works with linux. >> But for windows I must call >> usb_claim_interface() after usb_set_configuration(), >> because the windows usb_set_configuration sets >> dev->interface = -1 >> in line 233 of windows.c. >> Is there a reason for this line? >> > >The reason for this is that on Windows the user should be forced >to call the functions in the correct order, which is: > >usb_open() >usb_set_configuration() >usb_claim_interface() > >This should work across all platforms supported by libusb. Calling the functions >in any other order won't work on Windows (although it could work on Linux). > >The above sequence is compliant to the USB specifications, which require that >a device is in the 'unconfigured' state after reset, i.e. no valid configuration >is selected. >And as configurations contain interfaces, interfaces can only be claimed or used after a >valid configuration has been chosen. Okay, now it is clear. I used the wrong way because the libusb documentation said, that the interface must be claimed before anything else could be done. > >> >> With claiming the interface after set_configuration my device >> works fine with Windows XP, USB 2.0, DDK3790. >> (Except that I must call usb_bulk_read instead of usb_interrupt_read for >> USB 2.0, otherwise I get errorcode -22 (Out of Memory).) > >Strange. Here's the way usb_interrupt_read() is implemented, should behave the >same way as usb_bulk_read() does. > >int usb_interrupt_read(usb_dev_handle *dev, int ep, char *bytes, int size, > int timeout) >{ > return usb_bulk_read(dev, ep, bytes, size, timeout); >} > > >Error code -22 is EINVAL (invalid argument) is returned if the device is not open, >if no valid configuration is selected, or if no interface has been claimed. Sorry, I was unclear on this and gave the wrong errorcode: Using libusb with linux (2.6.4) causes errorcode -12 (out of memory) if using usb_interrupt_read for a device with USB 2.0 If I force USB 1.1 everything is fine. And for USB 2.0 I must use usb_bulk_read. Because usb_interrupt_read and usb_bulk_read have no important differences in Windows, I haven't tested it with Windows. Greetings Juergen -- mailto:Jue...@ic... Phone: +49/851/94412-14 Fax: +49/851/40141 |
From: Stephan M. <ste...@we...> - 2004-06-16 10:52:20
|
Version 0.1.8.1?? Did you mean 0.1.8.0, which is the latest? > > Hallo, > > I have an USB 2.0 device which works with libusb and USB 2.0. > > In my application I called > usb_open() > usb_claim_interface() > usb_set_configuration() > > in this order and it works with linux. > But for windows I must call > usb_claim_interface() after usb_set_configuration(), > because the windows usb_set_configuration sets > dev->interface = -1 > in line 233 of windows.c. > Is there a reason for this line? > The reason for this is that on Windows the user should be forced to call the functions in the correct order, which is: usb_open() usb_set_configuration() usb_claim_interface() This should work across all platforms supported by libusb. Calling the functions in any other order won't work on Windows (although it could work on Linux). The above sequence is compliant to the USB specifications, which require that a device is in the 'unconfigured' state after reset, i.e. no valid configuration is selected. And as configurations contain interfaces, interfaces can only be claimed or used after a valid configuration has been chosen. > > With claiming the interface after set_configuration my device > works fine with Windows XP, USB 2.0, DDK3790. > (Except that I must call usb_bulk_read instead of usb_interrupt_read for > USB 2.0, otherwise I get errorcode -22 (Out of Memory).) Strange. Here's the way usb_interrupt_read() is implemented, should behave the same way as usb_bulk_read() does. int usb_interrupt_read(usb_dev_handle *dev, int ep, char *bytes, int size, int timeout) { return usb_bulk_read(dev, ep, bytes, size, timeout); } Error code -22 is EINVAL (invalid argument) is returned if the device is not open, if no valid configuration is selected, or if no interface has been claimed. Stephan > > > Greetings > Juergen > -- > mailto:Jue...@ic... > Phone: +49/851/94412-14 > Fax: +49/851/40141 > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference > Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer > Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA > REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND > _______________________________________________ > Libusb-win32-devel mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel _______________________________________________________ WEB.DE Video-Mail - Sagen Sie mehr mit bewegten Bildern Informationen unter: http://freemail.web.de/?mc=021199 |
From: <IC-...@t-...> - 2004-06-16 09:22:39
|
Hallo, I have an USB 2.0 device which works with libusb and USB 2.0. In my application I called usb_open() usb_claim_interface() usb_set_configuration() in this order and it works with linux. But for windows I must call usb_claim_interface() after usb_set_configuration(), because the windows usb_set_configuration sets dev->interface = -1 in line 233 of windows.c. Is there a reason for this line? With claiming the interface after set_configuration my device works fine with Windows XP, USB 2.0, DDK3790. (Except that I must call usb_bulk_read instead of usb_interrupt_read for USB 2.0, otherwise I get errorcode -22 (Out of Memory).) Greetings Juergen -- mailto:Jue...@ic... Phone: +49/851/94412-14 Fax: +49/851/40141 |
From: <ben...@id...> - 2004-05-25 07:46:28
|
Dear Open Source developer I am doing a research project on "Fun and Software Development" in which I kindly invite you to participate. You will find the online survey under http://fasd.ethz.ch/qsf/. The questionnaire consists of 53 questions and you will need about 15 minutes to complete it. With the FASD project (Fun and Software Development) we want to define the motivational significance of fun when software developers decide to engage in Open Source projects. What is special about our research project is that a similar survey is planned with software developers in commercial firms. This procedure allows the immediate comparison between the involved individuals and the conditions of production of these two development models. Thus we hope to obtain substantial new insights to the phenomenon of Open Source Development. With many thanks for your participation, Benno Luthiger PS: The results of the survey will be published under http://www.isu.unizh.ch/fuehrung/blprojects/FASD/. We have set up the mailing list fa...@we... for this study. Please see http://fasd.ethz.ch/qsf/mailinglist_en.html for registration to this mailing list. _______________________________________________________________________ Benno Luthiger Swiss Federal Institute of Technology Zurich 8092 Zurich Mail: benno.luthiger(at)id.ethz.ch _______________________________________________________________________ |
From: Stephan M. <ste...@we...> - 2004-05-17 17:20:44
|
lib...@li... schrieb am 17.05.04 17:31:29: >=20 > Hi! >=20 >=20 > I'm sorry for subj but as i'm too new for that kind of things, i > wanted to ask whether there are any examples of working with real > usb devices. What i mean is, for example, to get packet-block from > some kind of device (not version or some standard info). There are many open source projects using libusb. For instance: libgphoto2: http://www.gphoto.org/ SANE: http://www.sane-project.org/ Projects using libusb-win32: sucr: http://www.cexx.org/dakota/sucr.htm=20 bitpim: http://bitpim.sourceforge.net/ P5 glove: http://www.robotgroup.net/index.cgi/P5Glove/ AVR programmer: http://unpy.net/avr/usb/uavrp/ These projects could all be used as an example of how to use libusb/libusb-win32. > As far as i > understand, it can be done asynchronously (like interrupt > generation) when this block comes from device (some callback > function or event)=3F USB (and libusb) doesn't support any kind of callback or events. The reaso= n for this is that USB is a single-master-multiple-slave bus. This means tha= t=20 devices only transmit data if a transfer is initiated by the host (PC). De= vices=20 never transmit data on their own. For more details see http://www.usb.org/developers/docs. > And is there any warranty of not losing a packet=3F Yes, see above. But if you are communicating with a device which produces a constant stream of data such as audio devices, DAQ devices, etc. you hav= e to ensure that the data is read fast enough by the host side to prevent da= ta loss. >=20 > I'd be grateful for any kind of feedback or reference. Excuse me > again. >=20 > PS Especially interesting are things concerned with micro-controllers > supporting USB. >=20 > Alles Gutes! >=20 > ...In Code We Trust... > --=20 > =F0=D2=C9 =D6=C5=CC=C1=CE=C9=C9, mailto:den...@ma... >=20 >=20 >=20 >=20 > ------------------------------------------------------- > This SF.Net email is sponsored by: SourceForge.net Broadband > Sign-up now for SourceForge Broadband and get the fastest > 6.0/768 connection for only $19.95/mo for the first 3 months! > http://ads.osdn.com/=3Fad=5Fid=3D2562&alloc=5Fid=3D6184&op=3Dclick > =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F > Libusb-win32-devel mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F Verschicken Sie romantische, coole und witzige Bilder per SMS! Jetzt neu bei WEB.DE FreeMail: http://freemail.web.de/=3Fmc=3D021193 |
From: Denis K. <den...@ma...> - 2004-05-17 15:30:55
|
Hi! I'm sorry for subj but as i'm too new for that kind of things, i wanted to ask whether there are any examples of working with real usb devices. What i mean is, for example, to get packet-block from some kind of device (not version or some standard info). As far as i understand, it can be done asynchronously (like interrupt generation) when this block comes from device (some callback function or event)? And is there any warranty of not losing a packet? I'd be grateful for any kind of feedback or reference. Excuse me again. PS Especially interesting are things concerned with micro-controllers supporting USB. Alles Gutes! ...In Code We Trust... -- При желании, mailto:den...@ma... |
From: Stephan M. <ste...@we...> - 2004-05-13 06:07:05
|
Try to use two threads. Something like this: thread() { while(1) { bulk_read(data); queue_write(data); } } main() { while(1) { wait_for_data(); queue_read(data); process(data); } } lib...@li... schrieb am 12.05.04 17:24:16: > > Hallo everybody, > > I try to program a USB video device with libusb. Does anybody know how > to read video data with bulk_read from the device without loosing data? > > When I try this, I loose data: > > while (TRUE) > { > bulk_read(data); > process(data); <= during process I loose data > } > > Thanks > Michael > > -- > ------------------------------------------------------------------------ > > Michael Bahrs > R & D > TerraTec Electronic GmbH > > Herrenpfad 38 > D-41334 Nettetal > > Phone: +49-2157-8179-332 > Fax: +49-2157-8179-22 > Email: mic...@te... <mailto:fri...@te...> > Internet: www.terratec.com <http://www.terratec.com> > > ------------------------------------------------------------------------ > This message is intended only for the use of the addressee(s) and may > contain information that is PRIVILEGED and CONFIDENTIAL. If you are not > the intended recipient, dissemination of this communication is > prohibited. If you have received this communication in error, please > erase all copies of the message and its attachments and notify > pos...@te... immediately. > IT IS NOT ALLOWED TO PUBLISH ANY PART OF THIS MESSAGE WITHOUT THE > AUTHOR'S WRITTEN PERMISSION. > > > > ------------------------------------------------------- > This SF.Net email is sponsored by Sleepycat Software > Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to > deliver higher performing products faster, at low TCO. > http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 > _______________________________________________ > Libusb-win32-devel mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel _______________________________________________________________________ ... and the winner is... WEB.DE FreeMail! - Deutschlands beste E-Mail ist zum 39. Mal Testsieger (PC Praxis 03/04) http://f.web.de/?mc=021191 |
From: Michael B. <mic...@te...> - 2004-05-12 15:23:54
|
Hallo everybody, I try to program a USB video device with libusb. Does anybody know how to read video data with bulk_read from the device without loosing data? When I try this, I loose data: while (TRUE) { bulk_read(data); process(data); <= during process I loose data } Thanks Michael -- ------------------------------------------------------------------------ Michael Bahrs R & D TerraTec Electronic GmbH Herrenpfad 38 D-41334 Nettetal Phone: +49-2157-8179-332 Fax: +49-2157-8179-22 Email: mic...@te... <mailto:fri...@te...> Internet: www.terratec.com <http://www.terratec.com> ------------------------------------------------------------------------ This message is intended only for the use of the addressee(s) and may contain information that is PRIVILEGED and CONFIDENTIAL. If you are not the intended recipient, dissemination of this communication is prohibited. If you have received this communication in error, please erase all copies of the message and its attachments and notify pos...@te... immediately. IT IS NOT ALLOWED TO PUBLISH ANY PART OF THIS MESSAGE WITHOUT THE AUTHOR'S WRITTEN PERMISSION. |
From: Stephan M. <ste...@we...> - 2004-05-06 06:09:43
|
A checked build is used because the drivers require the KdPrint() kernel function which is used to enable debug messages (can be turned on/off by 'usb_set_debug()'). If the drivers would have been compiled with the 'fre' option no debug support would be available. So if you don't need this feature you can turn it off by recompiling the drivers with the 'fre' option. But I wouldn't recommend this. This debug feature is really useful! Stephan Mian Adnan M PHCA <Mi...@ph...> schrieb am 05.05.04 23:52:37: > > > Why is a checked build used for the libusbfl.sys and libusbst.sys > instead of the free build? I am thinking maybe someone forgot to change the > build_drivers.bat file back to the free build after debugging was done, or > leave it in checked mode to make it easier for other developers to debug > there stub drivers. > > I changed the following line: > call setenv.bat %1 chk > to: > call setenv.bat %1 fre > > Adnan Mian > ____________________________________________________________________ Der WEB.DE Virenschutz schuetzt Ihr Postfach vor dem Wurm Sober.A-F! Kostenfrei fuer FreeMail Nutzer. http://f.web.de/?mc=021158 |
From: Stephan M. <ste...@we...> - 2004-05-06 05:57:27
|
Sorry, I forgot to attach the files. Here they are. > > > I did not see an attached file. I think since the response was posted to > the list the attached file was removed. Reply to this email, or cut and > post the text of the file to the list so other people might know of the > changes. Also, you might have to change the extension if you only send the > file to me since the mail server here might remove the file thinking it > might be a virus. I have had that happen a few times. > > Thanks again, > > Adnan Mian > > > > > Your question>Does this really work? Which DDK version are you using, > > Server2003-DDK, or the XP-DDK? > > My answer>I am using the Server 2003 DDK release 3790. > > > > I was able to make the executables, but after a few modifications. I > > noticed that the "make DDK_PATH=" should be "make > > DDK_ROOT_PATH=", but a better way to do this is to do the > > You are right, the current Makefile contains a bug. I attached a modified > version. > "make DDK_PATH=<DDK_PATH>" should work now. > > > following: > > 1. Go into the Makefile > > 2. Change DDK_ROOT_PATH = C:/WINDDK/2600.1106 to DDK_ROOT_PATH = > > with version. (ex. C:/WINDDK/3790) > > 3. Type "make" > > 4. Type "make dist" > > I noticed if I do not change the DDK_ROOT_PATH in the makefile then "make > > dist" cannot find the ddk. > > > > I also had to comment out the build -c -g -w in build_drivers.bat and > build > > the sys files manually from ddk command line. Do you any idea to what the > > problem is? The only thing I notice weird is that the backslashes are > > sometimes "\" and other times "/" like: > > > > The problem seems to be that the latest msys/mingw version defines an > environment variable (MAKEFLAGS) which somehow interferes with nmake (the > DDK make). > The attached file 'build_drivers.bat' fixes this. > > BTW, it now also compiles under cygwin! > > _____________________________________________________________________ > Der WEB.DE Virenschutz schuetzt Ihr Postfach vor dem Wurm Netsky.A-P! > Kostenfrei fuer alle FreeMail Nutzer. http://f.web.de/?mc=021157 > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: Oracle 10g > Get certified on the hottest thing ever to hit the market... Oracle 10g. > Take an Oracle 10g class now, and we'll give you the exam FREE. > http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click > _______________________________________________ > Libusb-win32-devel mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel > ____________________________________________________________________ Der WEB.DE Virenschutz schuetzt Ihr Postfach vor dem Wurm Sober.A-F! Kostenfrei fuer FreeMail Nutzer. http://f.web.de/?mc=021158 |
From: Stephan M. <ste...@we...> - 2004-05-05 06:46:39
|
> > Your question>Does this really work? Which DDK version are you using, > Server2003-DDK, or the XP-DDK? > My answer>I am using the Server 2003 DDK release 3790. > > I was able to make the executables, but after a few modifications. I > noticed that the "make DDK_PATH=" should be "make > DDK_ROOT_PATH=", but a better way to do this is to do the You are right, the current Makefile contains a bug. I attached a modified version. "make DDK_PATH=<DDK_PATH>" should work now. > following: > 1. Go into the Makefile > 2. Change DDK_ROOT_PATH = C:/WINDDK/2600.1106 to DDK_ROOT_PATH = > with version. (ex. C:/WINDDK/3790) > 3. Type "make" > 4. Type "make dist" > I noticed if I do not change the DDK_ROOT_PATH in the makefile then "make > dist" cannot find the ddk. > > I also had to comment out the build -c -g -w in build_drivers.bat and build > the sys files manually from ddk command line. Do you any idea to what the > problem is? The only thing I notice weird is that the backslashes are > sometimes "\" and other times "/" like: > The problem seems to be that the latest msys/mingw version defines an environment variable (MAKEFLAGS) which somehow interferes with nmake (the DDK make). The attached file 'build_drivers.bat' fixes this. BTW, it now also compiles under cygwin! _____________________________________________________________________ Der WEB.DE Virenschutz schuetzt Ihr Postfach vor dem Wurm Netsky.A-P! Kostenfrei fuer alle FreeMail Nutzer. http://f.web.de/?mc=021157 |
From: Mian A. M P. <Mi...@ph...> - 2004-05-05 00:20:29
|
Your question>Does this really work? Which DDK version are you using, Server2003-DDK, or the XP-DDK? My answer>I am using the Server 2003 DDK release 3790. I was able to make the executables, but after a few modifications. I noticed that the "make DDK_PATH=<DDK_PATH>" should be "make DDK_ROOT_PATH=<DDK_PATH>", but a better way to do this is to do the following: 1. Go into the Makefile 2. Change DDK_ROOT_PATH = C:/WINDDK/2600.1106 to DDK_ROOT_PATH =<DDK_PATH> with version. (ex. C:/WINDDK/3790) 3. Type "make" 4. Type "make dist" I noticed if I do not change the DDK_ROOT_PATH in the makefile then "make dist" cannot find the ddk. I also had to comment out the build -c -g -w in build_drivers.bat and build the sys files manually from ddk command line. Do you any idea to what the problem is? The only thing I notice weird is that the backslashes are sometimes "\" and other times "/" like: BUILD: Loading C:/WINDDK/3790\build.dat... I tried the slash both ways, but the only difference was the above line looked like: BUILD: Loading C:/WINDDK/3790/build.dat... The error I got is below which seems like a nmake option is not understood: make --win32 build_drivers make[1]: Entering directory `/c/junk/newdevice/libusb-win32-src-0.1.8.0' call build_drivers.bat C:/WINDDK/3790 c:\junk\newdevice\libusb-win32-src-0.1.8.0>path .;C:\msys\1.0\local\bin;C:\mingw\bin;C:\msys\1.0\bin;x\Engineering_APPS\PVCS 67\VM\win32\bin;c:\WINNT\system32;c:\WINNT;c:\WINNT\System32\Wbem;c:\Program Files\ATI Technologies\ATI Control Panel;c:\Tornado\host\resource\zinc;c:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\bin;c:\Program Files\Microsoft Visual Studio .NET 2003\Common7\IDE;c:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\PlatformSDK\Include;c:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\Include;c:\Program Files\Microsoft Visual Studio\Common\MSDev98\Bin;c:\Program Files\Microsoft Visual Studio\Common\Tools;c:\Program Files\Microsoft Visual Studio\VC98\bin;c:\Program Files\NVIDIA Corporation\Cg\bin;c:\Program Files\NSIS;c:\WINDDK\3790;C:/WINDDK/3790\bin c:\junk\newdevice\libusb-win32-src-0.1.8.0>set current_dir=c:\junk\newdevice\libusb-win32-src-0.1.8.0 c:\junk\newdevice\libusb-win32-src-0.1.8.0>call setenv.bat C:/WINDDK/3790 chk C:\junk\newdevice\libusb-win32-src-0.1.8.0\src\drivers>build -c -g -w BUILD: Adding /Y to COPYCMD so xcopy ops won't hang. BUILD: Object root set to: ==> objchk_wnet_x86 BUILD: Compile and Link for i386 BUILD: Loading C:/WINDDK/3790\build.dat... BUILD: Computing Include file dependencies: BUILD: Examining c:\junk\newdevice\libusb-win32-src-0.1.8.0\src\drivers directory tree for files to compile. c:\junk\newdevice\libusb-win32-src-0.1.8.0\src\drivers c:\junk\newdevice\libusb-win32-src-0.1.8.0\src\drivers\filter c:\junk\newdevice\libusb-win32-src-0.1.8.0\src\drivers\filter - 21 source files (2,600 lines) c:\junk\newdevice\libusb-win32-src-0.1.8.0\src\drivers\stub c:\junk\newdevice\libusb-win32-src-0.1.8.0\src\drivers\stub - 2 source files (192 lines) BUILD: Saving C:/WINDDK/3790\build.dat... Total of 23 source files (2,792 lines) to compile in 2 directories BUILD: Compiling c:\junk\newdevice\libusb-win32-src-0.1.8.0\src\drivers\filter directory NMAKE : fatal error U1065: invalid option '-' BUILD: nmake.exe failed - rc = 2 BUILD: Compiling c:\junk\newdevice\libusb-win32-src-0.1.8.0\src\drivers\stub directory NMAKE : fatal error U1065: invalid option '-' BUILD: nmake.exe failed - rc = 2 BUILD: Compile errors: not linking c:\junk\newdevice\libusb-win32-src-0.1.8.0\src\drivers\filter directory BUILD: Compile errors: not linking c:\junk\newdevice\libusb-win32-src-0.1.8.0\src\drivers\stub directory BUILD: Done C:\junk\newdevice\libusb-win32-src-0.1.8.0\src\drivers>cd c:\junk\newdevice\libusb-win32-src-0.1.8.0 C:\junk\newdevice\libusb-win32-src-0.1.8.0>copy src\drivers\i386\libusbfl.sys libusbfl.sys The system cannot find the file specified. C:\junk\newdevice\libusb-win32-src-0.1.8.0>copy src\drivers\i386\libusbst.sys libusbst.sys The system cannot find the file specified. C:\junk\newdevice\libusb-win32-src-0.1.8.0>cd c:\junk\newdevice\libusb-win32-src-0.1.8.0 make[1]: Leaving directory `/c/junk/newdevice/libusb-win32-src-0.1.8.0' make: *** No rule to make target `libusbst.sys', needed by `all'. Stop. Thanks, Adnan Mian -----Original Message----- From: Stephan Meyer [mailto:ste...@we...] Sent: Monday, May 03, 2004 12:58 To: lib...@li... Subject: Re: [Libusb-win32-devel] Build question... lib...@li... schrieb am 03.05.04 18:25:14: > > > I noticed in the Build Process the second bullet says: > make DDK_PATH=<DDK_PATH> > should this not be: > set DDK_PATH=<DDK_PATH> > ex. where DDK_PATH might be /c/WINDDK/3790 > > I think this is not needed if you define the ddk path in your > PATH%environment variables. I notice if you run "set" you can see the paths No, this is not sufficiant because the DDK scripts used to build the drivers require the DDK's root path to find the libraries, include files, etc. But I haven't tested the latest DDK yet maybe this has changed. > and see this already is defined. If you type "make" it starts to build the > executables. Does this really work? Which DDK version are you using, Server2003-DDK, or the XP-DDK? > > I reason I am asking this I am trying to build the executables. I > downloaded the libusb-win32-src-0.1.8.0.tar.gz to get the source to build, > but it did not work. I changed the CC=gcc in the makefile to CC=cl for the > Microsoft Visual C\C++ 6.0 complier. The following is the MinGW output. This won't work because a compiler which supports the new C99 standard is required to build the library (DLL). As far as I know neither MSVC nor Borland compilers are fully C99 compliant. As a result GCC is the only one capable of doing the job. > > $ ls > AUTHORS.txt Makefile install.nsi.in tests > COPYING_GPL.txt README.in license_nsis.txt > COPYING_LGPL.txt build_all.sh src > ChangeLog.txt build_drivers.bat testlibusb-win.exe.manifest > > LSDUser@SABTECHDEVPC /c/junk/finalusb/libusb-win32-src-0.1.8.0 > $ make dist > cl -c ./src/usb.c -o usb.o -O2 -Wall -DEOVERFLOW=139 -DVERSION_MAJOR=0 > -DVERSION _MINOR=1 -DVERSION_MICRO=8 -DVERSION_NANO=0 -I./src > -I./src/drivers/filter -I./s rc/service > Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 13.10.3077 for 80x86 > Copyright (C) Microsoft Corporation 1984-2002. All rights reserved. > > usb.c > c:\junk\finalusb\libusb-win32-src-0.1.8.0\src\error.h(21) : error C2010: '.' > : u nexpected in macro formal parameter list > c:\junk\finalusb\libusb-win32-src-0.1.8.0\src\error.h(21) : error C2010: '.' > : u nexpected in macro formal parameter list > c:\junk\finalusb\libusb-win32-src-0.1.8.0\src\error.h(21) : error C2010: '.' > : u nexpected in macro formal parameter list > src\usb.c(44) : warning C4127: conditional expression is constant > src\usb.c(56) : warning C4127: conditional expression is constant > src\usb.c(71) : warning C4127: conditional expression is constant > src\usb.c(73) : warning C4127: conditional expression is constant > src\usb.c(113) : warning C4127: conditional expression is constant > src\usb.c(125) : warning C4127: conditional expression is constant > src\usb.c(140) : warning C4127: conditional expression is constant > src\usb.c(142) : warning C4127: conditional expression is constant > src\usb.c(247) : warning C4018: '>=' : signed/unsigned mismatch > make: *** [usb.o] Error 2 > > > Paths in MinGW are set as: > PATH='.:/usr/local/bin:/mingw/bin:/bin:x/Engineering_APPS/PVCS67/VM/win32/bi > n:/c/WINNT/system32:/c/WINNT:/c/WINNT/System32/Wbem:/c/Program Files/ATI > Technologies/ATI Control Panel:/c/Tornado/host/resource/zinc:/c/Program > Files/Microsoft Visual Studio .NET 2003/Vc7/bin:/c/Program Files/Microsoft > Visual Studio .NET 2003/Common7/IDE:/c/Program Files/Microsoft Visual Studio > .NET 2003/Vc7/PlatformSDK/Include:/c/Program Files/Microsoft Visual Studio > .NET 2003/Vc7/Include:/c/Program Files/Microsoft Visual > Studio/Common/MSDev98/Bin:/c/Program Files/Microsoft Visual > Studio/Common/Tools:/c/Program Files/Microsoft Visual > Studio/VC98/bin:/c/Program Files/NVIDIA Corporation/Cg/bin:/c/Program > Files/NSIS:/c/WINDDK/3790' > > Thanks inadvance, > > Adnan Mian > > > ------------------------------------------------------- > This SF.Net email is sponsored by: Oracle 10g > Get certified on the hottest thing ever to hit the market... Oracle 10g. > Take an Oracle 10g class now, and we'll give you the exam FREE. > http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click > _______________________________________________ > Libusb-win32-devel mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel _____________________________________________________________________ Der WEB.DE Virenschutz schuetzt Ihr Postfach vor dem Wurm Netsky.A-P! Kostenfrei fuer alle FreeMail Nutzer. http://f.web.de/?mc=021157 ------------------------------------------------------- This SF.Net email is sponsored by: Oracle 10g Get certified on the hottest thing ever to hit the market... Oracle 10g. Take an Oracle 10g class now, and we'll give you the exam FREE. http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click _______________________________________________ Libusb-win32-devel mailing list Lib...@li... https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel |
From: Stephan M. <ste...@we...> - 2004-05-03 19:58:37
|
lib...@li... schrieb am 03.05.04 18:25:14: > > > I noticed in the Build Process the second bullet says: > make DDK_PATH=<DDK_PATH> > should this not be: > set DDK_PATH=<DDK_PATH> > ex. where DDK_PATH might be /c/WINDDK/3790 > > I think this is not needed if you define the ddk path in your > PATH%environment variables. I notice if you run "set" you can see the paths No, this is not sufficiant because the DDK scripts used to build the drivers require the DDK's root path to find the libraries, include files, etc. But I haven't tested the latest DDK yet maybe this has changed. > and see this already is defined. If you type "make" it starts to build the > executables. Does this really work? Which DDK version are you using, Server2003-DDK, or the XP-DDK? > > I reason I am asking this I am trying to build the executables. I > downloaded the libusb-win32-src-0.1.8.0.tar.gz to get the source to build, > but it did not work. I changed the CC=gcc in the makefile to CC=cl for the > Microsoft Visual C\C++ 6.0 complier. The following is the MinGW output. This won't work because a compiler which supports the new C99 standard is required to build the library (DLL). As far as I know neither MSVC nor Borland compilers are fully C99 compliant. As a result GCC is the only one capable of doing the job. > > $ ls > AUTHORS.txt Makefile install.nsi.in tests > COPYING_GPL.txt README.in license_nsis.txt > COPYING_LGPL.txt build_all.sh src > ChangeLog.txt build_drivers.bat testlibusb-win.exe.manifest > > LSDUser@SABTECHDEVPC /c/junk/finalusb/libusb-win32-src-0.1.8.0 > $ make dist > cl -c ./src/usb.c -o usb.o -O2 -Wall -DEOVERFLOW=139 -DVERSION_MAJOR=0 > -DVERSION _MINOR=1 -DVERSION_MICRO=8 -DVERSION_NANO=0 -I./src > -I./src/drivers/filter -I./s rc/service > Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 13.10.3077 for 80x86 > Copyright (C) Microsoft Corporation 1984-2002. All rights reserved. > > usb.c > c:\junk\finalusb\libusb-win32-src-0.1.8.0\src\error.h(21) : error C2010: '.' > : u nexpected in macro formal parameter list > c:\junk\finalusb\libusb-win32-src-0.1.8.0\src\error.h(21) : error C2010: '.' > : u nexpected in macro formal parameter list > c:\junk\finalusb\libusb-win32-src-0.1.8.0\src\error.h(21) : error C2010: '.' > : u nexpected in macro formal parameter list > src\usb.c(44) : warning C4127: conditional expression is constant > src\usb.c(56) : warning C4127: conditional expression is constant > src\usb.c(71) : warning C4127: conditional expression is constant > src\usb.c(73) : warning C4127: conditional expression is constant > src\usb.c(113) : warning C4127: conditional expression is constant > src\usb.c(125) : warning C4127: conditional expression is constant > src\usb.c(140) : warning C4127: conditional expression is constant > src\usb.c(142) : warning C4127: conditional expression is constant > src\usb.c(247) : warning C4018: '>=' : signed/unsigned mismatch > make: *** [usb.o] Error 2 > > > Paths in MinGW are set as: > PATH='.:/usr/local/bin:/mingw/bin:/bin:x/Engineering_APPS/PVCS67/VM/win32/bi > n:/c/WINNT/system32:/c/WINNT:/c/WINNT/System32/Wbem:/c/Program Files/ATI > Technologies/ATI Control Panel:/c/Tornado/host/resource/zinc:/c/Program > Files/Microsoft Visual Studio .NET 2003/Vc7/bin:/c/Program Files/Microsoft > Visual Studio .NET 2003/Common7/IDE:/c/Program Files/Microsoft Visual Studio > .NET 2003/Vc7/PlatformSDK/Include:/c/Program Files/Microsoft Visual Studio > .NET 2003/Vc7/Include:/c/Program Files/Microsoft Visual > Studio/Common/MSDev98/Bin:/c/Program Files/Microsoft Visual > Studio/Common/Tools:/c/Program Files/Microsoft Visual > Studio/VC98/bin:/c/Program Files/NVIDIA Corporation/Cg/bin:/c/Program > Files/NSIS:/c/WINDDK/3790' > > Thanks inadvance, > > Adnan Mian > > > ------------------------------------------------------- > This SF.Net email is sponsored by: Oracle 10g > Get certified on the hottest thing ever to hit the market... Oracle 10g. > Take an Oracle 10g class now, and we'll give you the exam FREE. > http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click > _______________________________________________ > Libusb-win32-devel mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel _____________________________________________________________________ Der WEB.DE Virenschutz schuetzt Ihr Postfach vor dem Wurm Netsky.A-P! Kostenfrei fuer alle FreeMail Nutzer. http://f.web.de/?mc=021157 |