interesting
/
riscv-openocd
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Add comments to README about compiler and library dependencies. 

git-svn-id: svn://svn.berlios.de/openocd/trunk@2441 b42882b7-edfa-0310-969c-e2dbd0fdcd60
This commit is contained in:
zwelch 2009-07-01 19:55:28 +00:00
parent 917f92f052
commit 3731bc5877
1 changed files with 11 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
README
View File

@ -128,7 +128,14 @@ those looking for a quick-install
OpenOCD Dependencies OpenOCD Dependencies
-------------------- --------------------
You will need to install the appropriate driver files, if you want to 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: build support for a USB or FTDI-based interface:
- ft2232, jlink, rlink, vsllink, usbprog, arm-jtag-ew: - ft2232, jlink, rlink, vsllink, usbprog, arm-jtag-ew:
@ -139,6 +146,9 @@ build support for a USB or FTDI-based interface:
or the Amontec version (from @uref{http://www.amontec.com}), for or the Amontec version (from @uref{http://www.amontec.com}), for
easier support of JTAGkey's vendor and product IDs. easier support of JTAGkey's vendor and product IDs.
Many Linux distributions provide these packages through their automated
installation and update mechanisms.
Compiling OpenOCD Compiling OpenOCD
----------------- -----------------