From: "John Ericson" <list@johnericson.me>
To: "Miguel Ojeda" <miguel.ojeda.sandonis@gmail.com>
Cc: rust-for-linux@vger.kernel.org
Subject: Re: [Rust for Linux] Happy new year & Poll for call
Date: Fri, 08 Jan 2021 09:34:48 -0500 [thread overview]
Message-ID: <f8fc7d60-9f9f-4892-85f9-1ae1d20f3291@www.fastmail.com> (raw)
In-Reply-To: <CANiq72mb4G=Hb9j8BxxFFXwW2YvU72KbPYDw3SvV1Wn080gEjA@mail.gmail.com>
On Fri, Jan 8, 2021, at 3:26 AM, Miguel Ojeda wrote:
> On the topic of -Z build-std, I have been working on [1] which integrates the building of core, alloc, etc. in Kbuild instead of using build-std.
Oh cool!
> even if build-std stabilizes, starts getting used by rustbuild itself, etc.
And for what it's worth, I think this approach also benefits from build-std maturing, because it's really compiling the standard library from the source alongside the rest of the (Rust parts of a) project vs using pre-built binaries that is the crucial distinction here. Both build-std and this are squarely the former not the latter.
John
prev parent reply other threads:[~2021-01-08 14:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-03 8:18 [Rust for Linux] Happy new year & Poll for call Miguel Ojeda
2021-01-07 21:03 ` Miguel Ojeda
2021-01-07 21:14 ` Alex Gaynor
2021-01-07 22:46 ` John Ericson
2021-01-08 1:22 ` John Ericson
2021-01-08 8:26 ` Miguel Ojeda
2021-01-08 14:34 ` John Ericson [this message]
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=f8fc7d60-9f9f-4892-85f9-1ae1d20f3291@www.fastmail.com \
--to=list@johnericson.me \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=rust-for-linux@vger.kernel.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.
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 NNTP newsgroup(s).