From: Doug Evans <dje@google.com>
To: gdb-patches@sourceware.org
Subject: Re: [patch] make run
Date: Mon, 30 Sep 2013 22:36:00 -0000 [thread overview]
Message-ID: <21065.64755.63780.888296@ruffy.mtv.corp.google.com> (raw)
In-Reply-To: <yjt2txh2aqq0.fsf@ruffy.mtv.corp.google.com>
Doug Evans writes:
> Hi.
> Since we can't agree on making gdb runnable from its build directory
> (without having to manually specify --data-directory)
> I plan to commit this patch (if there are no objections).
>
> I plan to add an entry for it in the Hints section of the
> wikified internals manual as well.
> https://sourceware.org/gdb/wiki/InternalsManual
And with the requisite .PHONY.
[thanks SamB]
2013-09-30 Doug Evans <dje@google.com>
* Makefile.in (GDBFLAGS): New variable.
(run): New rule.
Index: Makefile.in
===================================================================
RCS file: /cvs/src/src/gdb/Makefile.in,v
retrieving revision 1.1270
diff -u -p -r1.1270 Makefile.in
--- Makefile.in 25 Sep 2013 23:17:11 -0000 1.1270
+++ Makefile.in 30 Sep 2013 22:34:02 -0000
@@ -178,6 +178,9 @@ INTL_CFLAGS = @INCINTL@
# Did the user give us a --with-gdb-datadir option?
GDB_DATADIR = @GDB_DATADIR@
+# Flags to pass to gdb when invoked with "make run".
+GDBFLAGS =
+
# Helper code from gnulib.
GNULIB_BUILDDIR = build-gnulib
LIBGNU = $(GNULIB_BUILDDIR)/import/libgnu.a
@@ -1339,6 +1342,10 @@ data-directory/Makefile: data-directory/
CONFIG_LINKS= \
$(SHELL) config.status
+.PHONY: run
+run: Makefile
+ ./gdb$(EXEEXT) --data-directory=`pwd`/data-directory $(GDBFLAGS)
+
jit-reader.h: $(srcdir)/jit-reader.in
$(SHELL) config.status $@
next prev parent reply other threads:[~2013-09-30 22:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-30 22:29 Doug Evans
2013-09-30 22:36 ` Doug Evans [this message]
2013-10-01 0:39 ` Sergio Durigan Junior
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=21065.64755.63780.888296@ruffy.mtv.corp.google.com \
--to=dje@google.com \
--cc=gdb-patches@sourceware.org \
/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