buildroot/package/openocd, branch 2017.05

package/o*/Config.in: fix ordering of statements

2017-05-01T16:57:46+00:00

The check-package script when ran gives warnings on ordering issues on all of these Config files. This patch cleans up all warnings related to the ordering in the Config files for packages starting with the letter o in the package directory. The appropriate ordering is: type, default, depends on, select, help See http://nightly.buildroot.org/#_config_files for more information. Signed-off-by: Adam Duskett Signed-off-by: Thomas Petazzoni

openocd: renumber patch

2017-04-29T13:07:22+00:00

Patch 0001 was removed a while ago, so rename the 0002 patch to 0001. Signed-off-by: Thomas Petazzoni

openocd: bump to 0.10.0

2017-04-29T12:59:00+00:00

Some configure options have been renamed. Support for the deprecated FT2232 devices has been removed in this release, so remove this option. Signed-off-by: Christophe Priouzeau [Thomas: - Add Config.in.legacy handling, suggested by Arnout. - Improve commit log with more details, suggested by Arnout.] Signed-off-by: Thomas Petazzoni

package: remove consecutive empty lines

2017-04-06T20:40:33+00:00

Occurrences were searched using [1]: check-package --include-only ConsecutiveEmptyLines $(find * -type f) and manually removed. [1] http://patchwork.ozlabs.org/patch/729666/ Signed-off-by: Ricardo Martincoski Signed-off-by: Thomas Petazzoni

package/openocd: indentation cleanup

2017-03-19T13:09:18+00:00

Signed-off-by: Jerzy Grzegorek Signed-off-by: Thomas Petazzoni

openocd: avoid documentation rebuild to fix build issues

2017-02-28T08:51:42+00:00

On PowerPC64(le), we patch all configure scripts. Due to this, the version.texi in OpenOCD files gets regenerated, and then since it has a newer date than openocd.info, openocd build system rebuilds the documentation. Unfortunately, this documentation rebuild fails on old machines. We work around this by faking the date of the generated version.texi file, to make the build system believe the documentation doesn't need to be regenerated. Fixes: http://autobuild.buildroot.net/results/3cbe65a46e75b8e67846d593884c96df97dec7a4 Signed-off-by: Thomas Petazzoni Reviewed-by: Sam Bobroff Signed-off-by: Peter Korsgaard

openocd: remove BR2_ARCH_HAS_ATOMICS dependency

2016-01-26T20:33:07+00:00

For some reason, since when openocd was introduced, it was using a BR2_ARCH_HAS_ATOMICS dependency for all sub-options that selected BR2_PACKAGE_LIBFTDI1, even if the libftdi1 package did not have any atomics dependency. Maybe it was confused with the libftdi package, which did have a BR2_ARCH_HAS_ATOMICS dependency ? Regardless, openocd with all four sub-options that currently depend on BR2_ARCH_HAS_ATOMICS builds perfectly fine with a toolchain that does not implement any of the __sync atomic built-ins, so we can remove the BR2_ARCH_HAS_ATOMICS dependency. Signed-off-by: Thomas Petazzoni Acked-by: "Yann E. MORIN" Signed-off-by: Thomas Petazzoni

package/openocd: select libusb when selecting libusb-compat

2016-01-01T18:56:22+00:00

libusb-compat depends on libusb package, so we need to select libusb package at the same time as libusb-compat to avoid an unmet dependency. Since 28f67899e54f15c6e48484ea2976c3e431756bcb, the build stop if a package build is trigged at Makefile level without being selected at Config.in level. This is the case here with BR2_PACKAGE_OPENOCD_USBPROG which select BR2_PACKAGE_LIBUSB_COMPAT without selecting BR2_PACKAGE_LIBUSB. Fixes: http://autobuild.buildroot.net/results/b4a/b4a8c54eed6bf75ab8ade0653953d19792155727/ Signed-off-by: Romain Naour Acked-by: "Yann E. MORIN" Signed-off-by: Peter Korsgaard

openocd: bump to 0.9.0

2015-12-01T16:35:41+00:00

Remove obsolete compilation error patch and update jimtcl related patch. Signed-off-by: Yegor Yefremov Signed-off-by: Thomas Petazzoni

package: update some home page URLs in Config.in.host files

2015-04-18T13:59:34+00:00

Some URLs for package/*/Config.in.host files could use some updating. Signed-off-by: Robert P. J. Day Signed-off-by: Thomas Petazzoni