unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Efraim Flashner <efraim@flashner.co.il>
To: David Elsing <david.elsing@posteo.net>
Cc: Andreas Enge <andreas@enge.fr>, guix-devel@gnu.org
Subject: Re: Problem building rust application
Date: Thu, 21 Nov 2024 21:21:10 +0200	[thread overview]
Message-ID: <Zz-IJpbxk4LOrn6-@3900XT> (raw)
In-Reply-To: <7yed35a6cu.fsf@posteo.net>

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

On Wed, Nov 20, 2024 at 10:27:29PM +0000, David Elsing wrote:
> Hi,
> 
> Andreas Enge <andreas@enge.fr> writes:
> > starting phase `build'
> > error: failed to select a version for `core-graphics-types`.
> >     ... required by package `core-graphics v0.23.2`
> >     ... which satisfies dependency `core-graphics = "^0.23.2"` of package `kanata v1.7.0-prerelease-2 (/tmp/guix-build-kanata-1.7.0-prerelease-2.drv-0/kanata-1.7.0-prerelease-2)`
> > versions that meet the requirements `^0.1` are: 0.1.1
> >
> > the package `core-graphics` depends on `core-graphics-types`, with features: `link` but `core-graphics-types` does not have these features.
> >
> > failed to select a version for `core-graphics-types` which could resolve this conflict
> >
> > We do have core-graphics-types@0.23.2 and core-graphics-types@0.1.1, so the
> > versions look okay to my untrained eye.
> 
> it appears that the crates `core-graphics` and `core-graphics-types` are
> developed in the same repository [1]. Looking at the commit where the
> `core-graphics` version was set to 0.23.2 [2], the
> corresponding `core-graphics-types` crate version (0.1.3) already has
> the "link" feature, but version 0.1.1 (the version in Guix) does not.
> This seems to be a mistake in the `core-graphics` crate.
> 
> As `kanata` depends on `core-graphics` version 0.23.2, you should add
> a package for rust-core-graphics-types with version 0.1.3 (the latest
> 0.1.* version) and use that instead in the #:cargo-inputs of
> rust-core-graphics-0.23.
> 
> Cheers,
> David
> 
> [1] https://github.com/servo/core-foundation-rs
> [2] https://github.com/servo/core-foundation-rs/blob/dd284a07f4aec3b78667462cd7ef56d0c6153c68
> 

Through some playing around I was able to build
rust-core-graphics-types@0.1.3, but I had to disable the automatic
linking. Since that crate is specifically for macOS I think the easiest
option you have is to remove the dependency from Cargo.toml with a
substitute* and just not include it.

-- 
Efraim Flashner   <efraim@flashner.co.il>   אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2024-11-21 19:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-20 20:40 Problem building rust application Andreas Enge
2024-11-20 22:27 ` David Elsing
2024-11-21 19:21   ` Efraim Flashner [this message]

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Zz-IJpbxk4LOrn6-@3900XT \
    --to=efraim@flashner.co.il \
    --cc=andreas@enge.fr \
    --cc=david.elsing@posteo.net \
    --cc=guix-devel@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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).