libusb-win32-devel

[Libusb-win32-devel] Re: using libusb-win32 together with libftdi

[Jonathon L. - H. <jon...@ha...>]

Cory,

Do you have libftdi and libusb-win32 packaged in the same dll?

I'd like to put them in the same dll, but I'd rather avoid figuring out 
all the cygwin stuff. (So could I have a copy of yours?)

Does mingw generate .lib files that VC++ can use?

with thanks

Jonathon Love

[Libusb-win32-devel] libusb-win32 LGPL license enquiry

[Jonathon L. - H. <jon...@ha...>]

G'day,

I just have a query about using libusb-win32 in proprietary software

In order to pass, along with our program we must provide:

  - object files (.lib files for VC++) for all our code
  - libusb-win32 packaged in a separate dll (so our code isn't staticly 
linked with it)
  - source code for libusb-win32
  - prominent notices saying that sections of our program are released 
under the LGPL
  - none of our own source code

with thanks

Jonathon Love

Haltech Engine Management Systems

Re: [Libusb-win32-devel] Problem locating new USB device with filter driver.

[Mark B. <mc...@ec...>]

I've had the same problem with the filter driver causing USB devices to 
disappear from add/remove programs. There is a bug open on this - 1412538.

As for using the filter driver where another driver is already 
installed... I found that libusb can be used to get the descriptors of 
such devices, but can not claim an interface if the usual driver has 
already done so. This was from experimenting with using libusb on a 
mouse, just to get the hang of things (and I wasn't sure that my 
hardware was working). To be able to claim an interface from the device, 
I had to install libusb as the driver for that device, overwriting the 
manufacturer's driver. Maybe if the manufacturer's driver doesn't 
connect to the device until some software is started you may be OK using 
only the filter driver, but just a warning that you may have to install 
libusb's drivers over the top of the manufacturer's in order to do any 
more than find the device and get it's descriptors!

Personally, I didn't find the filter driver much use, except to run 
testlibusb and see the descriptors of (most of) the devices connected. 
Not had any problems with libusb killing anything else. Maybe try again 
(if cleaning up the mess isn't too hard), and if it still kills 
everything else there could be a problem with your Windows installation.

That's just my (limited) experiences. Hope some it helps.

Mark.


Graeme Gill wrote:

>
> Some other problems I've noticed.
>
> After uninstalling libusb (both the filter and non-filter
> drivers), and re-installing all the USB plug and play drivers,
> my systems USB was operating correctly again.
>
> I then installed the filter driver, and noticed that
> the "Unplug/Eject" function of Windows stops operating. This
> means that when I want to remove a USB flash stick, there's
> no way of telling the system to unmount it. If I do
> remove the USB stick anyway, then I get a warning
> panel "Unsafe Removal of Device", telling me I
> should have clicked on the Unplug/Eject icon in the taskbar,
> which doesn't exist!
>
> (This has been bugging me for months. Now I know.
> Installing the libusb-win32 filter driver has caused
> this problem.)
>
> So it seems that on my system, both the filter driver,
> and the filter driver cause problems. The filter driver
> stops the Unplug/Eject function from working, but
> works well otherwise, and the non-filter driver
> kills the whole USB system.
>
> Graeme Gill.
>
>
> -------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job 
> easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache 
> Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> Libusb-win32-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel

Re: [Libusb-win32-devel] Problem locating new USB device with filter driver.

[Graeme G. <gr...@ar...>]

Some other problems I've noticed.

After uninstalling libusb (both the filter and non-filter
drivers), and re-installing all the USB plug and play drivers,
my systems USB was operating correctly again.

I then installed the filter driver, and noticed that
the "Unplug/Eject" function of Windows stops operating. This
means that when I want to remove a USB flash stick, there's
no way of telling the system to unmount it. If I do
remove the USB stick anyway, then I get a warning
panel "Unsafe Removal of Device", telling me I
should have clicked on the Unplug/Eject icon in the taskbar,
which doesn't exist!

(This has been bugging me for months. Now I know.
Installing the libusb-win32 filter driver has caused
this problem.)

So it seems that on my system, both the filter driver,
and the filter driver cause problems. The filter driver
stops the Unplug/Eject function from working, but
works well otherwise, and the non-filter driver
kills the whole USB system.

Graeme Gill.

Re: [Libusb-win32-devel] Problem locating new USB device with filter driver.

[Graeme G. <gr...@ar...>]

On rebooting m machine this morning, I notice I now
have more serious problems. USB has stopped working.
Presumably this has been caused by installing libiusb0.sys
for the device I want to support.

What should I do now ?

Graeme Gill.

Re: [Libusb-win32-devel] Re: using libusb-win32 together with libftdi

[Jonathon <j...@co...>]

> One thing you should be aware of is that a read in libftdi may return
> no payload (0 bytes).

Yes, the reason for this is because usb_read_bulk() to an FTDI chip always
returns 2 status bytes in addition to the payload. So usb_read_bulk()
never blocks, always returning 2 status bytes, or 2 status bytes +
payload.

hence, ftdi_read_data never blocks either. (ftdi_read_data obviously
removes the status bytes, leaving you with zero bytes)

I'd already half written my code before I found libftdi, which is how I've
figured out all this stuff.

I was working on making my software 'cope' with the usb being unplugged,
and being plugged in again. (Software says... you've gone offline, then
says you've gone back online)

Rather interestingly, subsequent calls to usb_claim_interface() ... (or
the libftdi equivalent) when claiming it for a second time [after
unplugging and replugging] would always fail. ('The device is busy') ...
but if I set the latency setting (16ms by default [in the chip]) somewhere
in my code (even to 16ms, which it was already set to!), claiming the
interface a second time would succeed.

oh, man, there's way too much magic in these FTDI chips.

> by continually polling ftdi_read_data until the requested number of
> bytes were received or the timeout in milliseconds elapsed.

yeah, did the same thing.

cheers

Jonathon

Re: [Libusb-win32-devel] Re: using libusb-win32 together with libftdi

[Cory S. <co...@mo...>]

Hi Jonathon,

Yes, I did get libftdi to work.  My problems turned out to be related
to Cygwin with the -mno-cygwin option.  Compiling libusb-win32,
libftdi, and my own application and libraries with MinGW/Msys solved
the issues I was having.  I admit it should not have made a
difference, but it did, and I'm glad it now works.

I have not tried Visual C++ so cannot provide any helpful hints for
that specifically.

One thing you should be aware of is that a read in libftdi may return
no payload (0 bytes).  So, I wrote a wrapper to perform a timed read
by continually polling ftdi_read_data until the requested number of
bytes were received or the timeout in milliseconds elapsed.  You may
need to do something similar in your code.

Best of luck,
Cory

On 4/21/06, Jonathon <j...@co...> wrote:
> How did you go Cory?
>
> Did you get libftdi working on libusb-win32 ??
>
> I'm working on a project doing that at the moment. I think I can get it
> all to build properly, but I'm using Visual C++
>
> J.

On 3/30/06, Cory Sharp <co...@mo...> wrote:
> I can get libftdi to work in Cygwin, but also experience issues you
> describe (read basically fails). I'm using libftdi 0.7 and have tried
> both libusb-win32 0.1.10.1 and CVS HEAD as of today.
>
> libftdi DOES work for me without problem providing I compile libftdi
> and my application *without* -mno-cygwin.  My ftdi/usb reads fail when
> I compile libftdi and my application with -mno-cygwin.
>
> Unfortunately, one of the things I'm building is a JNI DLL to be used
> by Java -- which pretty much requires -mno-cygwin.
>
> I can try to debug this, but I'd appreciate any suggestions about what
> kinds of things I should be looking for in particular, and where.
>
> Thanks, best,
> Cory
>
> ----- On 2006-01-09 03:23, <morper@te...> wrote:
>
> Has anyone tried to use libusb-win32 together with libftdi from
> intra2net? (http://www.intra2net.com/de/produkte/opensource/ftdi/index.ph=
p).
>
> I have the problem that, when I try to read data from the device via
> libftdi based on libusb-win32, I only receive some single bytes with
> very high values (between 248 and 255). Using the same software under
> Linux with libusb works correctly.
>
> Thanks for any suggestions.

Re: [Libusb-win32-devel] Problem locating new USB device with filter driver.

[Graeme G. <gr...@ar...>]

Stephan Meyer wrote:

>  > Presumably this is because there aren't any device specific
>  > USB drivers installed for this device. How can I tell Windows
>  > that the libusb-win32 filter driver will handle this device ?
> 
> You can't. On Windows every device needs a (device) driver in
> order to work. You either have to install the manufacturer's device
> driver or the one provided by libusb-win32.

OK - no point in attempting the impossible. Pretty brittle
and inflexible of MS to do things that way, but that seems
to be their style at times.

I created the .inf file and installed libusb0.sys, and yes,
the device now appears in testlibusb.exe output.

Can I hope that if the manufacturers USB driver is installed
over the top, that the filter driver will take over
for my application ?

(Thanks for helping sort my problems out.)

Graeme Gill.

[Libusb-win32-devel] Re: using libusb-win32 together with libftdi

[Jonathon <j...@co...>]

How did you go Cory?

Did you get libftdi working on libusb-win32 ??

I'm working on a project doing that at the moment. I think I can get it
all to build properly, but I'm using Visual C++

J.

Re: [Libusb-win32-devel] Problem locating new USB device with filter driver.

[Stephan M. <Ste...@ia...>]

> Yes it shows up in the device manager. It has a yellow exclamation
> mark. The Device status says "This device is not configured 
> correctly. (Code 1)
> To reinstall drivers for this device, click Reinstall Driver".
> 
> Presumably this is because there aren't any device specific
> USB drivers installed for this device. How can I tell Windows
> that the libusb-win32 filter driver will handle this device ?

You can't. On Windows every device needs a (device) driver in
order to work. You either have to install the manufacturer's device
driver or the one provided by libusb-win32.

From your application's point of view it should make no difference
whether you install libusb as a filter or as a 'normal' driver. 
You get the same API and the same functionality. The only difference
is the way the kernel driver (which is the same binary file in both 
cases) is installed.

> 
> [I'm presuming that using the inf-wizard to generate a device
>   .inf file will lead to installing the non-filter libusb-win32
>   driver for this device, which would likely solve the problem,
>   but seemed like a bad idea if the manufacturers drivers later
>   need to be installed.]
> 
> Graeme Gill.
> 
> 
> 
> 
> -------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, 
security?
> Get stuff done quickly with pre-integrated technology to make your job 
easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache 
Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> Libusb-win32-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel

Re: [Libusb-win32-devel] Problem locating new USB device with filter driver.

[Graeme G. <gr...@ar...>]

Stephan Meyer wrote:

> Does your device show up in the device manager? Is it installed
> properly (without a yellow exclamation mark or a red cross)?

Thanks for the response.

Yes it shows up in the device manager. It has a yellow exclamation
mark. The Device status says "This device is not configured correctly. (Code 1)
To reinstall drivers for this device, click Reinstall Driver".

Presumably this is because there aren't any device specific
USB drivers installed for this device. How can I tell Windows
that the libusb-win32 filter driver will handle this device ?

[I'm presuming that using the inf-wizard to generate a device
  .inf file will lead to installing the non-filter libusb-win32
  driver for this device, which would likely solve the problem,
  but seemed like a bad idea if the manufacturers drivers later
  need to be installed.]

Graeme Gill.

Re: [Libusb-win32-devel] Problem locating new USB device with filter driver.

[Stephan M. <Ste...@ia...>]

> [ Hello ? Anybody out there ? Is this mailing list still active ? ]
> 
> Some additional information:
> 
>    inf-wizard.exe does pick the device up (vendor ID 0x0765,
>    Product ID 0xD094) , but then I get the impression from
>    looking at its source, that it doesn't use libusb-win32
>    to locate devices.

Does your device show up in the device manager? Is it installed
properly (without a yellow exclamation mark or a red cross)?

> 
> libusb on OSX and Linux worked straight out of the box. The
> OS didn't make a fuss about the new device, and testlibusb
> found the device without trouble.
> 
> Any ideas why libusb-win32 is not behaving the same way ?
> 
> Graeme Gill.
> 
> 
> -------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, 
security?
> Get stuff done quickly with pre-integrated technology to make your job 
easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache 
Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> Libusb-win32-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel

Re: [Libusb-win32-devel] Problem locating new USB device with filter driver.

[Graeme G. <gr...@ar...>]

[ Hello ? Anybody out there ? Is this mailing list still active ? ]

Some additional information:

   inf-wizard.exe does pick the device up (vendor ID 0x0765,
   Product ID 0xD094) , but then I get the impression from
   looking at its source, that it doesn't use libusb-win32
   to locate devices.

libusb on OSX and Linux worked straight out of the box. The
OS didn't make a fuss about the new device, and testlibusb
found the device without trouble.

Any ideas why libusb-win32 is not behaving the same way ?

Graeme Gill.

[Libusb-win32-devel] Problem locating new USB device with filter driver.

[Graeme G. <gr...@ar...>]

I'm trying to develop some software to talk to a USB device.
Previous versions of this device communicated through a serial
port, but now the manufacturer has switched to USB.

The Device may or may not have had the originally manufacturers
USB drivers installed on the users machine. I'd like my software
to work in either case, and allow the user the option of
installing my software, or the manufacturers software,
or both, in any order.

So I've installed the LibUSB-win32 filter driver.
The sample application (testlibusb.c) compiles and runs OK.
Normally it will show 5 busses, and if I plug
a USB device in (such as a flash stick), the
device will turn up on one of the busses.

When I plug the device I'm developing for in,
I notice two things. One is that Windows (2K)
notices the new hardware, and goes looking for manufactures
drivers. I don't have the manufacturers software, because I
bought the device without it. Presumably Windows can be
made to stop doing this by tweaking the right registry settings,
although it's not clear to me whether this will then make it
difficult to install the manufacturers drivers later on.

The second thing I notice, is that testlibusb.exe doesn't
find the device. It's hard to even get to first base if
my software can't see it!

Can someone point me in the right direction to solve
this problem ? Windows can obviously see the device,
why can't the LibUSB filter driver see the device as well ?

(I'm using version 0.1.10.1)

thanks,
	Graeme Gill.

RE: [Libusb-win32-devel] 64-bit Windows libusb build - anyone do ne it yet?

[Brian H. <Bri...@da...>]

Hi.  After massaging my code a bit, I was able to re-compile 
a test program for the company I work for.  It ran nicely under 
a 64-bit operating system (Windows XP X64) utilitizing 
libusb !!!  :)

However, I did see some debug spew:

LIBUSB_DLL: Info: usb_os_init: dll version: 1.1.10.2
LIBUSB_DLL: Info: usb_os_init: driver version: 0.1.10.2
LIBUSB_DLL: Info: usb_set_debug: setting debugging level to 0 (off)

Is there an easy way to turn this off?

Thanks,
--Brian Hindman
P.S.  The codebase I'm working on can be found here:
http://www.maxim-ic.com/products/ibutton/software/1wire/wirekit.cfm
(hopefully, we will have a 64-bit Windows libusb build of it soon!)

> -----Original Message-----
> From: lib...@li...
> [mailto:lib...@li...]On Behalf Of
> Brian Hindman
> Sent: Monday, April 10, 2006 3:18 PM
> To: lib...@li...
> Subject: RE: [Libusb-win32-devel] 64-bit Windows libusb build - anyone
> do ne it yet?
> 
> 
> Hi.  I just used the batch files in the "checked build" with the 
> following setup:
> 
>  - WinXP (32-bit to do compiles)
>  - Server 2003 DKK, version 3790.1830
>  - "Windows Server 2003 Checked x64 Build Environment"
> 
> I used Cygwin cvs to get a brand new set of files about 2 hours
> ago.  Using the checked build, I had better luck (I could 
> compile with the 
> make_all batch file multiple times).  However, there were still 
> source files that were in the "Mac" format.  See partial printout
> of error messages below.  Looks like compiling with the batch files 
> under the "Checked" build is working ok (except for the "Mac file 
> format" error).
> 
> Do you think the "Mac" error could be my Cygwin/cvs settings?  
> 
> So, on my machine at least the batch files on a "Free" build 
> environment 
> still seems to have a few issues to be worked out...
> 
> On another note, for my "Free" environment builds, I was able to 
> install the resulting libusb0.sys (though, not with an inf file 
> produced by the inf-wizard.exe program as it wouldn't run).  However, 
> I modified a sample inf file and got it to install and be recognized 
> by Win XP X64.  The console testlibusb.exe ran and found my usb 
> device.  Now, I'm off to try to make headway compiling one of our 
> test apps against libusb for an AMD 64-bit machine...
> 
> --Brian Hindman
> 
> "errors in directory c:\cygwin\home\administrator\libusb\ddk_make
> abort_endpoint.c : error C1113: Mac file format detected: 
> please convert the
> sou
> rce file to either DOS or UNIX format
> Compiling - clear_feature.c for AMD64
> claim_interface.c : error C1113: Mac file format detected: 
> please convert
> the so
> urce file to either DOS or UNIX format
> Compiling - dispatch.c for AMD64
> clear_feature.c : error C1113: Mac file format detected: 
> please convert the
> sour
> ce file to either DOS or UNIX format
> Compiling - driver_registry.c for AMD64
> Compiling - get_configuration.c for AMD64
> Compiling - get_descriptor.c for AMD64
> get_configuration.c : error C1113: Mac file format detected: 
> please convert
> the
> source file to either DOS or UNIX format
> Compiling - get_interface.c for AMD64
> Compiling - get_status.c for AMD64
> Compiling - ioctl.c for AMD64
> get_status.c : error C1113: Mac file format detected: please 
> convert the
> source
> file to either DOS or UNIX format
> Compiling - libusb_driver.c for AMD64
> Compiling - pnp.c for AMD64
> Compiling - power.c for AMD64
> Compiling - release_interface.c for AMD64
> Compiling - reset_device.c for AMD64
> Compiling - reset_endpoint.c for AMD64
> reset_device.c : error C1113: Mac file format detected: 
> please convert the
> sourc
> e file to either DOS or UNIX format
> Compiling - set_configuration.c for AMD64
> reset_endpoint.c : error C1113: Mac file format detected: 
> please convert the
> sou
> rce file to either DOS or UNIX format
> Compiling - set_descriptor.c for AMD64
> Compiling - set_feature.c for AMD64
> set_descriptor.c : error C1113: Mac file format detected: 
> please convert the
> sou
> rce file to either DOS or UNIX format
> Compiling - set_interface.c for AMD64
> set_feature.c : error C1113: Mac file format detected: please 
> convert the
> source
>  file to either DOS or UNIX format
> Compiling - generating code... for AMD64
> Compiling - transfer.c for AMD64
> Compiling - vendor_request.c for AMD64
> Compiling - driver_debug.c for AMD64
> vendor_request.c : error C1113: Mac file format detected: 
> please convert the
> sou
> rce file to either DOS or UNIX format
> Compiling - generating code... for AMD64
> BUILD: Compile errors: not linking
> c:\cygwin\home\administrator\libusb\ddk_make
> directory
> BUILD: Done
> 
>     25 files compiled - 1 Warning - 10 Errors -  1016 LPS
> 
> > -----Original Message-----
> > From: lib...@li...
> > [mailto:lib...@li...]On Behalf Of
> > Stephan Meyer
> > Sent: Sunday, April 09, 2006 4:27 AM
> > To: lib...@li...
> > Subject: [Libusb-win32-devel] RE: [Libusb-win32-devel] 
> 64-bit Windows
> > libusb build - anyone do ne it yet?
> > 
> > 
> > 
> > 
> > > Stephen,
> > > 
> > > Thanks for that.  I was able to successfully 
> > > compile, but I was unable to use make_all.bat.  
> > > Each time I compiled, I could only compile one 
> > > item -- that is to say either libusb0.dll or 
> > > libusb0.sys or the inf wizard.  I was unable 
> > > to compile them all (or even two).  To make the 
> > > next binary, I would have to re-fetch from cvs.
> > 
> > I had no problems with any of the batch files using
> > to following setup:
> > 
> > - WinXP
> > - Server 2003 DKK, version 3790.1830
> > - "Windows Server 2003 Checked IA-64 Bit Build Environment"
> > - "Windows Server 2003 Checked x64 Build Environment"
> > 
> > > 
> > > Also, I got some warnings that the code files 
> > > were neither in DOS nor Unix text format (I'm 
> > > thinking it was a Mac format).  I was able to 
> > > fix that by performing a "dos2unix *" command 
> > > on all the source files.
> > 
> > I unix2dos-ified the whole codebase including all
> > build scripts and committed the changes to the CVS.
> > Maybe Windows' DDK can't handle UNIX file formats
> > properly. Please try the new version.
> > 
> > 
> > 
> > _______________________________________________________________
> > SMS schreiben mit WEB.DE FreeMail - einfach, schnell und
> > kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192
> > 
> > 
> > 
> > -------------------------------------------------------
> > This SF.Net email is sponsored by xPML, a groundbreaking 
> > scripting language
> > that extends applications into web and mobile media. Attend 
> > the live webcast
> > and join the prime developer group breaking into this new 
> > coding territory!
> > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&
> dat=121642
> _______________________________________________
> Libusb-win32-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
> 
> -- 
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.1.385 / Virus Database: 268.3.5/302 - Release 
> Date: 4/5/2006
>  
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by xPML, a groundbreaking 
> scripting language
> that extends applications into web and mobile media. Attend 
> the live webcast
> and join the prime developer group breaking into this new 
> coding territory!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&
dat=121642
_______________________________________________
Libusb-win32-devel mailing list
Lib...@li...
https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel

-- 
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.385 / Virus Database: 268.3.5/302 - Release Date: 4/5/2006
 

[Libusb-win32-devel] ddk errors

[Thomas S. <th...@th...>]

When I tried to compile a DLL with the 20051120 version with the 2003
DDK, I got the following output, and no DLL.  Is this supposed to work? 
I tried this in the WinXP and Win2003 Free and Checked build
environments.  It looks like make_all.bat did output a libusb.sys file
however.

T

C:\msys\home\swf\libusb-win32-src-20051120\ddk_make>make_dll.bat
        1 file(s) copied.
..\src\descriptors.c
..\src\error.c
..\src\inf_wizard.c
..\src\install.c
..\src\install_filter.c
..\src\libusb_dyn.c
..\src\registry.c
..\src\usb.c
..\src\windows.c
        9 file(s) copied.
..\libusb0.def
..\libusb0_drv.def
        2 file(s) copied.
..\src\error.h
..\src\registry.h
..\src\usb.h
..\src\usbi.h
        4 file(s) copied.
..\src\common.rc
..\src\inf_wizard_rc.rc
..\src\resource.rc
        3 file(s) copied.
        1 file(s) copied.
BUILD: Adding /Y to COPYCMD so xcopy ops won't hang.
BUILD: Using 2 child processes
BUILD: Object root set to: ==> objfre_wxp_x86
BUILD: Compile and Link for i386
BUILD: Loading C:\WINDDK\3790~1.183\build.dat...
BUILD: Computing Include file dependencies:
BUILD: Examining c:\msys\home\swf\libusb-win32-src-20051120\ddk_make
directory f
or files to compile.
    c:\msys\home\swf\libusb-win32-src-20051120\ddk_make - 7 source files
(4,155
lines)
BUILD: Compiling (NoSync)
c:\msys\home\swf\libusb-win32-src-20051120\ddk_make di
rectory
1>Compiling - resource.rc for i386
1>Compiling - windows.c for i386
1>Compiling - usb.c for i386
1>errors in directory c:\msys\home\swf\libusb-win32-src-20051120\ddk_make
1>usb.c(174) : error C2275: 'usb_dev_handle' : illegal use of this type
as an ex
pression
1>usb.c(174) : error C2065: 'udev' : undeclared identifier
1>usb.c(176) : error C4047: '=' : 'int' differs in levels of indirection
from 'u
sb_dev_handle *'
1>usb.c(178) : error C4047: 'function' : 'usb_dev_handle *' differs in
levels of
 indirection from 'int'
1>usb.c(180) : error C4047: 'function' : 'usb_dev_handle *' differs in
levels of
 indirection from 'int'
1>Compiling - error.c for i386
1>Compiling - install.c for i386
1>Compiling - descriptors.c for i386
1>Compiling - registry.c for i386
1>Compiling - generating code... for i386
BUILD: Compiling  c:\msys\home\swf\libusb-win32-src-20051120\ddk_make
directory
100>Compiling - usb.c for i386
100>usb.c(174) : error C2275: 'usb_dev_handle' : illegal use of this
type as an
expression
100>usb.c(174) : error C2065: 'udev' : undeclared identifier
100>usb.c(176) : error C4047: '=' : 'int' differs in levels of
indirection from
'usb_dev_handle *'
100>usb.c(178) : error C4047: 'function' : 'usb_dev_handle *' differs in
levels
of indirection from 'int'
100>usb.c(180) : error C4047: 'function' : 'usb_dev_handle *' differs in
levels
of indirection from 'int'
100>Building Library - objfre_wxp_x86\i386\libusb0.lib for i386
100>LIB : error LNK1181: cannot open input file
'objfre_wxp_x86\i386\usb.obj'
BUILD: Compile errors: not linking
c:\msys\home\swf\libusb-win32-src-20051120\dd
k_make directory
BUILD: Done

    10 files compiled - 10 Errors -  1495 LPS
    1 library built - 1 Error

C:\msys\home\swf\libusb-win32-src-20051120\ddk_make>

RE: [Libusb-win32-devel] 64-bit Windows libusb build - anyone do ne it yet?

[Brian H. <Bri...@da...>]

Hi.  I just used the batch files in the "checked build" with the 
following setup:

 - WinXP (32-bit to do compiles)
 - Server 2003 DKK, version 3790.1830
 - "Windows Server 2003 Checked x64 Build Environment"

I used Cygwin cvs to get a brand new set of files about 2 hours
ago.  Using the checked build, I had better luck (I could compile with the 
make_all batch file multiple times).  However, there were still 
source files that were in the "Mac" format.  See partial printout
of error messages below.  Looks like compiling with the batch files 
under the "Checked" build is working ok (except for the "Mac file 
format" error).

Do you think the "Mac" error could be my Cygwin/cvs settings?  

So, on my machine at least the batch files on a "Free" build environment 
still seems to have a few issues to be worked out...

On another note, for my "Free" environment builds, I was able to 
install the resulting libusb0.sys (though, not with an inf file 
produced by the inf-wizard.exe program as it wouldn't run).  However, 
I modified a sample inf file and got it to install and be recognized 
by Win XP X64.  The console testlibusb.exe ran and found my usb 
device.  Now, I'm off to try to make headway compiling one of our 
test apps against libusb for an AMD 64-bit machine...

--Brian Hindman

"errors in directory c:\cygwin\home\administrator\libusb\ddk_make
abort_endpoint.c : error C1113: Mac file format detected: please convert the
sou
rce file to either DOS or UNIX format
Compiling - clear_feature.c for AMD64
claim_interface.c : error C1113: Mac file format detected: please convert
the so
urce file to either DOS or UNIX format
Compiling - dispatch.c for AMD64
clear_feature.c : error C1113: Mac file format detected: please convert the
sour
ce file to either DOS or UNIX format
Compiling - driver_registry.c for AMD64
Compiling - get_configuration.c for AMD64
Compiling - get_descriptor.c for AMD64
get_configuration.c : error C1113: Mac file format detected: please convert
the
source file to either DOS or UNIX format
Compiling - get_interface.c for AMD64
Compiling - get_status.c for AMD64
Compiling - ioctl.c for AMD64
get_status.c : error C1113: Mac file format detected: please convert the
source
file to either DOS or UNIX format
Compiling - libusb_driver.c for AMD64
Compiling - pnp.c for AMD64
Compiling - power.c for AMD64
Compiling - release_interface.c for AMD64
Compiling - reset_device.c for AMD64
Compiling - reset_endpoint.c for AMD64
reset_device.c : error C1113: Mac file format detected: please convert the
sourc
e file to either DOS or UNIX format
Compiling - set_configuration.c for AMD64
reset_endpoint.c : error C1113: Mac file format detected: please convert the
sou
rce file to either DOS or UNIX format
Compiling - set_descriptor.c for AMD64
Compiling - set_feature.c for AMD64
set_descriptor.c : error C1113: Mac file format detected: please convert the
sou
rce file to either DOS or UNIX format
Compiling - set_interface.c for AMD64
set_feature.c : error C1113: Mac file format detected: please convert the
source
 file to either DOS or UNIX format
Compiling - generating code... for AMD64
Compiling - transfer.c for AMD64
Compiling - vendor_request.c for AMD64
Compiling - driver_debug.c for AMD64
vendor_request.c : error C1113: Mac file format detected: please convert the
sou
rce file to either DOS or UNIX format
Compiling - generating code... for AMD64
BUILD: Compile errors: not linking
c:\cygwin\home\administrator\libusb\ddk_make
directory
BUILD: Done

    25 files compiled - 1 Warning - 10 Errors -  1016 LPS

> -----Original Message-----
> From: lib...@li...
> [mailto:lib...@li...]On Behalf Of
> Stephan Meyer
> Sent: Sunday, April 09, 2006 4:27 AM
> To: lib...@li...
> Subject: [Libusb-win32-devel] RE: [Libusb-win32-devel] 64-bit Windows
> libusb build - anyone do ne it yet?
> 
> 
> 
> 
> > Stephen,
> > 
> > Thanks for that.  I was able to successfully 
> > compile, but I was unable to use make_all.bat.  
> > Each time I compiled, I could only compile one 
> > item -- that is to say either libusb0.dll or 
> > libusb0.sys or the inf wizard.  I was unable 
> > to compile them all (or even two).  To make the 
> > next binary, I would have to re-fetch from cvs.
> 
> I had no problems with any of the batch files using
> to following setup:
> 
> - WinXP
> - Server 2003 DKK, version 3790.1830
> - "Windows Server 2003 Checked IA-64 Bit Build Environment"
> - "Windows Server 2003 Checked x64 Build Environment"
> 
> > 
> > Also, I got some warnings that the code files 
> > were neither in DOS nor Unix text format (I'm 
> > thinking it was a Mac format).  I was able to 
> > fix that by performing a "dos2unix *" command 
> > on all the source files.
> 
> I unix2dos-ified the whole codebase including all
> build scripts and committed the changes to the CVS.
> Maybe Windows' DDK can't handle UNIX file formats
> properly. Please try the new version.
> 
> 
> 
> _______________________________________________________________
> SMS schreiben mit WEB.DE FreeMail - einfach, schnell und
> kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by xPML, a groundbreaking 
> scripting language
> that extends applications into web and mobile media. Attend 
> the live webcast
> and join the prime developer group breaking into this new 
> coding territory!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&
dat=121642
_______________________________________________
Libusb-win32-devel mailing list
Lib...@li...
https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel

-- 
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.385 / Virus Database: 268.3.5/302 - Release Date: 4/5/2006
 

Re: [Libusb-win32-devel] usb_find_busses prints number of busses

[Stephan M. <ste...@we...>]

I already fixed this bug. Changes are in the CVS.

> I notice that usb_find_busses() (or rather, usb_os_find_busses() in 
> windows.c) prints the number of busses found to stdout every time it is 
> called. Is there any reason why this is done, rather than doing so only 
> if debug is turned on?
> 
> This is with version 0.1.10.1, which as far as I can tell is the latest.
> 
> Mark.
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by xPML, a groundbreaking scripting language
> that extends applications into web and mobile media. Attend the live webcast
> and join the prime developer group breaking into this new coding territory!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
> _______________________________________________
> Libusb-win32-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel


_______________________________________________________________
SMS schreiben mit WEB.DE FreeMail - einfach, schnell und
kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192

[Libusb-win32-devel] =?iso-8859-15?Q?RE:_[Libusb-win32-devel]_64-bit_Windows__libusb_build_?= =?iso-8859-15?Q?-_anyone_do_ne_it_yet=3F?=

[Stephan M. <ste...@we...>]

> Stephen,
> 
> Thanks for that.  I was able to successfully 
> compile, but I was unable to use make_all.bat.  
> Each time I compiled, I could only compile one 
> item -- that is to say either libusb0.dll or 
> libusb0.sys or the inf wizard.  I was unable 
> to compile them all (or even two).  To make the 
> next binary, I would have to re-fetch from cvs.

I had no problems with any of the batch files using
to following setup:

- WinXP
- Server 2003 DKK, version 3790.1830
- "Windows Server 2003 Checked IA-64 Bit Build Environment"
- "Windows Server 2003 Checked x64 Build Environment"

> 
> Also, I got some warnings that the code files 
> were neither in DOS nor Unix text format (I'm 
> thinking it was a Mac format).  I was able to 
> fix that by performing a "dos2unix *" command 
> on all the source files.

I unix2dos-ified the whole codebase including all
build scripts and committed the changes to the CVS.
Maybe Windows' DDK can't handle UNIX file formats
properly. Please try the new version.



_______________________________________________________________
SMS schreiben mit WEB.DE FreeMail - einfach, schnell und
kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192

[Libusb-win32-devel] usb_find_busses prints number of busses

[Mark B. <mc...@ec...>]

I notice that usb_find_busses() (or rather, usb_os_find_busses() in 
windows.c) prints the number of busses found to stdout every time it is 
called. Is there any reason why this is done, rather than doing so only 
if debug is turned on?

This is with version 0.1.10.1, which as far as I can tell is the latest.

Mark.

RE: [Libusb-win32-devel] 64-bit Windows libusb build - anyone do ne it yet?

[Brian H. <Bri...@da...>]

Stephen,

Thanks for that.  I was able to successfully 
compile, but I was unable to use make_all.bat.  
Each time I compiled, I could only compile one 
item -- that is to say either libusb0.dll or 
libusb0.sys or the inf wizard.  I was unable 
to compile them all (or even two).  To make the 
next binary, I would have to re-fetch from cvs.

Also, I got some warnings that the code files 
were neither in DOS nor Unix text format (I'm 
thinking it was a Mac format).  I was able to 
fix that by performing a "dos2unix *" command 
on all the source files.

I was able to compile the following for X64 (or, 
at least AMD64):
1)  libusb0.sys
2)  libusb0.dll
3)  infwizard.exe
4)  testlibusb.exe

I couldn't compile the Windows version of the test program.

Anyway, I should have enough to start testing on 
Windows XP 64 (and possibly even on Windows Vista X64 Beta 1).  

I'll try to report back what I find.  Let me know if 
I should watch out for any "gotchas".  I'm basically trying to 
move some libraries/executables over to X64 for my company's 
USB device.  We previously had a build of our code against 
regular old X86 libusb for Windows.

Thanks again,
--Brian Hindman

> -----Original Message-----
> From: lib...@li...
> [mailto:lib...@li...]On Behalf Of
> Stephan Meyer
> Sent: Thursday, April 06, 2006 12:27 PM
> To: lib...@li...
> Subject: [Libusb-win32-devel] Re: [Libusb-win32-devel] 64-bit Windows
> libusb build - anyone done it yet?
> 
> 
> 
> I fixed it. A new version (new .bat files) is in the CVS.
> The problem was that the old batch files didn't properly
> remove temporary files when they were run from a 
> "free build environment"
>  
> > Stephen,
> > 
> > Hi.  I now have a test setup with a 64-bit AMD machine.  
> However, I was 
> > unable to compile the *.sys driver with Server 2003 DDK x64 build 
> > environment.
> > 
> > See below for the errors (after retrieving libusb CVS code 
> earlier in the
> > day).
> > Looks like there are quite a few "unresolved external 
> symbols".  Is there a 
> > missing file or include somewhere?
> > 
> > Please help if you can.
> > 
> > By the way, the filter driver seemed to compile and link 
> correctly :)
> > 
> > Thanks,
> > --Brian Hindman
> > 
> 
> 
> 
> _______________________________________________________________
> SMS schreiben mit WEB.DE FreeMail - einfach, schnell und
> kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by xPML, a groundbreaking 
> scripting language
> that extends applications into web and mobile media. Attend 
> the live webcast
> and join the prime developer group breaking into this new 
> coding territory!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&
dat=121642
_______________________________________________
Libusb-win32-devel mailing list
Lib...@li...
https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel

-- 
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.385 / Virus Database: 268.3.5/302 - Release Date: 4/5/2006
 

[Libusb-win32-devel] =?iso-8859-15?Q?Re:_[Libusb-win32-devel]_64-bit_Windows__libusb_build_?= =?iso-8859-15?Q?-_anyone_done_it_yet=3F?=

[Stephan M. <ste...@we...>]

I fixed it. A new version (new .bat files) is in the CVS.
The problem was that the old batch files didn't properly
remove temporary files when they were run from a 
"free build environment"
 
> Stephen,
> 
> Hi.  I now have a test setup with a 64-bit AMD machine.  However, I was 
> unable to compile the *.sys driver with Server 2003 DDK x64 build 
> environment.
> 
> See below for the errors (after retrieving libusb CVS code earlier in the
> day).
> Looks like there are quite a few "unresolved external symbols".  Is there a 
> missing file or include somewhere?
> 
> Please help if you can.
> 
> By the way, the filter driver seemed to compile and link correctly :)
> 
> Thanks,
> --Brian Hindman
> 



_______________________________________________________________
SMS schreiben mit WEB.DE FreeMail - einfach, schnell und
kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192

RE: [Libusb-win32-devel] RE: 64-bit Windows

[Brian H. <Bri...@da...>]

Bill,

Hi.  As promised, here's my 32-bit (X86) build log file...

--Brian Hindman

=========================
BUILD: Computing Include file dependencies:
BUILD: Examining c:\cygwin\home\administrator\libusb\ddk_make directory for
files to compile.
Compiling (NoSync) c:\cygwin\home\administrator\libusb\ddk_make directory
********************
'nmake.exe /nologo BUILDMSG=Stop. -i NTTEST= UMTEST= NOLINK=1 NOPASS0=1
386=1'

Stop.
Linking c:\cygwin\home\administrator\libusb\ddk_make directory
********************
'nmake.exe /nologo BUILDMSG=Stop. -i LINKONLY=1 NOPASS0=1 NTTEST= UMTEST=
386=1'
	link -out:output\i386\inf-wizard.exe -machine:ix86
@C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\nm108D.tmp
Microsoft (R) Incremental Linker Version 7.10.4035
Copyright (C) Microsoft Corporation.  All rights reserved.

-MERGE:_PAGE=PAGE 
-MERGE:_TEXT=.text 
-SECTION:INIT,d 
-OPT:REF 
-OPT:ICF 
-IGNORE:4198,4010,4037,4039,4065,4070,4078,4087,4089,4221 
-INCREMENTAL:NO 
-FULLBUILD 
/release 
-NODEFAULTLIB 
/WX 
-debug 
-debugtype:cv 
-version:5.2 
-osversion:5.2 
/functionpadmin:5 
/safeseh 
/opt:nowin98 
-merge:.rdata=.text 
/pdbcompress 
-STACK:0x40000,0x2000 
/tsaware 
-subsystem:windows,4.00 
-base:@C:\WINDDK\3790~1.183\bin\coffbase.txt,usermode 
-entry:WinMainCRTStartup 
objfre_wnet_x86\i386\resource.res 
objfre_wnet_x86\i386\windows.obj 
objfre_wnet_x86\i386\usb.obj 
objfre_wnet_x86\i386\error.obj 
objfre_wnet_x86\i386\install.obj 
objfre_wnet_x86\i386\descriptors.obj 
objfre_wnet_x86\i386\registry.obj 
C:\WINDDK\3790~1.183\lib\wnet\i386\BufferOverflowU.lib 
C:\WINDDK\3790~1.183\lib\crt\i386\msvcrt.lib 
C:\WINDDK\3790~1.183\lib\wnet\i386\advapi32.lib 
C:\WINDDK\3790~1.183\lib\wnet\i386\kernel32.lib 
C:\WINDDK\3790~1.183\lib\wnet\i386\gdi32.lib 
C:\WINDDK\3790~1.183\lib\wnet\i386\user32.lib 
C:\WINDDK\3790~1.183\lib\wnet\i386\setupapi.lib 
C:\WINDDK\3790~1.183\lib\wnet\i386\kernel32.lib 
C:\WINDDK\3790~1.183\lib\wnet\i386\advapi32.lib 
C:\WINDDK\3790~1.183\lib\wnet\i386\user32.lib 
C:\WINDDK\3790~1.183\lib\wnet\i386\comctl32.lib 
C:\WINDDK\3790~1.183\lib\wnet\i386\comdlg32.lib 
msvcrt.lib(crtexew.obj) : error LNK2019: unresolved external symbol
_WinMain@16 referenced in function _WinMainCRTStartup
output\i386\inf-wizard.exe : fatal error LNK1120: 1 unresolved externals
	echo Skip Binplace:
Skip Binplace:

Stop.

> -----Original Message-----
> From: lib...@li...
> [mailto:lib...@li...]On 
> Behalf Of Bill
> Lewis
> Sent: Thursday, April 06, 2006 11:21 AM
> To: lib...@li...
> Subject: Re: [Libusb-win32-devel] RE: 64-bit Windows
> 
> 
> I have been building successfully with the 2003 DDK build 3790.1830.
> 
> I am using the Free build, for WXP.
> 
> Can you post your buildfre_wxp_x86.log (or whatever yours is called)?
> 
> Bill
> 
> --- Brian Hindman <Bri...@da...> wrote:
> 
> > A small update:
> > 
> > Since I was not able to compile the libusb *.sys driver 
> > with Microsoft's DDK (Windows Server 2003 SP1) under the 
> > X64 free build environment, I decided to fall back to the 
> > regular X86 free build environment, and got the same 
> > errors (see previous e-mail message below).  I checked out 
> > the libusb code from CVS yesterday...
> > 
> > If someone can compile successfully using the ddk_make 
> > subdirectory, please point me in the right direction :)
> > 
> > Thanks,
> > --Brian Hindman
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by xPML, a groundbreaking 
> scripting language
> that extends applications into web and mobile media. Attend 
> the live webcast
> and join the prime developer group breaking into this new 
> coding territory!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&
dat=121642
_______________________________________________
Libusb-win32-devel mailing list
Lib...@li...
https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel

-- 
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.385 / Virus Database: 268.3.5/302 - Release Date: 4/5/2006
 

RE: [Libusb-win32-devel] RE: 64-bit Windows

[Brian H. <Bri...@da...>]

Bill,

Hi.  I'm not sure which to post, so I'll post the 64-bit log 
file (which is buildfre_wnet_AMD64.log).

My DDK is also 3790.1830.  I will post my X86 log file separately...

See below,
--Brian Hindman
P.S.  Thanks for taking a look

===========================
BUILD: Computing Include file dependencies:
BUILD: Examining c:\cygwin\home\administrator\libusb\ddk_make directory for
files to compile.
Compiling (NoSync) c:\cygwin\home\administrator\libusb\ddk_make directory
********************
'nmake.exe /nologo BUILDMSG=Stop. -i NTTEST= UMTEST= NOLINK=1 NOPASS0=1
AMD64=1'
	lib -out:output\amd64\libusb0.lib
@C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\nm126.tmp
Microsoft (R) Library Manager Version 8.00.40310.39
Copyright (C) Microsoft Corporation.  All rights reserved.

-IGNORE:4198,4010,4037,4039,4065,4070,4078,4087,4089,4221,4108,4088,4218 
/WX 
-nodefaultlib 
-machine:amd64 
-def:libusb0.def 
objfre_wnet_AMD64\amd64\resource.res 
objfre_wnet_AMD64\amd64\windows.obj 
objfre_wnet_AMD64\amd64\usb.obj 
objfre_wnet_AMD64\amd64\error.obj 
objfre_wnet_AMD64\amd64\install.obj 
objfre_wnet_AMD64\amd64\descriptors.obj 
objfre_wnet_AMD64\amd64\registry.obj 
   Creating library output\amd64\libusb0.lib and object
output\amd64\libusb0.exp

Stop.
Linking c:\cygwin\home\administrator\libusb\ddk_make directory
********************
'nmake.exe /nologo BUILDMSG=Stop. -i LINKONLY=1 NOPASS0=1 NTTEST= UMTEST=
MAKEDLL=1 AMD64=1'
	link -out:output\amd64\libusb0.dll -machine:amd64
@C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\nm128.tmp
Microsoft (R) Incremental Linker Version 8.00.40310.39
Copyright (C) Microsoft Corporation.  All rights reserved.

-MERGE:_PAGE=PAGE 
-MERGE:_TEXT=.text 
-SECTION:INIT,d 
-OPT:REF 
-OPT:ICF 
-IGNORE:4198,4010,4037,4039,4065,4070,4078,4087,4089,4221,4108,4088,4218 
-INCREMENTAL:NO 
-FULLBUILD 
/release 
-NODEFAULTLIB 
/WX 
-debug 
-debugtype:cv 
-version:5.2 
-osversion:5.2 
-debug 
-debugtype:cv,fixup,pdata 
/opt:nowin98 
C:\WINDDK\3790~1.183\lib\wnet\amd64\hotpatch.obj 
/functionpadmin:6 
-merge:.rdata=.text 
/pdbcompress 
-STACK:0x40000,0x1000 
-dll 
-base:@C:\WINDDK\3790~1.183\bin\coffbase.txt,libusb0 
-subsystem:console,4.10 
-entry:_DllMainCRTStartup 
output\amd64\libusb0.exp 
objfre_wnet_AMD64\amd64\resource.res 
objfre_wnet_AMD64\amd64\windows.obj 
objfre_wnet_AMD64\amd64\usb.obj 
objfre_wnet_AMD64\amd64\error.obj 
objfre_wnet_AMD64\amd64\install.obj 
objfre_wnet_AMD64\amd64\descriptors.obj 
objfre_wnet_AMD64\amd64\registry.obj 
C:\WINDDK\3790~1.183\lib\wnet\amd64\BufferOverflowU.lib 
C:\WINDDK\3790~1.183\lib\crt\amd64\msvcrt.lib 
C:\WINDDK\3790~1.183\lib\wnet\amd64\ntdll.lib 
C:\WINDDK\3790~1.183\lib\wnet\amd64\setupapi.lib 
C:\WINDDK\3790~1.183\lib\wnet\amd64\kernel32.lib 
C:\WINDDK\3790~1.183\lib\wnet\amd64\advapi32.lib 
C:\WINDDK\3790~1.183\lib\wnet\amd64\user32.lib 
	echo Skip Binplace:
Skip Binplace:

Stop.



> -----Original Message-----
> From: lib...@li...
> [mailto:lib...@li...]On 
> Behalf Of Bill
> Lewis
> Sent: Thursday, April 06, 2006 11:21 AM
> To: lib...@li...
> Subject: Re: [Libusb-win32-devel] RE: 64-bit Windows
> 
> 
> I have been building successfully with the 2003 DDK build 3790.1830.
> 
> I am using the Free build, for WXP.
> 
> Can you post your buildfre_wxp_x86.log (or whatever yours is called)?
> 
> Bill
> 
> --- Brian Hindman <Bri...@da...> wrote:
> 
> > A small update:
> > 
> > Since I was not able to compile the libusb *.sys driver 
> > with Microsoft's DDK (Windows Server 2003 SP1) under the 
> > X64 free build environment, I decided to fall back to the 
> > regular X86 free build environment, and got the same 
> > errors (see previous e-mail message below).  I checked out 
> > the libusb code from CVS yesterday...
> > 
> > If someone can compile successfully using the ddk_make 
> > subdirectory, please point me in the right direction :)
> > 
> > Thanks,
> > --Brian Hindman
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by xPML, a groundbreaking 
> scripting language
> that extends applications into web and mobile media. Attend 
> the live webcast
> and join the prime developer group breaking into this new 
> coding territory!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&
dat=121642
_______________________________________________
Libusb-win32-devel mailing list
Lib...@li...
https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel

-- 
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.385 / Virus Database: 268.3.5/302 - Release Date: 4/5/2006
 

Re: [Libusb-win32-devel] RE: 64-bit Windows

[Bill L. <wr...@ya...>]

I have been building successfully with the 2003 DDK build 3790.1830.

I am using the Free build, for WXP.

Can you post your buildfre_wxp_x86.log (or whatever yours is called)?

Bill

--- Brian Hindman <Bri...@da...> wrote:

> A small update:
> 
> Since I was not able to compile the libusb *.sys driver 
> with Microsoft's DDK (Windows Server 2003 SP1) under the 
> X64 free build environment, I decided to fall back to the 
> regular X86 free build environment, and got the same 
> errors (see previous e-mail message below).  I checked out 
> the libusb code from CVS yesterday...
> 
> If someone can compile successfully using the ddk_make 
> subdirectory, please point me in the right direction :)
> 
> Thanks,
> --Brian Hindman