From: Efraim Flashner <efraim@flashner.co.il>
To: Hartmut Goebel <h.goebel@crazy-compilers.com>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: rust (build system) deficits
Date: Mon, 9 Mar 2020 13:17:48 +0200 [thread overview]
Message-ID: <20200309111748.GJ1423@E5400> (raw)
In-Reply-To: <192815e6-7d83-2ef2-1f68-4ae3e0cce04e@crazy-compilers.com>
[-- Attachment #1: Type: text/plain, Size: 1815 bytes --]
On Mon, Mar 09, 2020 at 10:26:01AM +0100, Hartmut Goebel wrote:
> Am 08.03.20 um 21:10 schrieb John Soo:
> > Hmm. Can you elaborate more on “not able to build non-trivial rust applications”?
>
> I'm working on packaging sequoia-openpgp.org.
>
> This requires nettle-sys, a FFI to nettle. nettly-sys "optionally"
> requires "nettle-src". I added a phase to "nettle-sys" to remove the
> "optional" dependency. nettle-sys also requires bindgen.
As I assume you saw, there is nothing "optional" when using the
cargo-build-system. For nettle-sys and nettle-src I suggest looking at
rust-openssl-sys-no-vendor.patch which I modified from Debian. It takes
care of pretending openssl-sys also provides openssl-src.
> A second dependancy is "sequoia-openpgp", which requires rhe lalrpop
> parser generator for building.
>
> Now when building `sequioa-sqv`, I need to add all these dependencies again:
>
> - nettle-src, since it is "optional" for nettle-sys - and the phase was
> not executed.
> - bindgen, since it is required to build nettle-sys
> - lalrpop, since it is required for building sequoia-openpgp
>
> > Patching a library Cargo.toml seems like an excellent job for source patches or snippets.
>
> Quite some packages change Cargo.toml in a phase, e.g. rust-openssl-0.7.
> Thus I assumed, this is the way to go.
That could probably move to a snippet, or even into the
cargo-build-system. IIRC there are only 3 patterns like that which
appear multiple times, and they're only relevant when building that
actual crate, not when it's "just a dependency".
--
Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-03-09 11:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-07 13:46 rust (build system) deficits Hartmut Goebel
2020-03-07 18:41 ` John Soo
2020-03-08 17:16 ` Hartmut Goebel
2020-03-08 20:10 ` John Soo
2020-03-08 20:20 ` John Soo
2020-03-09 9:26 ` Hartmut Goebel
2020-03-09 11:17 ` Efraim Flashner [this message]
2020-03-09 14:00 ` John Soo
2020-03-09 14:50 ` Hartmut Goebel
2020-03-09 17:48 ` John Soo
2020-03-11 17:55 ` Hartmut Goebel
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=20200309111748.GJ1423@E5400 \
--to=efraim@flashner.co.il \
--cc=guix-devel@gnu.org \
--cc=h.goebel@crazy-compilers.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).