Github messages for voidlinux
 help / color / mirror / Atom feed
From: Frick-David <Frick-David@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Package Request: python3-hidapi (arch) or python3-hid (ubuntu)
Date: Fri, 04 Dec 2020 15:25:19 +0100	[thread overview]
Message-ID: <20201204142519.UWEr1pipQ1F7ylOo_4HPcg_UNniIwZJ_xCnG4o4rULs@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-19670@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1617 bytes --]

New comment by Frick-David on void-packages repository

https://github.com/void-linux/void-packages/issues/19670#issuecomment-738788306

Comment:
Per my discussion to package it:
```
- for a linux distro, you're going to need to build it linking to system hidapi (which is not its default)
- you need to pick which backends to enable (hidraw, libusb, or both)... default is both, but some distros may prefer only hidraw (which is the better one, unless hidraw is not available on that kernel for some reason)
- finally, if for some reason you need to override CFLAGS or anything like that, well, you may have issues with stuff being hardcoded in cython-hidapi's setup.py
again, the Arch PKGBUILD is a good reference, although they only build the hidraw backend and, like i mentined, this may not be the correct choice for void
regardless, be very careful that the build phase and the install phase are in sync in terms of which options you're sending to cython-hidapi's setup.py
(this is probably already handled by void, like options are only passed to build, and install uses the skip-build option... still, this is a common source of issues when building that lib with anything but its defaults options, which are not suitable for linux distros)
oh, the reason why you want to use system hidapi, instead of the default, is that the default is whatever hidapi version the project has pulled in... and no, then don't always stick to hidapi releases, in the past they have started to use a random commit
anyway: https://github.com/archlinux/svntogit-community/blob/packages/python-hidapi/trunk/PKGBUILD
```

  parent reply	other threads:[~2020-12-04 14:25 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-02  5:29 [ISSUE] " Frick-David
2020-03-02  9:35 ` xtraeme
2020-03-02 21:44 ` Frick-David
2020-03-03 13:59 ` jrigg
2020-03-03 14:12 ` jrigg
2020-03-06 21:18 ` Frick-David
2020-12-03  2:04 ` [ISSUE] [CLOSED] " Frick-David
2020-12-04  2:22 ` Frick-David
2020-12-04 13:38 ` Frick-David
2020-12-04 14:25 ` Frick-David [this message]
2020-12-04 19:13 ` Frick-David
2020-12-04 19:13 ` Frick-David
2020-12-14  0:39 ` Frick-David
2020-12-14  0:39 ` Frick-David

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=20201204142519.UWEr1pipQ1F7ylOo_4HPcg_UNniIwZJ_xCnG4o4rULs@z \
    --to=frick-david@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /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;
as well as URLs for NNTP newsgroup(s).