Re: [Libusb-devel] Windows backend on XP x64

[Jerome V. <jer...@gm...>]

2010/4/15 Michael Plante <mic...@gm...>:
> Jerome Vuarand wrote:
>>> Also, there is some work to do about stdint.h, since none is present
>>> in the the Windows SDK (I don't know about the DDK). However I don't
>>> think that's the source of the problem.
>
> "some work" as in you also want stdint.h in the binary dist?

Some work as in : realizing that the header is missing, checking
whether it's something from Unix of from C, whether it should be
shipped with the compiler or the SDK, find an implementation
compatible with a given toolchain, choose the right one among the
several implementations you can find.

I think a simple mention of the file and eventually a link to a
correct one would be enough. When I got the compilation error, I did a
grep "stdint" in the Windows backend wiki page, and a simple "Several
Microsoft toolchains come without stdint.h, you have to find a
compatible implementation yourself." would have helped.

It's the first time I realize VC++ toolchains lack that file, but I
guess it may be a common porting issue, so maybe there are already
usual solutions. However as far as I can tell I wouldn't recommend
putting stdint.h in the binary dist. Maybe moving the inclusion to a
#ifndef MSC_VER block, and adding the necessary typedefs would be
better. However I'm too new to that problem to tell you the better
solution.

>>> Also, I looked at libusb code, and noticed that there are a lot of
>>> debug logs in the form of calls to usbi_log and similar functions. Is
>>> there a way to extract these logs somehow even when libusb_init fails
>>> ?
>
> What do you mean by "extract"?  Are you saying you want to sort by message
> type of some sort, or are you saying you're not seeing log messages at all?

I'm not seeing any log at all in the console of my program. Should I
look elsewhere (a file, the system event log, etc.) ?