From: "Ludovic Courtès" <ludo@gnu.org>
To: Efraim Flashner <efraim@flashner.co.il>
Cc: guix-devel@gnu.org
Subject: Re: Overhauling the cargo-build-system
Date: Fri, 11 Oct 2019 00:33:18 +0200 [thread overview]
Message-ID: <87d0f4p6xd.fsf@gnu.org> (raw)
In-Reply-To: <20191010155056.GD1301@E5400> (Efraim Flashner's message of "Thu, 10 Oct 2019 18:50:56 +0300")
Hello!
Efraim Flashner <efraim@flashner.co.il> skribis:
> I'd like to challenge the assumption that packages are both libraries
> and source. A 'library' in rust compiles into one of three types: a
> static library (libfoo.a), a shared library (libfoo.so), or a
> 'rust-library' (libfoo.rlib).
Why don’t we create .so files, then? They have NEEDED and RUNPATH, so
that could work like for C, no?
> Let me repeat that. We have 192 rust packages that no one needs or
> wants, except in source form.
Ouch! So the rlib file is never actually used?!
You said “it is not possible to link an rlib to another rlib”, but
that’s not necessarily a problem, it’s like .a libraries, no?
> PROPOSAL:
> Change all the rust packages we have now to be source-only. Rename them
> from rust-foo to rust-foo-src or rust-src-foo.
In the current scheme, can you actually do, say:
guix environment --ad-hoc rust rust-foo rust-bar
and then (pseudo syntax):
rustc mystuff.rust -lfoo -lbar
?
Thanks,
Ludo’.
next prev parent reply other threads:[~2019-10-10 22:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-10 15:50 Overhauling the cargo-build-system Efraim Flashner
2019-10-10 22:33 ` Ludovic Courtès [this message]
2019-10-11 14:13 ` Efraim Flashner
2019-11-16 6:31 ` Martin Becze
2019-11-16 16:37 ` John Soo
2019-11-16 18:44 ` Martin Becze
2019-11-16 21:33 ` Ludovic Courtès
2019-11-17 2:35 ` Martin Becze
2019-11-17 7:19 ` Efraim Flashner
2019-11-17 21:22 ` Ludovic Courtès
2019-11-18 10:20 ` Efraim Flashner
2019-11-23 17:27 ` Ludovic Courtès
2019-12-09 4:45 ` Chris Marusich
2019-12-09 20:14 ` Martin Becze
2019-12-19 16:10 ` Ludovic Courtès
2019-12-19 16:09 ` Ludovic Courtès
2019-12-19 17:23 ` John Soo
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=87d0f4p6xd.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=efraim@flashner.co.il \
--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 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.