brary that
is provided by Cypress). I have build libcyusbserial on NetBSD and Linux
and both libraries run as expected. This last library uses libusb 1.0.
Under cygwin, I have built my program without trouble, but it is not
usable.
$ lsusb
...
Bus 001 Device 003: ID 04b4:0004 Cypress Semicond
On 13/06/2017 01:18, Chris Johnson wrote:
Hi.
Never run into this before. Running Win7 and installing cygwin via
setup-x86_64 v2.879.
I kept running into categories I couldn't install due to a missing
libUSB-W32 driver. Some of the categories are
Devel
Math
Net
Publishing
Python
I g
Hi.
Never run into this before. Running Win7 and installing cygwin via
setup-x86_64 v2.879.
I kept running into categories I couldn't install due to a missing
libUSB-W32 driver. Some of the categories are
Devel
Math
Net
Publishing
Python
I get an error about libusb0, says I ne
Greetings. I installed the current cygwin on a Win32 system specifically to
use libusb functions. This mostly works, except it appears that the library
doesn't see one particular USB device, even though its driver loads and the
associated Windows app works OK. Unfortunately, I need t
On 04/11/2015 21:09, Yaakov Selkowitz wrote:
On Wed, 2015-11-04 at 19:10 +0100, Achim Gratz wrote:
KIMURA Masaru writes:
can someone bump libusb packages to v1.0.20 or HEAD?
You could try to adopt the package…
A bit extreme, don't you think?
--
Yaakov
I guess he forgot to chec
On Wed, 2015-11-04 at 19:10 +0100, Achim Gratz wrote:
> KIMURA Masaru writes:
> > can someone bump libusb packages to v1.0.20 or HEAD?
>
> You could try to adopt the package…
A bit extreme, don't you think?
--
Yaakov
--
Problem reports: http://cygwin.c
KIMURA Masaru writes:
> can someone bump libusb packages to v1.0.20 or HEAD?
You could try to adopt the package…
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Waldorf MIDI Implementation & additional documentation:
http://Synth
Hi,
can someone bump libusb packages to v1.0.20 or HEAD?
FYI, v1.0.20 and HEAD have a compilation issue[1],
was already reported to the upstream, but is not fixed ATM.
Peace,
-
[1] https://github.com/libusb/libusb/issues/104
-
$ cygcheck -c -d libusb1.0 libusb1.0-devel
Cygwin Package
I'm working on a product that needs libusb to work in a cygwin process,
but there's a problem. The released version (1.0.19) doesn't support
two very fundamental features: pollfds and hotplug. I see strong
indications that the current git version *does* have these features, s
The following packages have been updated for both arches:
* libusb0-1.2.6.0-1
* libusb-devel-1.2.6.0-1
* libusb1.0-1.0.17-1
* libusb1.0-devel-1.0.17-1
LibUSB is a library that provides generic access to USB devices.
As a library, it is meant to be used by developers, to facilitate the
The libusb package uses the presence of _WIN32 to determine which
calling convention to use for the library externals - if _WIN32 is
defined it uses WINAPI. [See /usr/include/libusb-1.0/libusb.h.]
There is of course the question of whether it is/was sensible to use
WINAPI when the package is
Version 1.2.5.0-1 of "libusb-win32" has been uploaded.
This is a new upstream release, the filter installer is not shipped any
more as it does not build on cygwin any more.
It is a library that allows userspace application to access USB
devices on Windows operation systems (Win9
he user will have to install the driver and
> filter separately from the upstream installer.
Yes, especially as with newer 64bit Windows OSs, drivers must be
digitally signed -- which means the build (you?) would need to purchase
a digital cert... libusb has already done this, and their builds
Lars Bjørndal, le Fri 12 Aug 2011 16:13:53 +0200, a écrit :
> The available package seems to be outdated, and makes trouble on Windows
> 7 64 bit. Is there plans for updating the package for cygwin?
Just a matter of my finding some time to do it. I deferred it quite
a bit since newer versions are
The available package seems to be outdated, and makes trouble on Windows
7 64 bit. Is there plans for updating the package for cygwin?
Lars
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Un
Xiaofan Chen schrieb:
Just wondering if I can have the answer here. Thanks.
Please CC me as I am not subscribed. Thanks.
> The author asks if Cygwin libusb-1.0 should use stdcall or not?
> > http://sourceforge.net/mailarchive/message.php?msg_id=26873777
> >
> > Normal Pyt
Just wondering if I can have the answer here. Thanks.
Please CC me as I am not subscribed. Thanks.
--
Xiaofan
-- Forwarded message --
From: Andrew MacIntyre
Date: Tue, Jan 11, 2011 at 1:24 PM
Subject: RE: [ctypes-users] pyusb under Cygwin and stdcall libusb-1.0
[SEC
On 2010-04-26 08:27, Samuel Thibault wrote:
Version 1.0.7+gitbd62c472-1 of "libusb-1.0" has been uploaded.
It is a library that allows userspace application to access USB
devices on WinUSB-compatible Windows operation systems (WinXP, Vista, and 7).
It is being integrated and
Version 1.0.7+gitbd62c472-1 of "libusb-1.0" has been uploaded.
It is a library that allows userspace application to access USB
devices on WinUSB-compatible Windows operation systems (WinXP, Vista, and 7).
It is being integrated and fully API compatible to libusb availab
On Tue, Mar 16, 2010 at 3:52 PM, Jeremy Bopp wrote:
> On 3/16/2010 2:44 PM, Gregg Levine wrote:
>> Hello!
>> Where would I find out what the version of LibUSB that is supplied with
>> Cygwin?
>
> http://cygwin.com/packages/
>
> -Jeremy
Hello!
An excellent respo
On 3/16/2010 2:44 PM, Gregg Levine wrote:
> Hello!
> Where would I find out what the version of LibUSB that is supplied with
> Cygwin?
http://cygwin.com/packages/
-Jeremy
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Docu
Hello!
Where would I find out what the version of LibUSB that is supplied with Cygwin?
-
Gregg C Levine gregg.drw...@gmail.com
"This signature fought the Time Wars, time and again."
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygw
Version 1.0.5-1 of "libusb-1.0" has been uploaded.
It is a library that allows userspace application to access USB
devices on WinUSB-compatible Windows operation systems (WinXP, Vista, and 7).
It is being integrated and fully API compatible to libusb available at
http://libusb.sourc
At 02:37 2009-07-10 +0200, you wrote:
>At 00:08 2009-07-10 +0100, you wrote:
>>> During Cygwin Setup noticed system crash, while setup screen displayed
>>> something like:
>>> Running preremove script libusb-win32
>>> Attempting to isolate the problem I
At 00:08 2009-07-10 +0100, you wrote:
>> During Cygwin Setup noticed system crash, while setup screen displayed
>> something like:
>> Running preremove script libusb-win32
>> Attempting to isolate the problem I told setup to keep the current version
>> of li
Larry Hall (Cygwin) wrote:
> On 07/09/2009, Arend-Jan Westhoff wrote:
>> 3. Who drove Igor Peshansky away? (So we may lynch him and bring Igor
>> back.)
>
> That would be me but I won't tell you my name or where to find me...
>
> Oh rats! Looks like I'm going to have to go hide with Igor.
> But
On 07/09/2009, Arend-Jan Westhoff wrote:
3. Who drove Igor Peshansky away? (So we may lynch him and bring Igor back.)
That would be me but I won't tell you my name or where to find me...
Oh rats! Looks like I'm going to have to go hide with Igor.
But wait, where's Igor?... Now I'm really scr
Arend-Jan Westhoff wrote:
> During Cygwin Setup noticed system crash, while setup screen displayed
> something like:
> Running preremove script libusb-win32
> Attempting to isolate the problem I told setup to keep the current version
> of libusb-win32 and setup installed
libusb available at
http://libusb.sourceforge.net.
Well, almost:
1) has a #include . While that's certainly necessary
inside of libusb, it's not required for the public interface and
actually messes up some things which #include . Could you please
move that #include into an inter
Version 0.1.12.2-1 of "libusb-win32" has been uploaded.
This is a new upstream release, handles composite device interfaces.
It is a library that allows userspace application to access USB
devices on Windows operation systems (Win98SE, WinME, Win2k, WinXP).
It is derived from and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Apparently the linux version of libusb ships with a libusb.pc pkg-config
file. Packages use it to determine if libusb is installed, but
libusb-win32 package is missing it.
Could something like the attached be added to libusb-win32?
Yaakov
ically install the driver at postinstall of
> > the second package.
>
> That sounds ugly, why can't the user just run foo-config like every
> other package that requires configuration?
Currently, I'm indeed requiring the user to run /usr/sbin/libusb-install
by hand (and
nstall of
> > the second package.
>
> That sounds ugly, why can't the user just run foo-config like every
> other package that requires configuration?
Currently, I'm indeed requiring the user to run /usr/sbin/libusb-install
by hand (and uninstall is automatically
Samuel Thibault wrote:
> Yes of course (I actually call the uninstallation script at preremove).
> But the question is "do we dare installing a driver just because the
> user asked for package installation?".
>
> The problem is that libusb-win32 might be pulled as
On 23 April 2007 02:33, Samuel Thibault wrote:
> Yes of course (I actually call the uninstallation script at preremove).
> But the question is "do we dare installing a driver just because the
> user asked for package installation?".
>
> The problem is that libusb-w
stall script,
> for example.
Yes of course (I actually call the uninstallation script at preremove).
But the question is "do we dare installing a driver just because the
user asked for package installation?".
The problem is that libusb-win32 might be pulled as a dependency of
anot
n't need user input.
>
>> If running your libusb-install is more like a configuration step,
>
> It's not really configuration, it's really installation: the driver is
> copied into C:\WINDOWS\... and a service is registered.
>
>> I might also encourage l
On 23 April 2007 00:16, Morgan Gangwere wrote:
> On 4/22/07, Samuel Thibault wrote:
On 22 April 2007 14:49, Morgan Gangwere wrote:
> On 4/22/07, Brian Dessent wrote:
On 22 April 2007 15:45, Morgan Gangwere wrote:
> On 4/22/07, Samuel Thibault ens-lyon.org> wrote:
:-) Thank you Morgan!
input.
> If running your libusb-install is more like a configuration step,
It's not really configuration, it's really installation: the driver is
copied into C:\WINDOWS\... and a service is registered.
> I might also encourage leaving things as is if the running of the
> script r
Samuel Thibault wrote:
> Hi,
>
> Installing my libusb-win32 package doesn't automatically install the USB
> driver, the user has to run /usr/sbin/libusb-install. I preferred to go
> this way for safety.
>
> However, some user reported that it would be better
Hi,
Installing my libusb-win32 package doesn't automatically install the USB
driver, the user has to run /usr/sbin/libusb-install. I preferred to go
this way for safety.
However, some user reported that it would be better that the
installation is automatically performed (since if one ins
Hi,
Larry Hall (Cygwin), le Sun 22 Apr 2007 11:14:07 -0400, a écrit :
> A good reason for this division is to allow for user input during the
> configuration step, which "setup.exe" doesn't have support for.
It doesn't need user input.
> If running your
Hi,
Morgan Gangwere, le Sun 22 Apr 2007 08:44:55 -0600, a écrit :
> On 4/22/07, Samuel Thibault ens-lyon.org> wrote:
> >Installing my libusb-win32 package doesn't automatically install the USB
> >driver, the user has to run /usr/sbin/libusb-install. I preferred to go
On 4/22/07, Samuel Thibault ens-lyon.org> wrote:
Hi,
Installing my libusb-win32 package doesn't automatically install the USB
driver, the user has to run /usr/sbin/libusb-install. I preferred to go
this way for safety.
However, some user reported that it would be better that the
inst
Maurits Kooiman wrote:
> I used your libusb-win32 (the testlibusb worked).
> mine linker couldnt find the usb functions.
>
> Do you have any idea where to look?
>
> Regards
> Maurits Kooiman
>
> Result of the make-file:
>
> make -k all
> Building
Dear Reader,
I used your libusb-win32 (the testlibusb worked).
mine linker couldnt find the usb functions.
Do you have any idea where to look?
Regards
Maurits Kooiman
Result of the make-file:
make -k all
Building file: ../main.cpp
Invoking: GCC C++ Compiler
g++ -O3 -Wall -c -fmessage
Dear Reader,
I used your libusb-win32 (the testlibusb worked).
mine linker couldnt find the usb functions.
Do you have any idea where to look?
Regards
Maurits Kooiman
Result of the make-file:
make -k all
Building file: ../main.cpp
Invoking: GCC C++ Compiler
g++ -O3 -Wall -c -fmessage
Samuel,
Just confirming that this release solves my problem reported in
http://cygwin.com/ml/cygwin/2007-03/msg00718.html .
Many thanks for fixing this.
Ton van Overbeek
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Doc
Version 0.1.12.1-2 of "libusb-win32" has been uploaded.
It is a library that allows userspace application to access USB
devices on Windows operation systems (Win98SE, WinME, Win2k, WinXP).
It is derived from and fully API compatible to libusb available at
http://libusb.sourceforge.ne
Hi,
Corinna Vinschen, le Mon 26 Mar 2007 10:42:51 +0200, a écrit :
> On Mar 24 20:21, Samuel Thibault wrote:
> > > > Actually, I'm wondering: instead of trying to make libusb0.sys work
> > > > from /usr/lib/libusb/, is it fine (packaging-wise, I mean), in
> &g
On Mar 24 20:21, Samuel Thibault wrote:
> > > Actually, I'm wondering: instead of trying to make libusb0.sys work
> > > from /usr/lib/libusb/, is it fine (packaging-wise, I mean), in
> > > libusb-install, to just copy it into c:\windows\system32\drivers\ and
>
; Yes, I know. But copying usbd.sys to /usr/lib/libusb makes the problem
> go away.
Well, yes, but usbd.sys definitely belongs to windows/system32/drivers.
Remember that this is a windows-shipped file, we shouldn't make a copy
like this.
> > Actually, I'm wondering: instead of tr
On Sat, 24 Mar 2007, Samuel Thibault wrote:
> Hi,
>
> Ton van Overbeek, le Sat 24 Mar 2007 04:06:09 +0100, a écrit :
> > I believe I found the cause of the problem.
> > When running cygcheck on /usr/lib/libusb/libusb0.sys I get this:
> >
> > $ cygcheck /usr/lib/lib
Hi,
Ton van Overbeek, le Sat 24 Mar 2007 04:06:09 +0100, a écrit :
> I believe I found the cause of the problem.
> When running cygcheck on /usr/lib/libusb/libusb0.sys I get this:
>
> $ cygcheck /usr/lib/libusb/libusb0.sys
> c:/Cygwin/lib/libusb/libusb0.sys
> Error: could
I believe I found the cause of the problem.
When running cygcheck on /usr/lib/libusb/libusb0.sys I get this:
$ cygcheck /usr/lib/libusb/libusb0.sys
c:/Cygwin/lib/libusb/libusb0.sys
Error: could not find usbd.sys <
C:\WINDOWS\system32\ntoskrnl.exe
C:\WINDOWS\system32\BOOTVID.
Ton van Overbeek, le Fri 23 Mar 2007 16:56:48 +0100, a écrit :
> Yes, Installed 0.1.10.1-3 after removing 0.1.12.1-1 and it works fine.
Ok, so people can use that one instead for the few coming days until I
fix the issue.
> Also there is now an /usr/lib/libusb/install-filter.exe which d
On Fri, 23 Mar 2007, Samuel Thibault wrote:
> Hi,
>
> Ton van Overbeek, le Fri 23 Mar 2007 15:18:24 +0100, a écrit :
> > I have problems with the libusb-win32-0.1.12.1-1 Cygwin package.
>
> Just to make sure, does the old 0.1.10.1-3 work fine?
>
Yes, Installed 0.1.10.1-3
Hi,
Ton van Overbeek, le Fri 23 Mar 2007 15:18:24 +0100, a écrit :
> I have problems with the libusb-win32-0.1.12.1-1 Cygwin package.
Just to make sure, does the old 0.1.10.1-3 work fine?
> My guess is that /usr/sbin/libusb-install omits some crucial step
> (registry? kernel servic
I have problems with the libusb-win32-0.1.12.1-1 Cygwin package.
Installation went fine. After running /usr/sbin/libusb-install the test
program worked OK and also my own libusb based program worked fine.
The real problem started after the following reboot.
The /usr/sbin/libusb-install installs
Version 0.1.12.0-1 of "libusb-win32" has been uploaded.
It is a library that allows userspace application to access USB
devices on Windows operation systems (Win98SE, WinME, Win2k, WinXP).
It is derived from and fully API compatible to libusb available at
http://libusb.sourceforge.ne
Version 0.1.10.1-3 of "libusb-win32" has been uploaded.
It is a library that allows userspace application to access USB
devices on Windows operation systems (Win98SE, WinME, Win2k, WinXP).
It is derived from and fully API compatible to libusb available at
http://libusb.sourceforge.ne
Hi,
Eric Blake, le Mon 13 Feb 2006 07:18:36 -0700, a écrit :
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Redirected to list: http://cygwin.com/acronyms/#PPIOSPE
>
> According to Mary Cuper on 2/8/2006 10:18 AM:
> >> A quick "cygcheck -p libUSB"
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Redirected to list: http://cygwin.com/acronyms/#PPIOSPE
According to Mary Cuper on 2/8/2006 10:18 AM:
>> A quick "cygcheck -p libUSB" gets no hits, so libUSB has not been
>> officially ported to cygwin yet. Care to contri
Mary Cuper wrote:
How can I use libUSB with Windows/Cygwin like with Linux?
With Linux my code works (it finds the Atmel Microcontroller) but with
Windows/Cygwin it does not find the Microcontroller.
libUSB did not compile with Cygwin, so I installed libUSB-win32, but it does
not function
Eric Blake, le Wed 08 Feb 2006 10:04:39 -0700, a écrit :
> If it wasn't compiled for cygwin, it probably won't work to link it in to
> a cygwin program.
It will. There is a gcc\libusb.a provided in the binary package, which
works fine with cygwin-compiled brltty for instance.
Regards,
Samuel
--
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Mary Cuper on 2/8/2006 9:57 AM:
> How can I use libUSB with Windows/Cygwin like with Linux?
> With Linux my code works (it finds the Atmel Microcontroller) but with
> Windows/Cygwin it does not find the Microcontroller.
>
Mary Cuper, le Wed 08 Feb 2006 17:57:07 +0100, a écrit :
> libUSB did not compile with Cygwin,
Normal.
> so I installed libUSB-win32, but it does not function.
Mmm, works for me. Did you try their test program?
Regards,
Samuel
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-
How can I use libUSB with Windows/Cygwin like with Linux?
With Linux my code works (it finds the Atmel Microcontroller) but with
Windows/Cygwin it does not find the Microcontroller.
libUSB did not compile with Cygwin, so I installed libUSB-win32, but it does
not function.
Please help me.
Thanks
68 matches
Mail list logo
