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: [RFA] Update gdb's configure instructions


>>>>> "Eli" == Eli Zaretskii <eliz@gnu.org> writes:

Eli> Did this change since GDB 8.2?  Because when I built GDB 8.2, the
Eli> argument to --with-python was the top-level directory of the Python
Eli> installation on my build system.

It can be either, it turns out.  How's this text?

`--with-python[=PYTHON]'
     Build GDB with Python scripting support.  (Done by default if
     libpython is present and found at configure time.)  Python makes
     GDB scripting much more powerful than the restricted CLI
     scripting language.  If your host does not have Python installed,
     you can find it on `http://www.python.org/download/'.  The oldest
     version of Python supported by GDB is 2.4.  The optional argument
     PYTHON is used to find the Python headers and libraries.  It can
     be either the name of a Python executable, or the name of the
     directory in which Python is installed.

and in gdb.texinfo:

    @item Python
    @value{GDBN} can be scripted using Python language.  @xref{Python}.
    By default, @value{GDBN} will be compiled if the Python libraries are
    installed and are found by @file{configure}.  You can use the
    @code{--with-python} option to request Python, and pass either the
    file name of the relevant @code{python} executable, or the name of the
    directory in which Python is installed, to choose a particular
    installation of Python.

Tom


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