mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: "U-Boot Version 2 (barebox)" <barebox@lists.infradead.org>
Subject: why is some output placed under "srctree" even if i specify output dir?
Date: Fri, 27 Jun 2014 08:34:07 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.2.11.1406270830070.5167@localhost> (raw)


  perhaps another silly question, but i typically like to build with
all output generated in an external directory to keep my source
directory clean, but if i do that building the docs for barebox on the
"doc" branch:

  $ export KBUILD_OUTPUT=../barebox_build
  $ make docs

i still get the output files "Documentation/commands/*.rst" dumped in
my source directory because of:

docs: FORCE
        @mkdir -p $(srctree)/Documentation/commands
        @$(srctree)/Documentation/gen_commands.py $(srctree) $(srctree)/Documentation/commands
        @$(SPHINXBUILD) -b html -d $(objtree)/doctrees $(srctree)/Documentation \
                $(objtree)/Documentation/html

is this deliberate? it strikes me as inconsistent if i *explicitly*
specify an external build directory.

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-27 12:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-27 12:34 Robert P. J. Day [this message]
2014-06-27 12:56 ` Holger Schurig
2014-06-27 13:01   ` 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.1406270830070.5167@localhost \
    --to=rpjday@crashcourse.ca \
    --cc=barebox@lists.infradead.org \
    /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