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 13:55:17 -0800 [thread overview]
Message-ID: <d1485bb9-33d1-47a2-94df-2b691728f601@runbox.com> (raw)
In-Reply-To: <87jzn8vxz9.fsf@zancanaro.id.au>
Fair enough, I just meant that it's pretty hard as a newcomer to know
which build system You're supposed to use to start with when
encountering a project where several languages are used.
Alexis
On 13/02/2024 13:46, Carlo Zancanaro wrote:
> On Tue, Feb 13 2024, Alexis Simon wrote:
>> 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'm not sure why this is counter-intuitive. The existence of any rust at
> all means you need to build rust code. The normal way to do that in Guix
> is to use the cargo-build-system.
>
> Equally, I don't find it strange that the upstream build instructions[1]
> ask me to install a rust compiler and cbindgen. I need to do that if I
> want to build rust code.
>
> It's also worth noting that there are 22 packages in Cargo.lock[2], so
> building the one rust file in the repository is a bit more involved.
>
> Carlo
>
> [1]: https://molpopgen.github.io/fwdpy11/misc/developersguide.html
> [2]: https://github.com/molpopgen/fwdpy11/blob/main/rust/fp11rust/Cargo.lock
next prev parent reply other threads:[~2024-02-13 21:55 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
2024-02-13 21:46 ` Carlo Zancanaro
2024-02-13 21:55 ` Alexis Simon [this message]
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=d1485bb9-33d1-47a2-94df-2b691728f601@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.