From: Joel Brobecker <brobecker@adacore.com>
To: Doug Evans <dje@google.com>
Cc: tromey@redhat.com, gdb-patches@sourceware.org
Subject: Re: [RFA/python:1/2] Add support for --with-pythondir.
Date: Tue, 01 Jun 2010 20:15:00 -0000 [thread overview]
Message-ID: <20100601201537.GQ3019@adacore.com> (raw)
In-Reply-To: <AANLkTine_XZInXMTsR5mPzibXuxbnwh5MDRP8pF7GuZB@mail.gmail.com>
> I do think that we should allow for the possibility of having gdb
> python modules implemented as .so's.
Sure. The easiest seems to add support for that on top of what's
currently been proposed when the need arises. AFAICT, It looks like
all we have to do to make it work is add the lib-dynload directory
to the sys.path.
> 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.]
Hmmm, yes, that's right.
Let us know if you still have some concerns...
--
Joel
next prev parent reply other threads:[~2010-06-01 20:15 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
2010-06-01 20:15 ` Joel Brobecker [this message]
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=20100601201537.GQ3019@adacore.com \
--to=brobecker@adacore.com \
--cc=dje@google.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