python3-openvdb: build against the default python3 version

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

python3-openvdb: build against the default python3 version

Mathieu Malaterre-4
Hi all,

Could anyone point me at a Debian package (possibly using dh) where
multiple compilation are done (one against python3.7 and one against
python3.8). I'd like to avoid re-inventing the wheel for building a
cmake package (c++) which ships a single python module (so I need to
do one configure+build+install per python version).

Thanks,

On Fri, Mar 27, 2020 at 12:57 PM Emilio Pozuelo Monfort
<[hidden email]> wrote:

>
> Control: reopen -1 7.0.0-1
> Control: retitle -1 python3-openvdb: build against the default python3 version
>
> On Mon, 24 Feb 2020 11:10:49 +0100 Mathieu Malaterre <[hidden email]> wrote:
> > Control: tags -1 + patch
> > Control: retitle -1 replace python3-all-dev with python3.7-dev
>
> Err, that's not really the solution.
>
> The not ideal solution was to build for the default python version, i.e.
> build-depend on python3-dev and use python3. That would have built against
> python3.7 when that was the default, and against python3.8 now that it has
> changed. And with a binNMU from the release team, you wouldn't have even noticed.
>
> The ideal solution is to build against python3-all-dev and build for *all*
> supported python versions. So that when python3.7 and python3.8 are both
> supported, you build the python extension for both of them.
>
> Cheers,
> Emilio

Reply | Threaded
Open this post in threaded view
|

Re: python3-openvdb: build against the default python3 version

Scott Kitterman-5
Pybuild has a cmake plugin that I think is relatively new.  It may handle the
complexity for you, but I've never tried it.  We used to do this with pykde4,
which is available on snapshot..d.o.

Scott K

On Friday, March 27, 2020 8:48:33 AM EDT Mathieu Malaterre wrote:

> Hi all,
>
> Could anyone point me at a Debian package (possibly using dh) where
> multiple compilation are done (one against python3.7 and one against
> python3.8). I'd like to avoid re-inventing the wheel for building a
> cmake package (c++) which ships a single python module (so I need to
> do one configure+build+install per python version).
>
> Thanks,
>
> On Fri, Mar 27, 2020 at 12:57 PM Emilio Pozuelo Monfort
>
> <[hidden email]> wrote:
> > Control: reopen -1 7.0.0-1
> > Control: retitle -1 python3-openvdb: build against the default python3
> > version>
> > On Mon, 24 Feb 2020 11:10:49 +0100 Mathieu Malaterre <[hidden email]>
wrote:

> > > Control: tags -1 + patch
> > > Control: retitle -1 replace python3-all-dev with python3.7-dev
> >
> > Err, that's not really the solution.
> >
> > The not ideal solution was to build for the default python version, i.e.
> > build-depend on python3-dev and use python3. That would have built against
> > python3.7 when that was the default, and against python3.8 now that it has
> > changed. And with a binNMU from the release team, you wouldn't have even
> > noticed.
> >
> > The ideal solution is to build against python3-all-dev and build for *all*
> > supported python versions. So that when python3.7 and python3.8 are both
> > supported, you build the python extension for both of them.
> >
> > Cheers,
> > Emilio


signature.asc (849 bytes) Download Attachment