why is some output placed under "srctree" even if i specify output dir?

why is some output placed under "srctree" even if i specify output dir?

[Robert P. J. Day]

  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

Re: why is some output placed under "srctree" even if i specify output dir?

[Holger Schurig]

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?

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

Re: why is some output placed under "srctree" even if i specify output dir?

[Robert P. J. Day]

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