From: Mauro Carvalho Chehab <mchehab@infradead.org>
To: Jani Nikula <jani.nikula@intel.com>
Cc: Mauro Carvalho Chehab <mchehab@s-opensource.com>,
Hans Verkuil <hverkuil@xs4all.nl>,
Linux Media Mailing List <linux-media@vger.kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org,
Markus Heiser <markus.heiser@darmarit.de>,
Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: Re: parts of media docs sphinx re-building every time?
Date: Wed, 10 Aug 2016 05:47:55 -0300 [thread overview]
Message-ID: <20160810054755.0175f331@vela.lan> (raw)
In-Reply-To: <8760rbp8zh.fsf@intel.com>
Em Mon, 08 Aug 2016 18:37:38 +0300
Jani Nikula <jani.nikula@intel.com> escreveu:
> Hi Mauro & co -
>
> I just noticed running 'make htmldocs' rebuilds parts of media docs
> every time on repeated runs. This shouldn't happen. Please investigate.
I was unable to reproduce it here. Are you passing any special options
to the building system?
According to media Makefile, it should run the script only on four
conditions:
- if the dynamically-generated rst file is not found (e. g. after
make cleandocs);
- if the header file is changed;
- if the exceptions file changes;
- if the perl parser is changed.
All rules are like:
$(BUILDDIR)/audio.h.rst: ${UAPI}/dvb/audio.h ${PARSER} $(SRC_DIR)/audio.h.rst.exceptions
Regards,
Mauro
Cheers,
Mauro
next prev parent reply other threads:[~2016-08-10 18:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8760rbp8zh.fsf@intel.com>
2016-08-08 16:07 ` parts of media docs sphinx re-building every time? Markus Heiser
2016-08-08 17:26 ` Mauro Carvalho Chehab
2016-08-10 7:46 ` Jani Nikula
2016-08-10 9:04 ` Mauro Carvalho Chehab
2016-08-10 9:15 ` Jani Nikula
2016-08-10 9:22 ` Mauro Carvalho Chehab
2016-08-10 9:58 ` Markus Heiser
2016-08-10 10:11 ` Mauro Carvalho Chehab
2016-08-10 12:24 ` Daniel Vetter
2016-08-10 7:42 ` Jani Nikula
2016-08-10 8:23 ` Mauro Carvalho Chehab
2016-08-10 8:52 ` Mauro Carvalho Chehab
2016-08-10 8:47 ` Mauro Carvalho Chehab [this message]
2016-08-10 9:23 ` Jani Nikula
2016-08-10 13:46 ` Jonathan Corbet
2016-08-10 14:16 ` Markus Heiser
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=20160810054755.0175f331@vela.lan \
--to=mchehab@infradead.org \
--cc=corbet@lwn.net \
--cc=daniel.vetter@ffwll.ch \
--cc=hverkuil@xs4all.nl \
--cc=jani.nikula@intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=markus.heiser@darmarit.de \
--cc=mchehab@s-opensource.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox