Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.maint.python > #12900 > unrolled thread

Re: Packaging a python module when already using cmake buildsystem

Back to article view | Back to linux.debian.maint.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: Packaging a python module when already using cmake buildsystem Christian Kastner <ckk@debian.org> - 2020-09-25 13:30 +0200

#12900 — Re: Packaging a python module when already using cmake buildsystem

On 2020-09-24 13:22, Francis Murtagh wrote:
> I'm trying to package a newly added python component of our
> tool https://tracker.debian.org/pkg/armnn.
> 
> It has a setup.py and uses SetupTools and DistUtils so I was hoping to
> add --with Python3 and hope that a lot of magic would be done by pybuild.
> However as I'm already using cmake as the build system I can't stick
> pybuild in there.

You can pass --buildsystem to individual targets, so something like this
might work (haven't tried it though):

override_dh_auto_build:
	dh_auto_build --buildsystem=cmake
	dh_auto_build --buildsystem=pybuild

If that particular example doesn't work, I'm sure that a closely related
one should (I've seen it before, but unfortunately don't recall where).

I did a quick search on codesearch.debian.net and here's one example of
a d/rules using two separate build systems:

    https://sources.debian.org/src/python-tenacity/6.2.0-4/debian/rules/?hl=16#L16

Best,
Christian

[toc] | [standalone]

Back to top | Article view | linux.debian.maint.python

csiph-web