On Tue, Feb 3, 2015 at 5:55 PM, Paul Fertser <fercer...@gmail.com> wrote:
> I recommend to build with these options (provided libusb-1.0,
> libusb-1.0 and HIDAPI APIs are available via pkg-config in the host
> OS):
>
> --enable-buspirate
> --enable-amtjtagaccel
> --enable-oocd_trace
> --enable-arm-jtag-ew
> --enable-sysfsgpio (on systems using Linux, the kernel)
> --enable-usb_blaster_libftdi
> --enable-openjtag_ftdi
> --enable-presto_libftdi
> --enable-dummy
> --enable-remote-bitbang
> --enable-parport
>
> All the other common adapter drivers will get auto-enabled.
>
Just wanted to further clarify that for automated builds such as distro
packaging scripts etc, it actually makes sense to be explicit about the
adapters that should be enabled, even if they are auto-enabled. The reason
is to cause configure to fail if the prerequisites should be missing for
some reason, instead of silently creating an OpenOCD that lacks the desired
drivers.
For that purpose, perhaps it makes sense to add a --with-libusb1 etc, that
requires successful detection of the libraries, instead of having to
include at least one of the auto-detected adapters for each library. Just a
thought.
/Andreas
------------------------------------------------------------------------------
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________
OpenOCD-devel mailing list
OpenOCD-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openocd-devel
