all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Alexis Simon <alexis.simon@runbox.com>
To: Carlo Zancanaro <carlo@zancanaro.id.au>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Python package with some rust dependency
Date: Tue, 13 Feb 2024 11:36:16 -0800	[thread overview]
Message-ID: <493a23e1-ab4e-4a29-b937-6b0455db3be0@runbox.com> (raw)
In-Reply-To: <875xyt8dna.fsf@zancanaro.id.au>

Thanks a lot Carlo

I see what you mean there, but I'm probably out of my depth in terms of 
guix/guile knowledge so this will probably have to wait for me to level up.

On 12/02/2024 15:29, Carlo Zancanaro wrote:
> Hi Alexis,
> 
> I don't really know much about building rust. Given this one repository
> has both, I wonder if it would make sense to build them separately (as
> two packages), and have one as an input of the other.
> 
> Presumably this would mean the python package taking the rust package as
> an input, but the details might be more involved.
> 
> On Sun, Feb 11 2024, Alexis Simon wrote:
>> Going the cargo-build-system way, it errors probably because there's
>> no rust crate at the root of the project.
> 
> One option here might be to add a phase after the unpack phase, to chdir
> into the directory with the rust crate. You can see examples in lots of
> places in the Guix repository, like wpa-supplicant-gui. Which has a
> phase modification:
> 
>      (add-after 'unpack 'chdir
>        (lambda _ (chdir "wpa_supplicant/wpa_gui-qt4")))
> 
> You'll need to change the directory to match where in the fwdpy11 source
> you need to go to build the rust stuff.

Ok, this seems really counter intuitive though to go and use the cargo 
build system for a python package only have a tiny part in rust.

> 
> I hope that helps,

Thanks for the pointers, it helps

> 
> Carlo


  reply	other threads:[~2024-02-13 19:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-12  1:49 Python package with some rust dependency Alexis Simon
2024-02-12 23:29 ` Carlo Zancanaro
2024-02-13 19:36   ` Alexis Simon [this message]
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

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

  git send-email \
    --in-reply-to=493a23e1-ab4e-4a29-b937-6b0455db3be0@runbox.com \
    --to=alexis.simon@runbox.com \
    --cc=carlo@zancanaro.id.au \
    --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.