From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Holger Schurig <holgerschurig@gmail.com>
Cc: "U-Boot Version 2 (barebox)" <barebox@lists.infradead.org>
Subject: Re: why is some output placed under "srctree" even if i specify output dir?
Date: Fri, 27 Jun 2014 09:01:34 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.11.1406270858110.6308@localhost> (raw)
In-Reply-To: <CAOpc7mE1Z120BKc3bc8XDg2TaYUw6p3aKCE+dvwYOrhGrvTepg@mail.gmail.com>
On Fri, 27 Jun 2014, Holger Schurig wrote:
> Oh, that's interesting. Because sphinx-build can only be taught
> about one sourcedir. But in the srctree != objtree case we have two
> source dirs: the in srctree/Documentation with the provided *.rst
> files, and the objtree/Documentation/commands, with those files that
>
> @$(srctree)/Documentation/gen_commands.py $(srctree)
> $(objtree)/Documentation/commands
>
> could generate.
>
> Maybe gen_commands should also update the static *.rst files if
> srctree != objtree?
ok, that's something that can be decided by those of you higher up
the food chain; as i said, my only concern is that if i select an
external build directory, nothing should really be generated in the
source directory. but maybe i'm still unfamiliar with the build model
here -- still reading the sphinx docs, starting to really like this.
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
prev parent reply other threads:[~2014-06-27 13:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-27 12:34 why is some output placed under "srctree" even if i specify output dir? Robert P. J. Day
2014-06-27 12:56 ` Holger Schurig
2014-06-27 13:01 ` Robert P. J. Day [this message]
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.1406270858110.6308@localhost \
--to=rpjday@crashcourse.ca \
--cc=barebox@lists.infradead.org \
--cc=holgerschurig@gmail.com \
/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.