Steve Franks wrote:
>> I wonder how many other bumps we will find :-(
>>
>> --- Duane.
steve> I just want to "port" OOCD into the 'standard' freebsd port build
system.
steve> I want no special toys, ftd2xx or whatever.
steve> I'd like minimal support for all dongles .... [urjtag porter did
Please - look at the *NEW* version of the user manual.
I just added some things to Section 2 (not on line yet)
===========
To be useful: You must have LIBFTDI support, which uses "libusb"
-without it I would not even bother.
LIBFTDI builds some number of test apps - try them - they need to work
some how.
Again - I can't say it enough. Without "libftdi + libusb" - do not even
start.
http://www.freshports.org/devel/libusb/
and:
http://www.freshports.org/devel/libftdi
Seems to exist.. and should work..
The Issue #1 i see is this:
http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/129636
Get clarity on which version of "libftdi" - current version is 0.14.
Solve that problem first. DO NOT go backwards from 0.14.
=======================
>> If I should be just mangling the CFLAGS,
You mention: "CFLAGS"
Why? Does GCC not by default look in: '/usr/local/include' by default?
And does "LD" not look in /usr/local/lib ...
If so - then it is a non-issue.
Then plain:
./configure --enable-<a-fewthings-see-below>
The key to this is to look at the contents of "config.log" - when it fails.
It is a treasure trove of useful information. Start from the end and of
the file and work backwards.
==========================
I would suggest these options:
./configure \
--enable-dummy \
PRINTER PORTS
--enable-parport --enable-parport-giveio \
--enable-gw16012 --enable-parport-giveio --enable-amtjtagaccel
LIBFTDI + LIBUSB - give these:
--enable-ft2232_libftdi --enable-presto_libftdi
LIBUSB - add these:
--enable-jlink --enable-usbprog --enable-rlink --enable-vsllink
--enable-usbprog
==========================
*END*
==========================
-Duane.
_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development
