Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Doug Evans <dje@google.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: tromey@redhat.com, gdb-patches@sourceware.org
Subject: Re: [RFA/python:1/2] Add support for --with-pythondir.
Date: Sun, 30 May 2010 17:10:00 -0000	[thread overview]
Message-ID: <AANLkTine_XZInXMTsR5mPzibXuxbnwh5MDRP8pF7GuZB@mail.gmail.com> (raw)
In-Reply-To: <20100528160818.GN3019@adacore.com>

On Fri, May 28, 2010 at 9:08 AM, Joel Brobecker <brobecker@adacore.com> wrote:
> I wasn't personally thinking about .so modules for GDB. Do you have
> any example in mind where it would be more useful for a user to use
> a .so rather than a .py?

No example.  I just want us to have thought about it (since now seems
like the right time).
And I don't have a strong opinion on any particular solution.
I do think that we should allow for the possibility of having gdb
python modules implemented as .so's.

>> Also, do we want to name this --with-gdb-pythondir? [and do we want to
>> rename --with-python to --with-gdb-python?]
>
> I think that --with-python is a fine name, although now that I think
> of it, it might have been more consistent to name it with-python-prefix.
> I don't think that we should name it with a "gdb" in it, because this
> is not GDB's python library, but rather the prefix where python is
> installed.

For reference sake, --with-python-prefix is a worse name now.
Setting aside --with-python=yes, the preferred parameter is the name
or path of the python binary.  We fetch the needed parameters via
distutils of that binary. [Setting aside cross-compilation.]


  reply	other threads:[~2010-05-29  0:41 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-27  0:09 Add support for the GDB Python Library Joel Brobecker
2010-05-27  0:09 ` [RFA/python:2/2] First script in GDB python library - command/pahole.py Joel Brobecker
2010-05-27 20:37   ` Tom Tromey
2010-05-28  1:34     ` Joel Brobecker
2010-06-03  0:11     ` Joel Brobecker
2010-06-03  6:28       ` Doug Evans
2010-06-03 15:35         ` Joel Brobecker
2010-07-11 18:49           ` Tom Tromey
2010-05-27  0:25 ` [RFA/python:1/2] Add support for --with-pythondir Joel Brobecker
2010-05-27  6:49   ` Doug Evans
2010-05-27 20:32   ` Tom Tromey
2010-05-28  9:55     ` Doug Evans
2010-05-28 17:20       ` Joel Brobecker
2010-05-30 17:10         ` Doug Evans [this message]
2010-06-01 20:15           ` Joel Brobecker
2010-06-01 20:39             ` Doug Evans
2010-06-01 20:53               ` Joel Brobecker
2010-05-27  1:54 ` Add support for the GDB Python Library Doug Evans
2010-05-27  3:42   ` Doug Evans
2010-05-27 15:17   ` Joel Brobecker

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=AANLkTine_XZInXMTsR5mPzibXuxbnwh5MDRP8pF7GuZB@mail.gmail.com \
    --to=dje@google.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tromey@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