Menu
▾
▴
libusb-devel
|
From: Xiaofan C. <xia...@gm...> - 2010-03-30 03:32:29
|
I accidentally found out libusb-1.0 Windows Backend is already inside Cygwin packages yesterday during an installation of Cygwin. http://www.cygwin.com/ml/cygwin-announce/2010-03/msg00005.html http://cygwin.com/cgi-bin2/package-grep.cgi?grep=libusb I have not tried it yet. The version is called libusb1.0-1.0.5+git03e9371a. -- Xiaofan http://mcuee.blogspot.com |
|
From: Pete B. <pb...@gm...> - 2010-03-30 14:17:49
|
On 2010.03.30 04:32, Xiaofan Chen wrote: > I accidentally found out libusb-1.0 Windows Backend is already inside > Cygwin packages yesterday during an installation of Cygwin. > > I have not tried it yet. The version is called libusb1.0-1.0.5+git03e9371a. Interesting. I see it too on my end with the latest cygwin, and this is definitely one of the versions with the Windows backend. 03e9371a460031dcb599a1cf504539667cf12f1c is r153 (2010.02.06), so they are quite a few versions behind, but I guess they'll just update their package when we have the official release. And while I had no hand in this, I'm quite glad to see that libusb 1.0 adoption is being promoted in cygwin too. The more people use libusb 1.0, the better! Regards, /Pete |
|
From: Xiaofan C. <xia...@gm...> - 2010-06-12 02:01:22
|
On Tue, Mar 30, 2010 at 10:17 PM, Pete Batard <pb...@gm...> wrote: > Interesting. > > I see it too on my end with the latest cygwin, and this is definitely > one of the versions with the Windows backend. > 03e9371a460031dcb599a1cf504539667cf12f1c is r153 (2010.02.06), so they > are quite a few versions behind, but I guess they'll just update their > package when we have the official release. > > And while I had no hand in this, I'm quite glad to see that libusb 1.0 > adoption is being promoted in cygwin too. The more people use libusb > 1.0, the better! > FYI, they updated it to gitbd62c472-1 version which is dated 24-Apr-2010 (between r269 and r270). This is much more closer to the current tree. http://cygwin.com/cgi-bin2/package-grep.cgi?grep=libusb http://mirrors.xmission.com/cygwin/release/libusb1.0/ -- Xiaofan http://mcuee.blogspot.com |
|
From: Samuel T. <sam...@en...> - 2010-06-12 02:32:41
|
Hello, Xiaofan Chen, le Sat 12 Jun 2010 10:01:14 +0800, a écrit : > On Tue, Mar 30, 2010 at 10:17 PM, Pete Batard <pb...@gm...> wrote: > > And while I had no hand in this, I'm quite glad to see that libusb 1.0 > > adoption is being promoted in cygwin too. The more people use libusb > > 1.0, the better! > > FYI, they updated it to gitbd62c472-1 version which is dated 24-Apr-2010 > (between r269 and r270). This is much more closer to the current tree. > http://cygwin.com/cgi-bin2/package-grep.cgi?grep=libusb > http://mirrors.xmission.com/cygwin/release/libusb1.0/ Cf README: I packaged it for brltty :) Samuel |
|
From: Xiaofan C. <xia...@gm...> - 2010-06-12 02:48:25
|
On Sat, Jun 12, 2010 at 10:11 AM, Samuel Thibault <sam...@en...> wrote: >> FYI, they updated it to gitbd62c472-1 version which is dated 24-Apr-2010 >> (between r269 and r270). This is much more closer to the current tree. >> http://cygwin.com/cgi-bin2/package-grep.cgi?grep=libusb >> http://mirrors.xmission.com/cygwin/release/libusb1.0/ > > Cf README: I packaged it for brltty :) > I see. So you are the Cygwin packager for both libusb-1.0 and libusb-win32. Glad to know this. Maybe you want to update both libusb-1.0 and libusb-win32 to more recent version. Thanks. -- Xiaofan http://mcuee.blogspot.com |
|
From: chemelli <che...@te...> - 2010-10-02 12:07:18
|
Hi all, is there a way I can update on my own cygwin to latest libusb or even better, can you please update packages to current trunk as I see that from August a lot of new things are in. Thank you in advance, Simone -- View this message in context: http://libusb.6.n5.nabble.com/libusb-1-0-windows-backend-now-in-Cygwin-packages-tp3162p3073778.html Sent from the LibUSB Dev mailing list archive at Nabble.com. |
|
From: Xiaofan C. <xia...@gm...> - 2010-10-02 12:56:56
|
On Sat, Oct 2, 2010 at 8:07 PM, chemelli <che...@te...> wrote: > is there a way I can update on my own cygwin to latest libusb or even > better, can you please update packages to current trunk as I see that from > August a lot of new things are in. It is really not difficult for you to build libusb-pbatard under Cygwin. Get the git tree. Then run autogen.sh if you need the debug-log option. If you do not want to use the default configure options in the autogen.sh file. you can change it. For example, you can use "./configure --prefix=/usr --enable-examples-build". -- Xiaofan |
|
From: chemelli <che...@te...> - 2010-10-02 15:29:05
|
autogen.sh will all take care of installing static lib ? Simone -- View this message in context: http://libusb.6.n5.nabble.com/libusb-1-0-windows-backend-now-in-Cygwin-packages-tp3162p3073940.html Sent from the LibUSB Dev mailing list archive at Nabble.com. |
|
From: Pete B. <pb...@gm...> - 2010-10-02 17:06:54
|
On 2010.10.02 16:28, chemelli wrote: > autogen.sh will all take care of installing static lib ? The autogen.sh script itself doesn't install the libraries, but it helps creating a Makefile that has a "make install" feature, by calling configure. If you run "make install" after libusb has been compiled, it should follow the default procedure for the installation of libraries on UNIX-like systems and copy the static and dynamic library to /usr/local/lib, which is the default destination. Note that it is up to you to change the --prefix option if the default from "make install" doesn't suit your system's needs. Eg. if you want the libraries to be copied in /usr/lib rather than /usr/local/lib, you would use --prefix=/usr. The reason we are not setting up different defaults for each platform is that package maintainers on UNIX-ike systems would always use --prefix. Also note that you don't have to re-run configure if you simply want to add extra parameters from the ones already provided in autogen. For instance, if the only thing you need is change the installation prefix, you can use "./autogen.sh --prefix=/usr" and "--prefix=/usr" will be added to the configure line. You might also be able to disable some of the default configure options by feeding them to autogen as well (eg. even though --enable-debug-log is enabled by default, if you run "./autogen.sh --disable-debug-log", forced debug logging should be turned off). Regards, /Pete |
|
From: chemelli <che...@te...> - 2010-10-03 12:06:16
|
Thx a lot Pete for your complete explanation. I was able to both compile and install the lib :) In the code of the app I was trying to compile I had to do a small change: LIBUSB_API -> LIBUSB_CALL And now it compiles. I still get from time to time "libusb_handle_events returned with -1" and "usb bulk write failed : ret = -1". So I'm wondering if libusb is considered stable under Cygwin or there are some known issues... Thanks. -- View this message in context: http://libusb.6.n5.nabble.com/libusb-1-0-windows-backend-now-in-Cygwin-packages-tp3162p3074503.html Sent from the LibUSB Dev mailing list archive at Nabble.com. |
|
From: Xiaofan C. <xia...@gm...> - 2010-10-03 23:41:44
|
On Sun, Oct 3, 2010 at 8:06 PM, chemelli <che...@te...> wrote: > I still get from time to time "libusb_handle_events returned with -1" and > "usb bulk write failed : ret = -1". So I'm wondering if libusb is considered > stable under Cygwin or there are some known issues... > To solve the problem, you may have to post the program to demonstrate the problem. -- Xiaofan |
|
From: Pete B. <pb...@gm...> - 2010-10-04 16:30:33
|
On 2010.10.03 13:06, chemelli wrote: > In the code of the app I was trying to compile I had to do a small change: > > LIBUSB_API -> LIBUSB_CALL Yes, we recently changed the name of that macro. The last cygwin package would have used the old one. > I still get from time to time "libusb_handle_events returned with -1" and > "usb bulk write failed : ret = -1". So I'm wondering if libusb is considered > stable under Cygwin or there are some known issues... The libusb backend is still fairly new, so it is better considered as experimental at this stage. Of course, we're trying to iron out any potential bug, so if you can tell us more about the conditions under which those error appear, that would help. Telling us more about the device you are communicating with, your application, and especially providing a debug log would be especially useful. If you used autogen to recompile libusb, debug logging should already be enabled, through the --enable-debug-log option, but of course, if your application is GUI only, you will have to redirect the console to see that debug output. Or, as Xiaofan pointed out, providing some form of access to either the application (provided we can find a USB device that works with it) or its source would also help. Regards, /Pete |
|
From: Peter S. <pe...@st...> - 2010-10-04 19:30:34
|
chemelli wrote: > I still get from time to time "libusb_handle_events returned with -1" > and "usb bulk write failed : ret = -1". So I'm wondering if libusb > is considered stable under Cygwin or there are some known issues... No known issues, not too many have been using it in Cygwin. It would really help if you could send a debug log, and please note which library you are using. (Self-bult, which commit, or the cygwin package?) //Peter |
|
From: Simone c. <che...@te...> - 2010-10-05 08:12:10
|
I'm now testing the same on a VirtualBox with Ubuntu 10.04...once everything works there, I'll come back to the Cygwin thing ;) Thank you. Simone -----Original Message----- From: Peter Stuge [mailto:pe...@st...] Sent: lunedì 4 ottobre 2010 21:30 To: lib...@li... Subject: Re: [Libusb-devel] libusb-1.0 windows backend now in Cygwin packages chemelli wrote: > I still get from time to time "libusb_handle_events returned with -1" > and "usb bulk write failed : ret = -1". So I'm wondering if libusb is > considered stable under Cygwin or there are some known issues... No known issues, not too many have been using it in Cygwin. It would really help if you could send a debug log, and please note which library you are using. (Self-bult, which commit, or the cygwin package?) //Peter ---------------------------------------------------------------------------- -- Virtualization is moving to the mainstream and overtaking non-virtualized environment for deploying applications. Does it make network security easier or more difficult to achieve? Read this whitepaper to separate the two and get a better understanding. http://p.sf.net/sfu/hp-phase2-d2d _______________________________________________ Libusb-devel mailing list Lib...@li... https://lists.sourceforge.net/lists/listinfo/libusb-devel |
|
From: chemelli <che...@te...> - 2010-10-02 11:14:46
|
Hi all, is there a way I can update on my own cygwin to latest libusb or even better, can you please update packages to current trunk as I see that from August a lot of new things are in. Thank you in advance, Simone -- View this message in context: http://libusb.6.n5.nabble.com/libusb-1-0-windows-backend-now-in-Cygwin-packages-tp3162p3073734.html Sent from the LibUSB Dev mailing list archive at Nabble.com. |
|
From: Peter S. <pe...@st...> - 2010-10-04 19:29:02
|
chemelli wrote: > is there a way I can update on my own cygwin to latest libusb I suggest removing the installed cygwin package and then choosing if you want to use libusb.git or libusb-pbatard.git, and then build and install that manually into your cygwin environment: git clone git://git.libusb.org/libusb.git cd libusb ./autogen.sh --disable-debug-log && make install (Replace libusb with libusb-pbatard if you would like to test the code in Pete's repo, which has many more changes.) > or even better, can you please update packages to current trunk as > I see that from August a lot of new things are in. In libusb-pbatard.git, yes. In libusb.git, maybe, maybe not. I think it would be good if the cygwin package was based on libusb.git, and now that there is some Windows support it is actually possible. But note that Pete has many changes which are not included in libusb.git. However - what to package is of course completely up to the packager! :) I'd recommend staying close to libusb.git, but on the other hand it's interesting to get more testing for code in libusb-pbatard.git. //Peter |
|
From: Samuel T. <sam...@en...> - 2010-10-04 19:38:42
|
Peter Stuge, le Mon 04 Oct 2010 21:28:54 +0200, a écrit : > However - what to package is of course completely up to the packager! > :) I'd recommend staying close to libusb.git, but on the other hand > it's interesting to get more testing for code in libusb-pbatard.git. I could actually package both: the cygwin installer permits to provide "experimental" versions. BTW, if somebody feels he has both time and cygwin competence, feel free to ask me for adopting the libusb packages, I don't have as much time to spend on it as one could like. Samuel |
|
From: Simone c. <che...@te...> - 2010-10-11 11:16:50
|
Hi Samuel, are you going to package libusb-pbatard.git as "experimental" ? I want to be 100% sure it's not something wrong I do that leads to my issues (for example make install will not replace cybusb-1.0.dll). Thank you. Simone -----Original Message----- From: Samuel Thibault [mailto:sam...@en...] Sent: lunedì 4 ottobre 2010 21:39 To: lib...@li... Subject: Re: [Libusb-devel] libusb-1.0 windows backend now in Cygwin packages Peter Stuge, le Mon 04 Oct 2010 21:28:54 +0200, a écrit : > However - what to package is of course completely up to the packager! > :) I'd recommend staying close to libusb.git, but on the other hand > it's interesting to get more testing for code in libusb-pbatard.git. I could actually package both: the cygwin installer permits to provide "experimental" versions. BTW, if somebody feels he has both time and cygwin competence, feel free to ask me for adopting the libusb packages, I don't have as much time to spend on it as one could like. Samuel ---------------------------------------------------------------------------- -- Virtualization is moving to the mainstream and overtaking non-virtualized environment for deploying applications. Does it make network security easier or more difficult to achieve? Read this whitepaper to separate the two and get a better understanding. http://p.sf.net/sfu/hp-phase2-d2d _______________________________________________ Libusb-devel mailing list Lib...@li... https://lists.sourceforge.net/lists/listinfo/libusb-devel |
|
From: Xiaofan C. <xia...@gm...> - 2010-10-12 01:40:00
|
On Mon, Oct 11, 2010 at 7:16 PM, Simone chemelli <che...@te...> wrote: > Hi Samuel, > > are you going to package libusb-pbatard.git as "experimental" ? I want to be > 100% sure it's not something wrong I do that leads to my issues (for example > make install will not replace cybusb-1.0.dll). > If you are using libusb-pbatard, then you can post the full log (from "autogen.sh", "make" and "make install"). -- Xiaofan |
|
From: Simone c. <che...@te...> - 2010-10-13 10:27:59
|
Here you are. Simone MediaPortal Developer http://www.team-mediaportal.com -----Original Message----- From: Xiaofan Chen [mailto:xia...@gm...] Sent: martedì 12 ottobre 2010 03:40 To: Simone chemelli Cc: Samuel Thibault; lib...@li... Subject: Re: [Libusb-devel] libusb-1.0 windows backend now in Cygwin packages On Mon, Oct 11, 2010 at 7:16 PM, Simone chemelli <che...@te...> wrote: > Hi Samuel, > > are you going to package libusb-pbatard.git as "experimental" ? I want > to be 100% sure it's not something wrong I do that leads to my issues > (for example make install will not replace cybusb-1.0.dll). > If you are using libusb-pbatard, then you can post the full log (from "autogen.sh", "make" and "make install"). -- Xiaofan |
|
From: Xiaofan C. <xia...@gm...> - 2010-10-13 10:45:01
|
On Wed, Oct 13, 2010 at 6:27 PM, Simone chemelli <che...@te...> wrote: > Here you are. > > Simone > MediaPortal Developer > http://www.team-mediaportal.com I see nothing wrong in the log. What do you mean by "make install will not replace cybusb-1.0.dll"? libtool: install: dlpath=`/bin/sh 2>&1 -c '. .libs/'libusb-1.0.la'i; echo cygusb-1.0.dll'` libtool: install: dldir=/usr/local/lib/`dirname ../bin/cygusb-1.0.dll` libtool: install: test -d /usr/local/lib/../bin || mkdir -p /usr/local/lib/../bin libtool: install: /usr/bin/install -c .libs/cygusb-1.0.dll /usr/local/lib/../bin/cygusb-1.0.dll libtool: install: chmod a+x /usr/local/lib/../bin/cygusb-1.0.dll libtool: install: if test -n '' && test -n 'strip --strip-unneeded'; then eval 'strip --strip-unneeded /usr/local/lib/../bin/cygusb-1.0.dll' || exit 0; fi -- Xiaofan |
|
From: Xiaofan C. <xia...@gm...> - 2010-10-13 10:50:10
|
On Wed, Oct 13, 2010 at 6:44 PM, Xiaofan Chen <xia...@gm...> wrote: > On Wed, Oct 13, 2010 at 6:27 PM, Simone chemelli > <che...@te...> wrote: >> Here you are. >> > I see nothing wrong in the log. What do you mean by > "make install will not replace cybusb-1.0.dll"? > > libtool: install: dlpath=`/bin/sh 2>&1 -c '. .libs/'libusb-1.0.la'i; > echo cygusb-1.0.dll'` > libtool: install: dldir=/usr/local/lib/`dirname ../bin/cygusb-1.0.dll` > libtool: install: test -d /usr/local/lib/../bin || mkdir -p > /usr/local/lib/../bin > libtool: install: /usr/bin/install -c .libs/cygusb-1.0.dll > /usr/local/lib/../bin/cygusb-1.0.dll > libtool: install: chmod a+x /usr/local/lib/../bin/cygusb-1.0.dll > libtool: install: if test -n '' && test -n 'strip --strip-unneeded'; then eval > 'strip --strip-unneeded /usr/local/lib/../bin/cygusb-1.0.dll' || exit 0; fi > I just tried it myself and "make install" works fine to replace the cygusb-1.0.dll. -- Xiaofan |
|
From: Xiaofan C. <xia...@gm...> - 2010-10-13 13:09:17
|
On Wed, Oct 13, 2010 at 7:48 PM, Simone chemelli <che...@te...> wrote: > Please check the screenshots attached to previous message. > You are install it to /usr/local/bin and yet your screenshot shows /usr/bin (/bin for Cygwin). > libtool: install: dlpath=`/bin/sh 2>&1 -c '. .libs/'libusb-1.0.la'i; > echo cygusb-1.0.dll'` > libtool: install: dldir=/usr/local/lib/`dirname ../bin/cygusb-1.0.dll` > libtool: install: test -d /usr/local/lib/../bin || mkdir -p > /usr/local/lib/../bin > libtool: install: /usr/bin/install -c .libs/cygusb-1.0.dll > /usr/local/lib/../bin/cygusb-1.0.dll > libtool: install: chmod a+x /usr/local/lib/../bin/cygusb-1.0.dll > libtool: install: if test -n '' && test -n 'strip --strip-unneeded'; then eval > 'strip --strip-unneeded /usr/local/lib/../bin/cygusb-1.0.dll' || exit 0; fi > So you should check if /usr/local/bin has the latest cygusb-1.0.dll. If you want to overwrite the existing Cygwin libusb-1.0 package, then you should use "./autogen.sh --prefix=/usr". -- Xiaofan |
|
From: Peter S. <pe...@st...> - 2010-10-13 22:13:56
|
Xiaofan Chen wrote: > You are install it to /usr/local/bin and yet your screenshot > shows /usr/bin (/bin for Cygwin). .. > If you want to overwrite the existing Cygwin libusb-1.0 > package, then you should use "./autogen.sh --prefix=/usr". I would recommend instead uninstalling the Cygwin package and not changing the prefix, so that the binaries go into /usr/local/bin and are kept separate from Cygwin packaged binaries. //Peter |
|
From: Xiaofan C. <xia...@gm...> - 2010-10-13 23:35:30
|
On Thu, Oct 14, 2010 at 6:13 AM, Peter Stuge <pe...@st...> wrote: > Xiaofan Chen wrote: >> You are install it to /usr/local/bin and yet your screenshot >> shows /usr/bin (/bin for Cygwin). > .. >> If you want to overwrite the existing Cygwin libusb-1.0 >> package, then you should use "./autogen.sh --prefix=/usr". > > I would recommend instead uninstalling the Cygwin package and not > changing the prefix, so that the binaries go into /usr/local/bin and > are kept separate from Cygwin packaged binaries. I agree this is a better suggestion. -- Xiaofan |
