Em Fri, 01 Jul 2016 16:31:14 +0300 Jani Nikula <jani.nikula@xxxxxxxxx> escreveu: > On Fri, 01 Jul 2016, Mauro Carvalho Chehab <mchehab@xxxxxxxxxxxxxxx> wrote: > > Em Fri, 1 Jul 2016 15:24:44 +0300 > > Jani Nikula <jani.nikula@xxxxxxxxx> escreveu: > > > >> If the user requested specific DocBooks to be built using 'make > >> DOCBOOKS=foo.xml htmldocs', assume no Sphinx build is desired. This > >> check is transitional, and can be removed once we drop the DocBook > >> build. > > > > I guess this is actually a wrong assumption. I mean, it is valid to > > build multiple documents at the same time. Sometimes I do things > > like: > > make DOCBOOKS="media_api.xml device-drivers.xml" htmldocs > > > > When I want both docs to be compiled. > > > > What I would be expecting is that Sphinx would be looking into > > the DOCBOOKS targets and see if (some) of them belongs to it. > > > > Alternatively, we could add a separate makefile var for the > > Sphinx targets, but the logic would be more complex, as it > > should: > > Please let's not conflate DOCBOOKS to mean something other than > DocBooks. I think it'll be easier that way. OK. Works for me. > So I guess we'll need a way to build just a subset of the Sphinx > documentation. I would like that to be a somewhat generic thing, not > requiring a separate conf file for each subset. Is the granularity of a > directory enough? I've been meaning to look into passing different > <sourcedir> and <filenames> to sphinx-build for this, but I don't have > the time now. In the case of the media doc, it is actually a matter of building one rst file (linux_tv/index.rst). For that, I'm equally happy if we specify it via <sourcedir> or via <filename>. I suspect we'll end by needing filenames granularity in some future, but, if you find easier to just handle <sorcedir> for now, that's OK. Regards, Mauro -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html