<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN"> <HTML> <HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8"> <META NAME="GENERATOR" CONTENT="GtkHTML/3.26.0"> </HEAD> <BODY> On Mon, 2010-09-13 at 12:16 -0700, Jeremy Huddleston wrote: <BLOCKQUOTE TYPE=CITE> <TT>So --disable-docs in this case means nothing is installed?</TT> </BLOCKQUOTE> That's the general idea of this XORG_ENABLE_DOCS. Each module can decide of the exact meaning of what constitute a "document". For xorg-docs, the MAINTAINERS file may be installed anyway. This macro was born in the context of using the doc toolchain, like groff, xmlto, doxygen, ps2pdf, fop and the likes. A builder could disable all documentation in one go rather than inspecting which tool is used and turn off the tools. A builder can turn off an individual tool  if it is known to be present but broken. There is a lot of flexibility now. I wish I can find a way to document this. <BLOCKQUOTE> <PRE> --enable-docs    Enable building the documentation (default: yes) </PRE> </BLOCKQUOTE> There 3 broad categories of documents: "doc", "specs" and "devel-docs" which have corresponding macros: <BLOCKQUOTE> <PRE> XORG_ENABLE_DOCS XORG_ENABLE_SPECS XORG_ENABLE_DEVEL_DOCS </PRE> </BLOCKQUOTE> Typically devel-docs are not installed. For a complete list, see wiki <A HREF="http://www.x.org/wiki/Development/Documentation/WritingDocumentation">http://www.x.org/wiki/Development/Documentation/WritingDocumentation</A> Some accept a minimum version number: <BLOCKQUOTE> <PRE> XORG_WITH_XMLTO(0.0.20) </PRE> </BLOCKQUOTE> Gaetan </BODY> </HTML>