On Wed, Apr 7, 2010 at 11:11 AM, Xiaofan Chen wrote:
> This is the test result now with testall.py (removing all those debug
> information from libusb 1.0 Windows).
It seems to me that libusb-1.0.dll debugging information will disturb
the results. So I build it under Cygwin again to remove the d
For normal Windows Python 2.5 and 2.6, I have the same results.
C:\cygwin\home\mcuee\mcu\pyusb\pyusb\tests>set PYUSB_DEBUG_LEVEL=debug
C:\cygwin\home\mcuee\mcu\pyusb\pyusb\tests>c:\Python25\python.exe testall.py
2010-04-07 11:17:04,351 DEBUG:usb.backend.libusb10:Error loading libusb 1.0 back
end
On Wed, Apr 7, 2010 at 11:04 AM, Xiaofan Chen wrote:
> On Wed, Apr 7, 2010 at 8:58 AM, Wander Lairson
> wrote:
>> wan...@darkstar /cygdrive/c/Projetos/pyusb/trunk
>> $ python
>> Python 2.5.5 (r255:77872, Mar 15 2010, 00:43:13)
>> [GCC 4.3.4 20090804 (release) 1] on cygwin
>> Type "help", "copyri
On Wed, Apr 7, 2010 at 8:58 AM, Wander Lairson wrote:
> wan...@darkstar /cygdrive/c/Projetos/pyusb/trunk
> $ python
> Python 2.5.5 (r255:77872, Mar 15 2010, 00:43:13)
> [GCC 4.3.4 20090804 (release) 1] on cygwin
> Type "help", "copyright", "credits" or "license" for more information.
Ah, I update
On Wed, Apr 7, 2010 at 9:29 AM, Wander Lairson wrote:
> By the way, it feels like the problem with libusb_init is that it
> cannot load winusb.dll, but I haven't debug enough to be sure about
> that...
>
> 2010/4/6 Wander Lairson :
>> Kind of strange, for libusb 1.0 fails on libusb_init call, and
By the way, it feels like the problem with libusb_init is that it
cannot load winusb.dll, but I haven't debug enough to be sure about
that...
2010/4/6 Wander Lairson :
> Kind of strange, for libusb 1.0 fails on libusb_init call, and libusb
> 0.1 is sucessfully loaded:
>
>
> wan...@darkstar /cygdri
Kind of strange, for libusb 1.0 fails on libusb_init call, and libusb
0.1 is sucessfully loaded:
wan...@darkstar /cygdrive/c/Projetos/pyusb/trunk
$ python
Python 2.5.5 (r255:77872, Mar 15 2010, 00:43:13)
[GCC 4.3.4 20090804 (release) 1] on cygwin
Type "help", "copyright", "credits" or "license" f
On Tue, Apr 6, 2010 at 10:09 PM, Wander Lairson
wrote:
> Oh, I haven't realized that the problem was just library names...
> Sorry making you loosing your time.. I updated the code to support
> cygwin libraries, rev 58 should work.
>
Unfortunately not, Cygwin seems to be a bit different.
mc...@a
On Tue, Apr 6, 2010 at 10:28 PM, Wander Lairson
wrote:
> I haven't cygwin environment here, so I tested against my default
> Python installation and got it the same error. I guess we should test
> it with python which comes with cygwin. I will try it on my home
> machine.
>
>> C:\cygwin\home\mcuee
I haven't cygwin environment here, so I tested against my default
Python installation and got it the same error. I guess we should test
it with python which comes with cygwin. I will try it on my home
machine.
Wander
2010/4/6 Xiaofan Chen :
> On Tue, Apr 6, 2010 at 9:26 PM, Wander Lairson
> wro
On Tue, Apr 6, 2010 at 9:26 PM, Wander Lairson wrote:
> I added some preliminary log support to PyUSB at revision 56, it uses
> the logging module. Currently, you can define the environment variable
> PYUSB_DEBUG_LEVEL with the following values: critical, error, warning,
> information, debug. Runn
Oh, I haven't realized that the problem was just library names...
Sorry making you loosing your time.. I updated the code to support
cygwin libraries, rev 58 should work.
Wander
2010/4/6 Xiaofan Chen :
> On Tue, Apr 6, 2010 at 9:29 PM, Wander Lairson
> wrote:
>> Please, try again with rev 56, a
On Tue, Apr 6, 2010 at 9:29 PM, Wander Lairson wrote:
> Please, try again with rev 56, and define the env variable
> PYUSB_DEBUG_LEVEL=debug. Let's what it says to us...
>
mc...@acerpc ~
$ python
Python 2.5.2 (r252:60911, Dec 2 2008, 09:26:14)
[GCC 3.4.4 (cygming special, gdc 0.12, using dmd 0.1
Please, try again with rev 56, and define the env variable
PYUSB_DEBUG_LEVEL=debug. Let's what it says to us...
Wander
2010/4/6 Xiaofan Chen :
> I am not so sure why pyusb can not find the backend
> under Cygwin Python (latest svn). Kind of strange.
>
> I have cygusb0.dll and cygusb-1.0.dll under
I added some preliminary log support to PyUSB at revision 56, it uses
the logging module. Currently, you can define the environment variable
PYUSB_DEBUG_LEVEL with the following values: critical, error, warning,
information, debug. Running tests with debug defined, explain why
get_backend failed wi
I am not so sure why pyusb can not find the backend
under Cygwin Python (latest svn). Kind of strange.
I have cygusb0.dll and cygusb-1.0.dll under
c:\cygwin\bin and they are the DLL name for
libusb-win32 0.1 and libusb 1.0 Windows under
Cygwin respectively.
I even tried to add 'cygusb0' and 'cygu
On Mon, Apr 5, 2010 at 6:46 PM, Wander Lairson wrote:
> When I port 1.0 windows backend, I will check. But maybe not in time
> for alpha 0 release.
No problem. Take your time. I just think pyusb will be a nice test
bed for libusb 1.0 Windows backend as well.
It seems to me that libusb 0.1 backe
17 matches
Mail list logo
