From: Hartmut Goebel <h.goebel@crazy-compilers.com>
To: Pjotr Prins <pjotr.public12@thebird.nl>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Some more rust/cargo insights
Date: Mon, 7 Jun 2021 14:04:02 +0200 [thread overview]
Message-ID: <b9076919-0409-32a4-e516-98cf642b7272@crazy-compilers.com> (raw)
In-Reply-To: <20210607082830.uo73mksfvogfxxf6@thebird.nl>
Am 07.06.21 um 10:28 schrieb Pjotr Prins:
> Exactly my idea. One challenge will be that the source of dependencies
> need to be available - think of it as include files. One thing we
> could do as ship them as part of the Guix package. Or have a separate
> one for sources. We do that for include files already.
Well, the current cargo-build-system already handles the source
dependencies.
We need to aim towards pre-built libraries (rlib, much like .a files in
C, I assume)
When cargo calls rustc, the command looks like:
LD_LIBRARY_PATH='$PWD/target/release/deps:/gnu/store/…-rust-1.45.2/lib' \
rustc … src/lib.rs --crate-type lib \
-L dependency=$PWD/target/release/deps \
--extern
xmlparser=$PWD/target/release/deps/libxmlparser-53596ac1828b1c97.rmeta
Thus I assume one could pass the rlib's of all dependencies in -L and
the respective mata-data in --extern
--
Regards
Hartmut Goebel
| Hartmut Goebel | h.goebel@crazy-compilers.com |
| www.crazy-compilers.com | compilers which you thought are impossible |
next prev parent reply other threads:[~2021-06-07 12:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-06 14:15 Some more rust/cargo insights Hartmut Goebel
[not found] ` <20210606183857.gthvipntymstivh4@thebird.nl>
2021-06-07 7:10 ` Hartmut Goebel
2021-06-07 8:28 ` Pjotr Prins
2021-06-07 12:04 ` Hartmut Goebel [this message]
2021-06-07 15:13 ` John Soo
2021-06-07 15:15 ` John Soo
2021-06-07 16:26 ` Hartmut Goebel
2021-06-07 16:41 ` Hartmut Goebel
2021-06-08 9:15 ` Efraim Flashner
2021-06-08 15:38 ` Hartmut Goebel
2021-06-14 5:22 ` Maxim Cournoyer
-- strict thread matches above, loose matches on Subject: below --
2021-06-07 18:48 Leo Prikler
2021-06-08 17:01 ` Leo Famulari
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=b9076919-0409-32a4-e516-98cf642b7272@crazy-compilers.com \
--to=h.goebel@crazy-compilers.com \
--cc=guix-devel@gnu.org \
--cc=pjotr.public12@thebird.nl \
/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.