-Presently, GCC is required to build OpenOCD. The developers have begun
-to enforce strict code warnings (-Wall, -Werror, -Wextra, and more) and
-use C99-specific features: inline functions, named initializers, mixing
-declarations with code, and other tricks. While it may be possible to
-use other compilers, they must be somewhat modern and could require
-extending support to conditionally remove GCC-specific extensions.
-
-Also, you need to install the appropriate driver files, if you want to
-build support for a USB or FTDI-based interface:
-
-- ft2232, jlink, rlink, vsllink, usbprog, arm-jtag-ew:
- - libusb: required for portable communication with USB dongles
-- ft2232 also requires:
- - libftdi: http://www.intra2net.com/opensource/ftdi/ *OR*
- - ftd2xx: http://www.ftdichip.com/Drivers/D2XX.htm,
- or the Amontec version (from http://www.amontec.com), for
- easier support of JTAGkey's vendor and product IDs.
-
-Many Linux distributions provide these packages through their automated
-installation and update mechanisms; however, some Linux versions include
-older versions of libftdi. In particular, using Ubuntu 8.04 has been
-problematic, but newer versions of Ubuntu do not have this problem.
-
-Compiling OpenOCD
------------------
-
-To build OpenOCD (on both Linux and Cygwin), use the following sequence
-of commands:
-
- ./configure [with some options listed in the next section]
- make
- make install
-
-The 'configure' step generates the Makefiles required to build OpenOCD,
-usually with one or more options provided to it. The first 'make' step
-will build OpenOCD and place the final executable in ./src/. The
-final (optional) step, ``make install'', places all of the files in the
-required location.
-
-Cross-Compiling Options
------------------------
-
-To cross-compile, you must specify both --build and --host options to
-the 'configure' script. For example, you can configure OpenOCD to
-cross-compile on a x86 Linux host to run on Windows (MinGW32), you could
-use the following configuration options:
-
- ./configure --build=i686-pc-linux-gnu --host=i586-mingw32msvc ...
-
-Likewise, the following options allow OpenOCD to be cross-compiled for
-an ARM target on the same x86 host:
-
- ./configure --build=i686-pc-linux-gnu --host=arm-elf ...
+GCC or Clang is currently required to build OpenOCD. The developers
+have begun to enforce strict code warnings (-Wall, -Werror, -Wextra,
+and more) and use C99-specific features: inline functions, named
+initializers, mixing declarations with code, and other tricks. While
+it may be possible to use other compilers, they must be somewhat
+modern and could require extending support to conditionally remove
+GCC-specific extensions.