From: Heinrich Schuchardt <xypron.glpk@gmx.de>
To: u-boot@lists.denx.de
Subject: [PATCH 2/2] doc: describe building with GCC
Date: Sun, 6 Sep 2020 13:38:17 +0200 [thread overview]
Message-ID: <0ca537f4-7046-2bf8-4012-cd84e421ac4e@gmx.de> (raw)
In-Reply-To: <20200905124023.GK24856@bill-the-cat>
On 9/5/20 2:40 PM, Tom Rini wrote:
> 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!
I think the documentation serves different readers:
1) Users who want to build U-Boot and understand how to use it. They
will be interested in:
* What is U-Boot?
* Building U-Boot
* Board specific installation information
* Booting
* Using the shell
* Firmware update
In this area we are lacking a lot. Between "Build U-Boot" and "Develop
U-Boot" I see a need for a main chapter "Using U-Boot".
2) Developers who want to modify U-Boot and contribute to upstream. They
will be interested in
* APIs
* Inner workings of U-Boot
* Contribution guidelines
In this area we should strive to move the existing documentation to
reStructured text.
The description about the clang implementation of gd should be moved to
the "Develop U-Boot" section as a non-developer would not care about it.
We can add a chapter "Global data" collecting all gd related information.
Best regards
Heinrich
next prev parent reply other threads:[~2020-09-06 11:38 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
2020-09-06 11:38 ` Heinrich Schuchardt [this message]
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=0ca537f4-7046-2bf8-4012-cd84e421ac4e@gmx.de \
--to=xypron.glpk@gmx.de \
--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