Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 921618 - media-libs/zxing-cpp Add tests and python bindings
Summary: media-libs/zxing-cpp Add tests and python bindings
Status: UNCONFIRMED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal minor
Assignee: Gentoo KDE team
URL:
Whiteboard:
Keywords: PullRequest
Depends on:
Blocks:
 
Reported: 2024-01-08 21:48 UTC by Marcin Deranek
Modified: 2024-10-13 23:28 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
Sample media-libs/zxing-cpp ebuild with tests and python bindings (zxing-cpp-2.2.1.ebuild,1.38 KB, application/vnd.gentoo.ebuild)
2024-01-08 21:48 UTC, Marcin Deranek
Details
QA imperfect python multi-target ebuild (zxing-cpp-2.2.1-r1.ebuild,1.88 KB, application/vnd.gentoo.ebuild)
2024-08-21 00:31 UTC, Anthony Ryan
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Marcin Deranek 2024-01-08 21:48:13 UTC
Created attachment 881688 [details]
Sample media-libs/zxing-cpp ebuild with tests and python bindings

Please add tests and python binding to media-libs/zxing-cpp. See attached sample ebuild which does exactly that (tested).
Comment 1 Anthony Ryan 2024-08-21 00:30:46 UTC
I also made an attempt at this today, but I've decided to give up for now and use pip in a virtualenv after sinking too many hours trying to get this right.

I'm attaching my work in progress ebuild in case someone else wants to continue.

I really wanted to get python multi-version support working, because I detest python libraries that are single target. It makes migrating python versions such a headache when it's effortless on multi-version libs.

My ebuild has two lingering problems that have led me to give up:

1. We need distuitls-r1 to get the python metadata, but the upstream's setup.py custom cmake wrapper doesn't pass the cmake variables Gentoo expects. We get a handful of QA warnings for each one built.

Similarly, if we use cmake directly, we're missing the python metadata we expect.


2. I believe it's copying the entire library into each python .so file, which isn't ideal. At least all copies are going to be updated each time the ebuild is, but it should be using the system library and only having the python code in each python .so
Comment 2 Anthony Ryan 2024-08-21 00:31:49 UTC
Created attachment 900841 [details]
QA imperfect python multi-target ebuild