[Libusbx-devel] Compiling on a fresh installation on Mac OS X

Hi, I was a bit surprised that the default installation obtained by cloning (using git clone on the command line) git://github.com/libusbx/libusbx.gitdid not include a configure or any of the artifacts generated by the autoconf suite. Using a fresh cloned directory and having MacPort's autoconf a

Re: [Libusbx-devel] Compiling on a fresh installation on Mac OS X

Yves Arrouye wrote: > I was a bit surprised that the default installation obtained by cloning > (using git clone on the command line) > git://github.com/libusbx/libusbx.gitdid not include a configure configure & co are generated and included in release tarballs. Since they are generated files they

Re: [Libusbx-devel] Compiling on a fresh installation on Mac OS X

Hi Yves, On 2012.07.23 10:42, Yves Arrouye wrote: > I was a bit surprised that the default installation obtained by cloning > (using git clone on the command > line) git://github.com/libusbx/libusbx.git > did not include a configure or > any of the artifacts

Re: [Libusbx-devel] Compiling on a fresh installation on Mac OS X

On 2012.07.23 11:30, Peter Stuge wrote: > I speak for the libusb project with my 8 years of experience > there, not for the libusbx fork of a few months which is ran by Pete. How convenient of you to ignore the many years of experience myself (and the other admins) also have with libusb, as well

Re: [Libusbx-devel] Compiling on a fresh installation on Mac OS X

Pete Batard wrote: > you're going to earn yourself a ban. That's confusing, but I guess you'll do as you like. > > but working > > with git does require more of you. I think that's a good thing > > Please keep this bullshit about how git is going to save the world I didn't write as verbosely a

Re: [Libusbx-devel] Compiling on a fresh installation on Mac OS X

> > libusb has always had the autogen.sh script which generates (and runs) > configure in a git tree. It works also with Mac OS X Xcode tools. > Okay. I personally do not build in the source tree (that tree is shared between my Mac environment and a Linux VM; I have also taken this habit as it

Re: [Libusbx-devel] Compiling on a fresh installation on Mac OS X

On 2012.07.23 12:09, Peter Stuge wrote: > That's confusing It shouldn't be. There aren't many ways to interpret your intent behind your "with my 8 years of experience there, not for the libusbx fork of a few months which is ran by Pete", and they all point to trolling. It has been explained to

Re: [Libusbx-devel] Compiling on a fresh installation on Mac OS X

On 2012.07.23 12:23, Yves Arrouye wrote: > Maybe a options autogen.sh could make it stop short of running configure? As Peter isn't aware, because he isn't involved that closely in libusbx, we do have a bootstrap.sh that does the same as autogen.sh but doesn't run configure. I did mention both i

Re: [Libusbx-devel] Compiling on a fresh installation on Mac OS X

Yes I read autogen.sh since I posted and saw what to does. Sure, an INSTALL.git or even a README.git would be perfect (and a good place to mention bootstrap vs autogen). On Mon, Jul 23, 2012 at 1:39 PM, Pete Batard wrote: > On 2012.07.23 12:23, Yves Arrouye wrote: > > Maybe a options autogen.sh

Re: [Libusbx-devel] libusb segfaults - causes pcscd to crash

> On 2012.07.21 20:29, Ludovic Rousseau wrote: > Can you try to make pcscd generate a core file? Does this imply that the usbmon output is not useful and can be disabled? > You may have to play with "ulimit -c unlimited" to allow the creation > of a core file. After doing some research about uli

Re: [Libusbx-devel] Compiling on a fresh installation on Mac OS X

On 2012.07.23 12:49, Yves Arrouye wrote: > Sure, an INSTALL.git or even a README.git would be perfect (and a good > place to mention bootstrap vs autogen). I think README.git is probably better as well. Will try to add one soon. Regards, /Pete ---

Re: [Libusbx-devel] libusb segfaults - causes pcscd to crash

> On 2012.07.23 13:51, sebastiank wrote: >> On 2012.07.21 20:29, Ludovic Rousseau wrote: >> You may have to play with "ulimit -c unlimited" to allow the creation >> of a core file. > After doing some research about ulimit, I’m afraid to say that I can’t > enable the generation of core dumps. Well

Re: [Libusbx-devel] Compiling on a fresh installation on Mac OS X

Pete Batard wrote: > Where did the issue become trying to convince Yves that using git > (or another VCS for that matter) was better for him? I don't know how you came up with the idea that I tried to do that. Fortunately it didn't seem like Yves interpreted what I wrote like you did. Communicat

[Libusbx-devel] Async API question:

Hi there, Here's the code and output of my test. I'm trying to understand what's going wrong! I mean that I'm expecting the callback function "cb_xfr" from my bulk transfer to be called after libusb_submit_transfer is called. I'm communicating to a FPGA through a Cypress USB (FX2) and It's work

Re: [Libusbx-devel] Async API question:

Kevyn-Alexandre Paré wrote: > Here's the code and output of my test. I'm trying to understand > what's going wrong! I mean that I'm expecting the callback function > "cb_xfr" from my bulk transfer to be called after > libusb_submit_transfer is called. I'm communicating to a FPGA > through a Cypress

[Libusbx-devel] liamstask opened issue 37 on libusbx/libusbx

[liamstask][1] opened [issue 37][2] on [libusbx/libusbx][3] July 23, 2012 > v0.1.11, winusb backend: aborts do not succeed for open transfers on a device that gets disconnected [1]: https://github.com/liamstask [2]: https://github.com/libusbx/libusbx/issues/37 (v0.1.11, winusb backend: abo

[Libusbx-devel] liamstask commented on issue 37 on libusbx/libusbx

[liamstask][1] commented on [issue 37][2] on [libusbx/libusbx][3] July 24, 2012 > Ah, I see ERROR_FILE_NOT_FOUND does not get handled in windows_transfer_callback() in windows_usb.c. Seems like cleaning up and setting the transfer status to LIBUSB_TRANSFER_NO_DEVICE would be ideal, as well as hand