X-Git-Url: https://review.openocd.org/gitweb?p=openocd.git;a=blobdiff_plain;f=README;h=d1b983d76aebea4cfbc8391f764f28496cf42c1d;hp=34f1e7b9ca311586e590600f3ca18d895be6f39b;hb=3b4a8af80d9cf3fb370c1177c2cf81f9c0a2e5e9;hpb=fe97fab6a04665c71f1b721b061564de45b98e09 diff --git a/README b/README index 34f1e7b9ca..d1b983d76a 100644 --- a/README +++ b/README @@ -203,11 +203,6 @@ interfaces should be included (among other things). The following list of options was extracted from the output of './configure --help'. Other options may be available there: - --enable-maintainer-mode enable make rules and dependencies not useful - (and sometimes confusing) to the casual installer - NOTE: This option is *required* for GIT builds! - It should *not* be used to build a release. - --enable-dummy Enable building the dummy JTAG port driver --enable-parport Enable building the pc parallel port driver @@ -291,7 +286,7 @@ options may be available there: --disable-internal-jimtcl Disable building internal jimtcl - --enable-libusb0 Use libusb-0.1 library for USB JTAG devices + --enable-remote-bitbang Enable building support for the Remote Bitbang jtag driver @@ -434,7 +429,7 @@ Using the GIT command line client, you might use the following command to set up a local copy of the current repository (make sure there is no directory called "openocd" in the current directory): - git clone git://git.code.sf.net/p/openocd/code + git clone git://git.code.sf.net/p/openocd/code openocd Then you can update that at your convenience using @@ -453,9 +448,9 @@ Tips For Building From a GIT Repository --------------------------------------- Building OpenOCD from a repository requires a recent version of the GNU -autotools (autoconf >= 2.59 and automake >= 1.9). +autotools (autoconf >= 2.60 and automake >= 1.9). 1) Run './bootstrap' to create the 'configure' script and prepare the build process for your host system. -2) Run './configure --enable-maintainer-mode' with other options. +2) Run './configure' with other options.