Re: Add LIBDIR/gdb/python-<version> to Python search path

[Daniel Jacobowitz <dan@codesourcery.com>]

On Thu, May 20, 2010 at 11:40:01AM -0700, Joel Brobecker wrote:
> The intent is to allow us to package up a GDB binary with python support.
> Since we do not know whether the target system on which GDB is going to
> be installed has the correct version of python (or even if it has, whether
> it has been built correctly), we want to also package up the python
> library as well.  That way, regardless of what the target system provides,
> we know the debugger will be using a well-defined version of the python
> library.
> 
> The location I chose for that is GDB_LIBDIR/python-<version>, where
> GDB_LIBDIR is LIBDIR/gdb by default.  So, for instance, with a prefix
> set to /my/prefix/dir, a default GDB_LIDIR, and Python version 2.5,
> we'd be using: /my/prefix/dir/lib/gdb/python-2.5.

I have a not-as-nice local patch to achieve a similar goal, so I'm in
favor.  But what do you see as the role of GDB_LIBDIR, other than
this?

GDB isn't the only program in our distribution that needs an included
Python, so we're not going to put it in lib/gdb.  But it'd be nice to
have other GDB-private data outside of top-level lib/.

-- 
Daniel Jacobowitz
CodeSourcery