From: Andrew Cagney <cagney@gnu.org>
To: gdb-patches@sources.redhat.com
Subject: [patch/rfc] Build TUI when curses
Date: Tue, 10 Feb 2004 20:10:00 -0000 [thread overview]
Message-ID: <40293ACC.5040506@gnu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 372 bytes --]
Hello,
This patch modifies GDB's build process so that the TUI code is built
when curses is available. Previously --enable-tui was also required.
With this patch:
./gdb -i=tui
will start up the TUI interface. That other post creates a program
called "tui" program that starts the TUI by default.
Comments? I'll look to also commit this round the 16th Feb.
Andrew
[-- Attachment #2: diffs --]
[-- Type: text/plain, Size: 2745 bytes --]
2004-02-10 Andrew Cagney <cagney@redhat.com>
* configure.in: Always check for curses. Enable TUI when curses
is available.
Index: configure.in
===================================================================
RCS file: /cvs/src/src/gdb/configure.in,v
retrieving revision 1.144
diff -u -r1.144 configure.in
--- configure.in 8 Feb 2004 17:53:08 -0000 1.144
+++ configure.in 10 Feb 2004 19:57:34 -0000
@@ -135,6 +135,17 @@
fi
fi
+# FIXME: kettenis/20030102: We seem to prefer HP curses (Hcurses) over
+# Xcurses on HP-UX; see the `-D__HP_CURSES' in the relevant host
+# Makefile fragments. That's why we need to have `Hcurses' before
+# `curses'. I don't see why we should use HP curses if a more
+# standard curses is available, except that according to HP's
+# documentation one needs to compile `-D_XOPEN_SOURCE_EXTENDED' on
+# HP-UX 10.10 and 10.20.
+
+AC_SEARCH_LIBS(initscr, [ncurses Hcurses curses], [],
+ [AC_MSG_ERROR([no curses library found])])
+
# Enable TUI.
AC_ARG_ENABLE(tui,
[ --enable-tui enable full-screen terminal user interface (TUI)],
@@ -143,14 +154,16 @@
;;
*)
AC_MSG_ERROR([bad value $enableval for --enable-tui]) ;;
- esac])
+ esac],enable_tui=yes)
if test x"$enable_tui" = xyes; then
if test -d $srcdir/tui; then
- CONFIG_OBS="$CONFIG_OBS \$(SUBDIR_TUI_OBS)"
- CONFIG_DEPS="$CONFIG_DEPS \$(SUBDIR_TUI_DEPS)"
- CONFIG_SRCS="$CONFIG_SRCS \$(SUBDIR_TUI_SRCS)"
- ENABLE_CFLAGS="$ENABLE_CFLAGS \$(SUBDIR_TUI_CFLAGS)"
- need_curses=yes
+ if test "$ac_cv_search_initscr" != no; then
+ CONFIG_OBS="$CONFIG_OBS \$(SUBDIR_TUI_OBS)"
+ CONFIG_DEPS="$CONFIG_DEPS \$(SUBDIR_TUI_DEPS)"
+ CONFIG_SRCS="$CONFIG_SRCS \$(SUBDIR_TUI_SRCS)"
+ CONFIG_INITS="$CONFIG_INITS \$(SUBDIR_TUI_INITS)"
+ ENABLE_CFLAGS="$ENABLE_CFLAGS \$(SUBDIR_TUI_CFLAGS)"
+ fi
fi
fi
@@ -279,20 +292,7 @@
# Since GDB uses Readline, we need termcap functionality, so we need
# to find a library that provides that. When GDB is configured with
-# --enable-tui, we need full curses functionality.
-#
-# FIXME: kettenis/20030102: We seem to prefer HP curses (Hcurses) over
-# Xcurses on HP-UX; see the `-D__HP_CURSES' in the relevant host
-# Makefile fragments. That's why we need to have `Hcurses' before
-# `curses'. I don't see why we should use HP curses if a more
-# standard curses is available, except that according to HP's
-# documentation one needs to compile `-D_XOPEN_SOURCE_EXTENDED' on
-# HP-UX 10.10 and 10.20.
-
-if test "$need_curses" = yes; then
- AC_SEARCH_LIBS(initscr, [ncurses Hcurses curses], [],
- [AC_MSG_ERROR([no curses library found])])
-fi
+# the TUI, we need full curses functionality.
case $host_os in
cygwin*)
next reply other threads:[~2004-02-10 20:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-10 20:10 Andrew Cagney [this message]
2004-02-11 6:38 ` Eli Zaretskii
2004-02-11 14:52 ` Andrew Cagney
2004-02-16 19:36 ` Andrew Cagney
2004-02-11 15:18 Michael Elizabeth Chastain
2004-02-11 15:43 ` Bob Rossi
2004-02-11 15:55 ` Andrew Cagney
2004-02-11 19:26 ` Eli Zaretskii
2004-02-11 15:58 Michael Elizabeth Chastain
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=40293ACC.5040506@gnu.org \
--to=cagney@gnu.org \
--cc=gdb-patches@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox