From: Cairn <cairn@pm.me>
To: help guix <help-guix@gnu.org>
Subject: Issues updating the definition of qtserialport
Date: Tue, 11 Oct 2022 02:08:53 +0000 [thread overview]
Message-ID: <_iscfHYuJA2XxS8EK1xt9ce2gEYDzY3pBop-uxcad4pDWaU_zTZX4WnWgcvbIkJw5nLldH21eNyM6lXltDYMeQEHceasJVTyCKQidYiU0V4=@pm.me> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1289 bytes --]
Hey! I'm trying to update `qtserialport` to 6.3.1 for use with another package (and so it's up-to-date with other Qt modules). I'll make sure to rename the current package to "qtserialport-5" as well.
I'm having trouble getting it to recognize udev, which it requires. The current package definition has a patching phase which makes the path to udev absolute. I can't find any issues with this phase, and yet building with 6.3.1 throws an error:
CMake Error at /gnu/store/...-qtbase-6.3.1/lib/cmake/Qt6Core/Qt6CoreMacros.cmake:2440 (add_library):
Target "SerialPort" links to target "PkgConfig::Libudev" but the target was
not found. Perhaps a find_package() call is missing for an IMPORTED
target, or an ALIAS target is missing?
Call Stack (most recent call first):
/gnu/store/...-qtbase-6.3.1/lib/cmake/Qt6/QtModuleHelpers.cmake:128 (_qt_internal_add_library)
src/serialport/CMakeLists.txt:6 (qt_internal_add_module)
I'm pretty sure this is easy to reproduce. All I did was replace the version number, update dependencies and (after some testing) replaced the modify phases line with "#~(modify-phases #$phases". I'd love to know if there's anything I've obviously missed. If this is an easy fix, feel free to send a patch before me.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 855 bytes --]
next reply other threads:[~2022-10-11 2:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-11 2:08 Cairn [this message]
2022-10-12 4:05 ` Issues updating the definition of qtserialport Cairn
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='_iscfHYuJA2XxS8EK1xt9ce2gEYDzY3pBop-uxcad4pDWaU_zTZX4WnWgcvbIkJw5nLldH21eNyM6lXltDYMeQEHceasJVTyCKQidYiU0V4=@pm.me' \
--to=cairn@pm.me \
--cc=help-guix@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.