All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: "U-Boot Version 2 (barebox)" <barebox@lists.infradead.org>
Subject: Re: [PATCH] Documentation: User manual, "barebox" section
Date: Mon, 30 Jun 2014 12:34:35 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.2.11.1406301230030.30890@localhost> (raw)
In-Reply-To: <20140630160839.GL14257@pengutronix.de>

On Mon, 30 Jun 2014, Sascha Hauer wrote:

> 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.

  hmmmmmm ... i seem to be able to generate the docs out of tree just
fine. i'll check again and make sure. all i'm doing is setting:

  $ export KBUILD_OUTPUT=<dest dir>

and running

  $ make docs

and the sphinx-based documentation appears to be created just fine in
that output/build directory. am i misunderstanding something here?

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2014-06-30 16:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-30 14:41 [PATCH] Documentation: User manual, "barebox" section Robert P. J. Day
2014-06-30 16:08 ` Sascha Hauer
2014-06-30 16:34   ` Robert P. J. Day [this message]
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=alpine.LFD.2.11.1406301230030.30890@localhost \
    --to=rpjday@crashcourse.ca \
    --cc=barebox@lists.infradead.org \
    --cc=s.hauer@pengutronix.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 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.