aboutsummaryrefslogtreecommitdiff
path: root/gdb/README
diff options
context:
space:
mode:
authorFernando Nasser <fnasser@redhat.com>2000-12-22 15:03:10 +0000
committerFernando Nasser <fnasser@redhat.com>2000-12-22 15:03:10 +0000
commitbec71058e4d7f5bfa8ff09dcf7060aa87ac2b115 (patch)
tree5eea216c2aee28f4caf3601e1145c24c1be99a93 /gdb/README
parent315f8b0e915af8849346008a8cda74d79301ad22 (diff)
downloadgdb-bec71058e4d7f5bfa8ff09dcf7060aa87ac2b115.zip
gdb-bec71058e4d7f5bfa8ff09dcf7060aa87ac2b115.tar.gz
gdb-bec71058e4d7f5bfa8ff09dcf7060aa87ac2b115.tar.bz2
2000-12-22 Fernando Nasser <fnasser@redhat.com>
* README: Suggest building in an empty directory.
Diffstat (limited to 'gdb/README')
-rw-r--r--gdb/README15
1 files changed, 14 insertions, 1 deletions
diff --git a/gdb/README b/gdb/README
index cd8c6c2..c718b6f 100644
--- a/gdb/README
+++ b/gdb/README
@@ -35,13 +35,26 @@ called `gdb-5.0', which contains:
config-ml.in gdb missing mpw-install
config.guess include mkinstalldirs opcodes
-To build GDB, you can just do:
+You can build GDB right in the source directory:
cd gdb-5.0
./configure
make
cp gdb/gdb /usr/local/bin/gdb (or wherever you want)
+However, we recommend that an empty directory be used instead.
+This way you do not clutter your source tree with binary files
+and will be able to create different builds with different
+configuration options.
+
+You can build GDB in any empty build directory:
+
+
+ mkdir build
+ cd build
+ <full path to your sources>/gdb-5.0/configure
+ make
+
(Building GDB with DJGPP tools for MS-DOS/MS-Windows is slightly
different; see the file gdb-5.0/gdb/config/djgpp/README for details.)