From: Sascha Hauer <s.hauer@pengutronix.de>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: "U-Boot Version 2 (barebox)" <barebox@lists.infradead.org>
Subject: Re: [PATCH] Documentation: User manual, "barebox" section
Date: Mon, 30 Jun 2014 18:08:39 +0200 [thread overview]
Message-ID: <20140630160839.GL14257@pengutronix.de> (raw)
In-Reply-To: <alpine.LFD.2.11.1406301040190.13816@localhost>
On Mon, Jun 30, 2014 at 10:41:58AM -0400, Robert P. J. Day wrote:
>
> Various grammar/font fixes to that section, including adding an
> additional section describing how to properly do "out of tree"
> configuration and building.
>
> Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca>
Thanks for documenting the out of tree build. I always forget how to do
this. Finally I have a place to look at ;)
BTW buildinf the documentation out of tree is currently broken. This is
because we autogenerate the command files:
@$(srctree)/Documentation/gen_commands.py $(srctree) $(srctree)/Documentation/command
We should generate them in $(objtree), but then we the autogenerated
command files in another place than the rest of the documentation.
sphinx expects a single directory though.
I have no good idea how to solve this, other than copying all doc files
to $(objtree)/Documentation before calling sphinxs-build.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2014-06-30 16:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-30 14:41 Robert P. J. Day
2014-06-30 16:08 ` Sascha Hauer [this message]
2014-06-30 16:34 ` Robert P. J. Day
2014-06-30 16:59 ` Robert P. J. Day
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=20140630160839.GL14257@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=rpjday@crashcourse.ca \
/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