public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: linux-kbuild@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH?] docbook: make cleandocs
Date: Fri, 10 Apr 2009 22:49:30 +0200	[thread overview]
Message-ID: <20090410204930.GA26185@uranus.ravnborg.org> (raw)
In-Reply-To: <20090410133538.fa2b9798.randy.dunlap@oracle.com>

On Fri, Apr 10, 2009 at 01:35:38PM -0700, Randy Dunlap wrote:
> Hi Sam,
> 
> "make clean" cleans DocBook generated files, but I would like a way to
> clean _only_ those generated files.  Something like the patch below,
> except that it doesn't work.  :(
> 
> Can you give me ideas of how to fix it, please?
> 
> Thanks,
> ---
> ~Randy
> 
> 
> 
> 
> From: Randy Dunlap <randy.dunlap@oracle.com>
> 
> Add a 'make cleandocs' target to clean up all generated
> DocBook files.
> 
> Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
> ---
>  Documentation/DocBook/Makefile |   15 ++++++++++++---
>  1 file changed, 12 insertions(+), 3 deletions(-)
> 
> --- linux-2.6.30-rc1-git3.orig/Documentation/DocBook/Makefile
> +++ linux-2.6.30-rc1-git3/Documentation/DocBook/Makefile
> @@ -31,7 +31,7 @@ PS_METHOD	= $(prefer-db2x)
>  
>  ###
>  # The targets that may be used.
> -PHONY += xmldocs sgmldocs psdocs pdfdocs htmldocs mandocs installmandocs
> +PHONY += xmldocs sgmldocs psdocs pdfdocs htmldocs mandocs installmandocs cleandocs
>  
>  BOOKS := $(addprefix $(obj)/,$(DOCBOOKS))
>  xmldocs: $(BOOKS)
> @@ -213,11 +213,12 @@ silent_gen_xml = :
>  dochelp:
>  	@echo  ' Linux kernel internal documentation in different formats:'
>  	@echo  '  htmldocs        - HTML'
> -	@echo  '  installmandocs  - install man pages generated by mandocs'
> -	@echo  '  mandocs         - man pages'
>  	@echo  '  pdfdocs         - PDF'
>  	@echo  '  psdocs          - Postscript'
>  	@echo  '  xmldocs         - XML DocBook'
> +	@echo  '  mandocs         - man pages'
> +	@echo  '  installmandocs  - install man pages generated by mandocs'
> +	@echo  '  cleandocs       - clean all generated DocBook files'
>  
>  ###
>  # Temporary files left by various tools
> @@ -235,6 +236,14 @@ clean-files := $(DOCBOOKS) \
>  
>  clean-dirs := $(patsubst %.xml,%,$(DOCBOOKS)) man
>  
> +cleandocs:
> +	echo "clean-files: $(clean-files)"
> +	echo "clean-dirs: $(clean-dirs)"
> +	cd Documentation/DocBook
> +	rm -f $(clean-files)
> +	rm -rf $(clean-dirs)
> +	cd ../..

Each command are executed in their own shell.
So the "cd Documentation/DocBook" will have no effect.
You need to do something like:

	cd Documentation/DocBook && rm -f $(clean-files) && rm -rf $(clean-dirs)

Or the one I would prefer:

	rm -f $(call objectify, $(clean-files))
	rm -rf $(call objectify, $(clean-dirs))


In the command section of the above rule.

	Sam

  reply	other threads:[~2009-04-10 20:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-10 20:35 [PATCH?] docbook: make cleandocs Randy Dunlap
2009-04-10 20:49 ` Sam Ravnborg [this message]
2009-04-10 21:20   ` [PATCH v2] " Randy Dunlap
2009-04-10 22:42     ` Sam Ravnborg

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=20090410204930.GA26185@uranus.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=randy.dunlap@oracle.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