Hi all,
On 30 March 2014 08:39, Paul Fertser <[email protected]> wrote:
> Hi,
>
> I'm pleased to announce the first release candidate of the upcoming
> OpenOCD version. The source archives are available from the usual SF
> download locations.
>
> From now on we're entering a feature freeze stage aimed at producing a
> quality release as soon as possible. That means that everyone is
> encouraged to pay specific attention to:
>
> 1. Build issues;
> 2. Regressions;
> 3. Segfaults;
> 4. Other major bugs.
I'm the maintainer of openocd in NixOS. I wonder if there are any
recommended configure flags that should use for building for a distro.
I see many (all?) J-link based dongles are auto-enabled, but many
other options, for potentially interesting features, are not enabled.
Here is the list of flags I wonder whether I should enable:
--enable-jtag_vpi Enable building support for JTAG VPI
--enable-usb_blaster_libftdi
Enable building support for the Altera USB-Blaster
using the libftdi driver, opensource alternate of
FTD2XX
--enable-usb_blaster_ftd2xx
Enable building support for the Altera USB-Blaster
using the FTD2XX driver from ftdichip.com
(What happens if I don't specify any of the "usb_blaster" option? No
support at all?)
--enable-amtjtagaccel Enable building the Amontec JTAG-Accelerator driver
--enable-zy1000-master Use ZY1000 JTAG master registers
--enable-zy1000 Enable ZY1000 interface
--enable-ioutil Enable ioutil functions - useful for standalone
OpenOCD implementations
--enable-ep93xx Enable building support for EP93xx based SBCs
--enable-at91rm9200 Enable building support for AT91RM9200 based SBCs
--enable-bcm2835gpio Enable building support for bitbanging on BCM2835
(as found in Raspberry Pi)
--enable-gw16012 Enable building support for the Gateworks GW16012
JTAG Programmer
--enable-presto_libftdi Enable building support for ASIX Presto Programmer
using the libftdi driver
--enable-presto_ftd2xx Enable building support for ASIX Presto Programmer
using the FTD2XX driver
--enable-openjtag_ftd2xx
Enable building support for the OpenJTAG Programmer
with ftd2xx driver
--enable-openjtag_ftdi Enable building support for the OpenJTAG Programmer
with ftdi driver
--enable-oocd_trace Enable building support for some prototype
OpenOCD+trace ETM capture hardware
--enable-buspirate Enable building support for the Buspirate
--enable-sysfsgpio Enable building support for programming driven via
sysfs gpios.
--enable-minidriver-dummy
Enable the dummy minidriver.
--enable-remote-bitbang Enable building support for the Remote Bitbang jtag
driver
Is there any reason not to enable all? (Except from maybe saving a few
bytes of install size?)
And if enabling all the right thing to do for distros, how about
making a "enable-all" switch so that on the next release we don't
accidentally configure out some cool new feature just because we
forgot to look very closely at ./configure --help?
Btw, thanks for making a new release. IMHO, releases are important for
distros and users :-)
Best regards,
Bjørn Forsman
------------------------------------------------------------------------------
_______________________________________________
OpenOCD-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openocd-devel
