This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Add support for the GDB Python Library


On Wed, May 26, 2010 at 6:24 PM, Doug Evans <dje@google.com> wrote:
> On Wed, May 26, 2010 at 5:08 PM, Joel Brobecker <brobecker@adacore.com> wrote:
>> Hello,
>>
>> One of the things that we still don't have in the FSF tree is a "GDB
>> Python Library" - that is a collection of standard Python scripts that
>> come with GDB. The idea is to help future contributions but setting
>> things up so that it's easy to add new python-based commands/functions/
>> features, etc.
>>
>> This is what this couple of patches provide:
>> ?- Patch #1: Defines a pythondir where the GDB Python library is
>> ? ?expected to be found, and enhances the GDB/python support to
>> ? ?look for them there.
>> ?- Path #2: is built on top of patch #1, and provides the first
>> ? ?such python patch. ?We selected one form project archer that
>> ? ?might be useful: pahole.py.
>
> Is there a reason to not make pythondir be $(GDB_DATADIR)/python or some such?
> [I'm not sure to what extent .pyc files are architecture independent.
> Is that it?]

For reference sake,
I did a configure of python 2.6.5 with different values for --prefix
and --exec-prefix.
*.py* got put in $prefix/lib/python2.6.
lib-dynload got put in $exec_prefix/lib/python2.6.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]