From: "Ludovic Courtès" <ludo@gnu.org>
To: Mathieu Othacehe <othacehe@gnu.org>
Cc: 55321@debbugs.gnu.org
Subject: [bug#55321] Document building for foreign architectures
Date: Sun, 22 May 2022 22:47:13 +0200 [thread overview]
Message-ID: <874k1hqoq6.fsf@gnu.org> (raw)
In-Reply-To: <87k0avdi8p.fsf@gnu.org> (Mathieu Othacehe's message of "Sun, 08 May 2022 19:52:38 +0200")
Hi!
I’m late to the party but I’d like to contribute this: 👍
Some nitpicking though:
> +Foreign architectures
> +* Using cross-compilation:: Build for foreign architecture using cross-compilation.
> +* Using native building:: Build for foreign architectures natively.
Please use “title case” for node and section names, as in:
Foreign Architectures
> +You might need to use GNU Guix to produce packages (@pxref{Invoking guix
> +package}), packs (@pxref{Invoking guix pack}) or even full systems
> +(@pxref{Invoking guix system}) targeting computers with different CPU
> +architectures than the one of your current CPU.
> +
> +GNU Guix supports two distinct mechanisms to target foreign
As a rule of thumb, I think it’s good to avoid repeating “GNU Guix”
because the reader most likely knows that it’s the manual they’re
reading :-) and because we can often be more precise or less verbose.
In this case, we could write:
You can build packages, packs, or even full systems targeting
computers with a different CPU architecture than the CPU you are
using, or running a different operating system.
> +@item
> +The second one, called native building, consists in building using the
> +CPU instruction set of the foreign system you are targeting. It often
> +requires emulation, using the QEMU program for instance.
> +The targets are specified as GNU triplets (@pxref{Specifying Target
s/The targets/Targets/ (or “Cross-compilation targets”?)
> +@node Using native building
> +@section Using native building
Or: “Native Builds”? (“Using […] building” sounds weird to me.)
That’s all, thank you! :-)
Ludo’.
next prev parent reply other threads:[~2022-05-22 20:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-08 17:52 [bug#55321] Document building for foreign architectures Mathieu Othacehe
2022-05-22 2:42 ` Maxim Cournoyer
2022-05-22 13:14 ` bug#55321: " Mathieu Othacehe
2022-05-22 20:47 ` Ludovic Courtès [this message]
2022-05-25 7:49 ` [bug#55321] " Mathieu Othacehe
2022-05-25 13:28 ` Ludovic Courtès
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=874k1hqoq6.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=55321@debbugs.gnu.org \
--cc=othacehe@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.