From: Eli Zaretskii <eliz@gnu.org>
To: Andrew Burgess <andrew.burgess@embecosm.com>
Cc: gdb-patches@sourceware.org, richard.bunt@arm.com
Subject: Re: [PATCH] gdb: Allow more control over where to find python libraries
Date: Thu, 06 Feb 2020 18:31:00 -0000 [thread overview]
Message-ID: <83lfpfftz8.fsf@gnu.org> (raw)
In-Reply-To: <20200206164617.7461-1-andrew.burgess@embecosm.com> (message from Andrew Burgess on Thu, 6 Feb 2020 16:46:17 +0000)
> 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?
next prev parent reply other threads:[~2020-02-06 18:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-06 16:46 Andrew Burgess
2020-02-06 18:31 ` Eli Zaretskii [this message]
2020-02-19 15:53 ` Andrew Burgess
2020-02-19 15:57 ` Eli Zaretskii
2020-02-07 17:58 ` Simon Marchi
2020-02-08 0:22 ` Andrew Burgess
2020-02-19 16:27 ` [PATCHv2] " Andrew Burgess
2020-02-19 17:09 ` Eli Zaretskii
2020-02-20 17:00 ` Tom Tromey
2020-02-20 19:22 ` Andrew Burgess
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=83lfpfftz8.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=andrew.burgess@embecosm.com \
--cc=gdb-patches@sourceware.org \
--cc=richard.bunt@arm.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