Re: [PATCH] gdb: Allow more control over where to find python libraries

[Andrew Burgess <andrew.burgess@embecosm.com>]

* Eli Zaretskii <eliz@gnu.org> [2020-02-06 20:31:23 +0200]:

> > From: Andrew Burgess <andrew.burgess@embecosm.com>
> > Cc: Richard Bunt <richard.bunt@arm.com>,	Andrew Burgess <andrew.burgess@embecosm.com>
> > Date: Thu,  6 Feb 2020 16:46:17 +0000
> > 
> > The motivation behind this commit is to make it easier to bundle the
> > Python libraries with GDB when linking GDB against a static
> > libpython, the Python libraries will be manually added into the GDB
> > installation tree, and GDB should be able to find them at run-time.
> > The installation tree will look like this:
> > 
> >   .
> >   |-- bin/
> >   |-- include/
> >   |-- lib/
> >   |   `-- python3.8/
> >   `-- share/
> > 
> > The benefit here is that the entire installation tree can be bundled
> > into a single archive and copied to another machine with a different
> > version of Python installed, and GDB will still work, including its
> > Python support.
> 
> This assumes that the Python libraries and support files are part of
> the GDB distribution, right?  But if those are distributed with GDB,
> so should be their sources, to adhere to the license, no?

Hi Eli,

As Simon mentioned I don't think that I described my intentions very
well.  The intended use case for this situation is building the Python
interpreter statically into GDB, and then placing Python's *.py files
into a directory relative to the built GDB executable, and have GDB
manage to find them.

The use for this would be that at XXX organisation I can build a
version of GDB, package it up into a tar-file and copy this onto
several different machines, which might be running different OS
versions.

In this situation I don't think there's any licensing issue as the
builds of GDB are not going outside the XXX organisation.

If I did decide to distribute the pre-built GDB tar-files outside of
XXX, then the source for GDB, and the source for Python would be made
available also from XXX, but I didn't believe simply distributing two
pre-built things in one package means I have to upstream merge the two
projects - have I miss-understood?

Thanks,
Andrew