From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [PATCH 2/2] doc: describe building with GCC
Date: Sat, 5 Sep 2020 08:40:23 -0400 [thread overview]
Message-ID: <20200905124023.GK24856@bill-the-cat> (raw)
In-Reply-To: <20200905085853.29081-3-xypron.glpk@gmx.de>
On Sat, Sep 05, 2020 at 10:58:53AM +0200, Heinrich Schuchardt wrote:
> Provide a description of the U-Boot build process with GCC in the HTML
> documentation.
>
> Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
> ---
> doc/build/gcc.rst | 119 ++++++++++++++++++++++++++++++++++++++++++++
> doc/build/index.rst | 1 +
> 2 files changed, 120 insertions(+)
> create mode 100644 doc/build/gcc.rst
It's good to have this. Can we restructure things so that it's clear
that the majority of this is toolchain independent and we can update the
clang doc, or if this becomes a more generic "build U-Boot for target"
doc, we just need to add a section about the Clang caveat about how gd
works and then it's just noting that instead of
CROSS_COMPILE=aarch64-linux-gnu- it's CROSS_COMPILE="clang -target
aarch64-linux-gnu" ? Thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20200905/787d9aa9/attachment.sig>
next prev parent reply other threads:[~2020-09-05 12:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-05 8:58 [PATCH 0/2] doc: describe building with GCC Heinrich Schuchardt
2020-09-05 8:58 ` [PATCH 1/2] doc: describe source repository Heinrich Schuchardt
2020-09-14 19:41 ` Tom Rini
2020-09-05 8:58 ` [PATCH 2/2] doc: describe building with GCC Heinrich Schuchardt
2020-09-05 12:40 ` Tom Rini [this message]
2020-09-06 11:38 ` Heinrich Schuchardt
2020-09-14 19:41 ` Tom Rini
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=20200905124023.GK24856@bill-the-cat \
--to=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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