From: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
To: Sakari Ailus <sakari.ailus@iki.fi>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab@infradead.org>
Subject: Re: [PATCH] DocBook: only copy stuff to media_api if media xml is generated
Date: Thu, 19 Nov 2015 09:53:00 -0200 [thread overview]
Message-ID: <20151119095300.7a296d83@recife.lan> (raw)
In-Reply-To: <20151119101943.GB17128@valkosipuli.retiisi.org.uk>
Em Thu, 19 Nov 2015 12:19:43 +0200
Sakari Ailus <sakari.ailus@iki.fi> escreveu:
> Hi Mauro,
>
> On Thu, Nov 19, 2015 at 07:45:13AM -0200, Mauro Carvalho Chehab wrote:
> > It is possible to use:
> > make DOCBOOKS=device-drivers.xml htmldocs
> >
> > To produce just a few docbooks. In such case, the media docs
> > won't be built, causing the makefile target to return an error.
> >
> > While this is ok for human eyes, if the above is used on an script,
> > it would cause troubles.
> >
> > Fix it by only creating/filling the media_api directory if the
> > media_api.xml is found at DOCBOOKS.
> >
> > Signed-off-by: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
> > ---
> > Documentation/DocBook/media/Makefile | 6 ++++--
> > 1 file changed, 4 insertions(+), 2 deletions(-)
> >
> > diff --git a/Documentation/DocBook/media/Makefile b/Documentation/DocBook/media/Makefile
> > index 02848146fc3a..2840ff483d5a 100644
> > --- a/Documentation/DocBook/media/Makefile
> > +++ b/Documentation/DocBook/media/Makefile
> > @@ -199,8 +199,10 @@ DVB_DOCUMENTED = \
> > #
> >
> > install_media_images = \
> > - $(Q)-mkdir -p $(MEDIA_OBJ_DIR)/media_api; \
> > - cp $(OBJIMGFILES) $(MEDIA_SRC_DIR)/*.svg $(MEDIA_SRC_DIR)/v4l/*.svg $(MEDIA_OBJ_DIR)/media_api
> > + $(Q)if [ "x$(findstring media_api.xml,$(DOCBOOKS))" != "x" ]; then \
> > + mkdir -p $(MEDIA_OBJ_DIR)/media_api; \
> > + cp $(OBJIMGFILES) $(MEDIA_SRC_DIR)/*.svg $(MEDIA_SRC_DIR)/v4l/*.svg $(MEDIA_OBJ_DIR)/media_api; \
> > + fi
> >
> > $(MEDIA_OBJ_DIR)/%: $(MEDIA_SRC_DIR)/%.b64
> > $(Q)base64 -d $< >$@
>
> I'd still copy the files even if the directory was there. It's entirely
> possible that new files appeared between the make runs, or that the existing
> files changed. cp will just overwrite the targets in that case.
>
> Albeit one still has to issue "make cleandocs" to get the DocBook rebuilt.
> Oh well... One thing at a time? :-)
I guess you misread the patch...
It unconditionally copy the files even if the media_api directory exists,
if make is called with:
make htmldocs
or with:
make DOCBOOKS=media_api.xml htmldocs
It will only suppress the copy and dir make if someone wants to build
some other html file, with something like:
make DOCBOOKS=device-drivers.xml htmldocs
Please notice that I use internally a script that detects when a patch
is merged on my tree. In such case, it builds the Kernel and the
documentation, if it is affected, with this logic:
cat Documentation/DocBook/device-drivers.tmpl |perl -ne 'print "$1\n" if (m/^\!I(.*media.*)/)' >$TMPFILE
if [ "`git show $TAG|diffstat -p1 -l|grep -f $TMPFILE`" ]; then
rm $TMPFILE
make DOCBOOKS=device-drivers.xml htmldocs 2>&1|grep /media/
if [ "$?" != "0" ]; then
play ~/sounds/pipe.wav 2>/dev/null >/dev/null
fi
else
rm $TMPFILE
fi
Without this patch, it beeps all the times it runs, because
cp $(OBJIMGFILES) $(MEDIA_SRC_DIR)/*.svg $(MEDIA_SRC_DIR)/v4l/*.svg $(MEDIA_OBJ_DIR)/media_api;
will fail, as no OBJIMGFILES would be produced.
Regards,
Mauro
next prev parent reply other threads:[~2015-11-19 11:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-19 9:45 [PATCH] DocBook: only copy stuff to media_api if media xml is generated Mauro Carvalho Chehab
2015-11-19 10:19 ` Sakari Ailus
2015-11-19 11:53 ` Mauro Carvalho Chehab [this message]
2015-11-19 13:56 ` Sakari Ailus
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=20151119095300.7a296d83@recife.lan \
--to=mchehab@osg.samsung.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=sakari.ailus@iki.fi \
/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