unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Alexis Simon <alexis.simon@runbox.com>
To: help-guix <help-guix@gnu.org>
Subject: Python package with some rust dependency
Date: Sun, 11 Feb 2024 17:49:32 -0800	[thread overview]
Message-ID: <0fdf88c8-1f1a-420b-a27c-aa07cb273059@runbox.com> (raw)

Hi,

I've been trying to package a science python software that mixes some 
C++ and rust dependencies.
https://github.com/molpopgen/fwdpy11

I'm stuck in how to handle this.
Going the pyproject-build-system way, the cargo part errors at accessing 
crates.io as would be expected, I guess I should probably patch the 
cargo.toml to use the local registry?

Going the cargo-build-system way, it errors probably because there's no 
rust crate at the root of the project.

Here is what I've tried so far
https://codeberg.org/alxsim/local-channel/src/branch/main/packages/fwdpy11.scm

Does anyone have pointers on how to handle the build of this packages?

Thanks,
Alexis


             reply	other threads:[~2024-02-12  1:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-12  1:49 Alexis Simon [this message]
2024-02-12 23:29 ` Python package with some rust dependency Carlo Zancanaro
2024-02-13 19:36   ` Alexis Simon
2024-02-13 21:46     ` Carlo Zancanaro
2024-02-13 21:55       ` Alexis Simon
2024-02-16  6:08         ` Alexis Simon
2024-02-17  0:02           ` Alexis Simon
2024-02-17 11:50             ` Carlo Zancanaro
2024-02-17 16:46               ` Alexis Simon
2024-02-17 19:25                 ` Alexis Simon
2024-02-18  3:03                 ` Carlo Zancanaro

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=0fdf88c8-1f1a-420b-a27c-aa07cb273059@runbox.com \
    --to=alexis.simon@runbox.com \
    --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. 
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).