Tim Wescott wrote:
> I suppose one is just supposed to know
No, certainly not.
In my opinion, what is supposed to happen is that my (libusb
maintainer) constructive and quite detailed review of code by a
student who had not contributed to OpenOCD and seemingly not used
libusb-1.0 before which add
Released, 0.7.0. It works great now.
On Sat, 2013-08-03 at 09:45 +0200, Freddie Chopin wrote:
> Are you building a released version (like 0.7.0) or a downloaded
> repository snapshot? The latter probably won't work - you need to have a
> real git repository to build the most recent version.
>
On 8 August 2013 03:14, Tim Wescott wrote:
> On Sat, 2013-08-03 at 08:12 +0400, Paul Fertser wrote:
>> Hi,
>>
>> On Fri, Aug 02, 2013 at 04:55:24PM -0700, Tim Wescott wrote:
>> > Without libusb-0.1-4 installed I do:
>> >
>> > ./configure --enable-ft2232_libftdi --enable-stlink
>>
>> Please do not
On Sat, 2013-08-03 at 08:12 +0400, Paul Fertser wrote:
> Hi,
>
> On Fri, Aug 02, 2013 at 04:55:24PM -0700, Tim Wescott wrote:
> > Without libusb-0.1-4 installed I do:
> >
> > ./configure --enable-ft2232_libftdi --enable-stlink
>
> Please do not use ft2232_libftdi at all, --enable-ftdi is the cur
Are you building a released version (like 0.7.0) or a downloaded
repository snapshot? The latter probably won't work - you need to have a
real git repository to build the most recent version.
Regards,
FCh
--
Get your SQ
On 2013-08-02 21:12, Paul Fertser wrote:
> Hi,
>
> On Fri, Aug 02, 2013 at 04:55:24PM -0700, Tim Wescott wrote:
>> Without libusb-0.1-4 installed I do:
>>
>> ./configure --enable-ft2232_libftdi --enable-stlink
>
> Please do not use ft2232_libftdi at all, --enable-ftdi is the current
> driver for
Hi,
On Fri, Aug 02, 2013 at 04:55:24PM -0700, Tim Wescott wrote:
> Without libusb-0.1-4 installed I do:
>
> ./configure --enable-ft2232_libftdi --enable-stlink
Please do not use ft2232_libftdi at all, --enable-ftdi is the current
driver for those devices. And you can remove libusb-0.1 altogether
