Hi Christoph (2020.01.20_13:58:10_+0200)
> It looks like dh-python should include Python_EXECUTABLE:
>
> https://gitlab.kitware.com/cmake/cmake/commit/06d9e67fbd2b2dfc9cba12327866b2f73eab8a18
Thanks for that. It's fairly easy to add those to the variables we
export, so done.
In libarcus' case
Fwiw, olasd found a way to make it work using the current dh_python
version:
https://salsa.debian.org/3dprinting-team/libarcus/commit/2503ec8273bdb67a710a0d2b633efa8909ed083c
But having that built-in would be nicer.
Christoph
>From 2503ec8273bdb67a710a0d2b633efa8909ed083c Mon Sep 17 00:00:00
Hi Lisandro,
> I'm writing this because at first I understood that dh-python should *set*
> this
> variable, but that's FindPython's job.
I'm afraid that's the case here. We need to invoke cmake twice: once
for Python 3.7 and once for 3.8 (to build extensions for both of them)
Hi! tl;dr: I was wrong.
On Tue, 21 Jan 2020 at 17:31, Lisandro Damián Nicanor Pérez Meyer
wrote:
>
> Hi!
[snip]
> > -- Found Python3: /usr/bin/python3.8 (found suitable version "3.8.1",
> > minimum required is "3.4") found components: Interpreter Development
> >
> > It looks like dh-python
Hi!
On 20/01/20 12:58, Christoph Berg wrote:
> Package: dh-python
> Version: 4.20191017
> Severity: normal
>
> libarcus and libsavitar from the 3dprinting team have the problem
> that the cmake jobs called from dh_auto_install use the wrong python
> version, note that 3.8 is used in the 3.7
Package: dh-python
Version: 4.20191017
Severity: normal
libarcus and libsavitar from the 3dprinting team have the problem
that the cmake jobs called from dh_auto_install use the wrong python
version, note that 3.8 is used in the 3.7 install pass:
6 matches
Mail list logo
