[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87mvm1po6k.fsf@intel.com>
Date: Fri, 01 Jul 2016 14:56:03 +0300
From: Jani Nikula <jani.nikula@...el.com>
To: Markus Heiser <markus.heiser@...marit.de>
Cc: Mauro Carvalho Chehab <mchehab@....samsung.com>,
Jonathan Corbet <corbet@....net>, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org, hverkuil@...all.nl,
daniel.vetter@...ll.ch, airlied@...il.com,
grant.likely@...retlab.ca, rdunlap@...radead.org, keithp@...thp.com
Subject: Re: [PATCH] doc: flat-table directive
On Fri, 01 Jul 2016, Markus Heiser <markus.heiser@...marit.de> wrote:
> Am 01.07.2016 um 12:44 schrieb Jani Nikula <jani.nikula@...el.com>:
>
>> On Fri, 01 Jul 2016, Mauro Carvalho Chehab <mchehab@....samsung.com> wrote:
>>> Not being able to compile just one docbook is a regression and breaks
>>> my process. This needs to be fixed.
>>
>> Do you have a regression with *DocBook XML* on docs-next now? If yes,
>> clearly that must be fixed ASAP.
>
> Now I see the problem ...
>
> It seems that we didn't neglected that the DocBook Makefile
> builds single books, e.g.
>
> make DOCBOOKS=device-drivers.xml htmldocs
>
> Since the Makefile.sphinx does not care the environment DOCBOOKS,
> the XML is build and the reST also, where only the XML content
> should be build.
>
> Jani, may could you apply a small fix on the Makefile.sphinx which
> takes into account, not to run the sphinx-build if the DOCBOOK
> environment is set .. is it a solution for a start?
That is not the problem. Makefile.sphinx happily ignores DOCBOOKS. For
example 'make DOCBOOKS=kernel-api.xml htmldocs' on docs-next works just
fine for me. Sphinx build ignores DOCBOOKS, the DocBook build works just
like it always did.
BR,
Jani.
--
Jani Nikula, Intel Open Source Technology Center
Powered by blists - more mailing lists