Bug 5929 - Files not cleaned when configured with --disable-docs
Summary: Files not cleaned when configured with --disable-docs
Status: RESOLVED FIXED
Alias: None
Product: cairomm
Classification: Unclassified
Component: Build (show other bugs)
Version: CVS HEAD
Hardware: All All
: high minor
Assignee: Murray Cumming
QA Contact:
URL:
Whiteboard:
Keywords: janitor, patch
Depends on:
Blocks:
 
Reported: 2006-02-18 01:46 UTC by Danilo Piazzalunga
Modified: 2006-02-17 07:18 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
Output files in docs subdir only if --enable-docs is set (1.06 KB, patch)
2006-02-18 01:50 UTC, Danilo Piazzalunga
Details | Splinter Review

Description Danilo Piazzalunga 2006-02-18 01:46:36 UTC
Some files generated at configure time are not cleaned when ./configure is
called with --disable-docs. These files are:

  docs/Makefile
  docs/reference/Makefile
  docs/reference/Doxyfile

The solution is to list these files in a separate AC_CONFIG_FILES directive
which gets called only when enable_docs=yes.
Comment 1 Danilo Piazzalunga 2006-02-18 01:50:25 UTC
Created attachment 4647 [details] [review]
Output files in docs subdir only if --enable-docs is set

This patch also contains another minor change: it splits the (deprecated)
AC_OUTPUT(files) call into two separate calls: AC_CONFIG_FILES(files) and
AC_OUTPUT() without arguments.

This is the recommended usage for AC_OUTPUT and it is exactly what autoconf
does automatically, so this alone doesn't change the generated configure at
all.
Comment 2 Jonathon Jongsma 2006-02-18 02:18:25 UTC
committed to CVS.  thanks

2006-02-17  Danilo Piazzalunga  <danilopiazza@gmail.com>

	* configure.in: Bug #5929: Output files in docs subdir only if
	--enable-docs is set.  This prevents configure from generating files which
	are not cleaned up when --disable-docs is used.
	Use AC_CONFIG_FILES and AC_OUTPUT as recommended.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.