zcy
/
tinyriscv-openocd
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

David Brownell <david-b@pacbell.net>: 

More minor improvements to README to help polish the 0.2.0 release:
- Add note about Ubuntu 8.04 (in lieu of starting a README.Linux file).
- Fix introductory paragraph to Bulding OpenOCD
- Remove some vestigial texinfo markup.


git-svn-id: svn://svn.berlios.de/openocd/trunk@2448 b42882b7-edfa-0310-969c-e2dbd0fdcd60
__archive__
zwelch 2009-07-02 04:55:46 +00:00
parent 6d08c1800c
commit 14fb875e8f
1 changed files with 10 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
README
View File

@ -117,13 +117,11 @@ Building OpenOCD
The INSTALL file contains generic instructions for running 'configure' The INSTALL file contains generic instructions for running 'configure'
and compiling the OpenOCD source code. That file is provided by default and compiling the OpenOCD source code. That file is provided by default
for all GNU automake packages, and for all GNU automake packages. If you are not familiar with the GNU
autotools, then you should read those instructions first.
if you are not familiar with the GNU autotools, then you should read The remainder of this document tries to provide some instructions for
those instructions first. those looking for a quick-install.
Still, the
remainder of this document tries to provide complete instructions for
those looking for a quick-install
OpenOCD Dependencies OpenOCD Dependencies
-------------------- --------------------
@ -143,11 +141,13 @@ build support for a USB or FTDI-based interface:
- ft2232 also requires: - ft2232 also requires:
- libftdi: http://www.intra2net.com/opensource/ftdi/ *OR* - libftdi: http://www.intra2net.com/opensource/ftdi/ *OR*
- ftd2xx: http://www.ftdichip.com/Drivers/D2XX.htm, - ftd2xx: http://www.ftdichip.com/Drivers/D2XX.htm,
or the Amontec version (from @uref{http://www.amontec.com}), for or the Amontec version (from 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 Many Linux distributions provide these packages through their automated
installation and update mechanisms. 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 Compiling OpenOCD
----------------- -----------------
@ -377,7 +377,7 @@ called "openocd" in the current directory):
svn checkout svn://svn.berlios.de/openocd/trunk openocd svn checkout svn://svn.berlios.de/openocd/trunk openocd
If you prefer GIT based tools, the @command{git-svn} package works too: If you prefer GIT based tools, the git-svn package works too:
git svn clone -s svn://svn.berlios.de/openocd git svn clone -s svn://svn.berlios.de/openocd
@ -386,7 +386,7 @@ Tips For Building From The Subversion Repository
Building OpenOCD from a repository requires a recent version of the GNU Building OpenOCD from a repository requires a recent version of the GNU
autotools (autoconf >= 2.59 and automake >= 1.9). For building on autotools (autoconf >= 2.59 and automake >= 1.9). For building on
Windows, you have to use Cygwin. Make sure that your @env{PATH} Windows, you have to use Cygwin. Make sure that your PATH
environment variable contains no other locations with Unix utils (like environment variable contains no other locations with Unix utils (like
UnxUtils) - these can't handle the Cygwin paths, resulting in obscure UnxUtils) - these can't handle the Cygwin paths, resulting in obscure
dependency errors. This was an observation gathered from the logs of dependency errors. This was an observation gathered from the logs of