From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Ian Campbell <ian.campbell@citrix.com>
Cc: "Fioravante, Matthew E." <Matthew.Fioravante@jhuapl.edu>,
Matt Wilson <msw@amazon.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH 4/4] docs: check for documentation generation tools in docs/configure.
Date: Fri, 18 Jan 2013 17:12:58 +0100 [thread overview]
Message-ID: <50F9748A.6000906@citrix.com> (raw)
In-Reply-To: <1358519140-20052-4-git-send-email-ian.campbell@citrix.com>
On 18/01/13 15:25, Ian Campbell wrote:
> It is sometimes hard to discover all the optional tools that should be
> on a system to build all available Xen documentation. By checking for
> documentation generation tools at ./configure time and displaying a
> warning, Xen packagers will more easily learn about new optional build
> dependencies, like markdown, when they are introduced.
>
> Based on a patch by Matt Wilson. Changed to use a separate
> docs/configure which is called from the top-level in the same manner
> as stubdoms.
>
> Rerun autogen.sh and "git add docs/configure" after applying this patch.
>
> Signed-off-by: Matt Wilson <msw@amazon.com>
> Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
> Acked-by: Matt Wilson <msw@amazon.com>
> (For the change to introduce docs/configure)
> Cc: "Fioravante, Matthew E." <Matthew.Fioravante@jhuapl.edu>
> Cc: Roger Pau Monné <roger.pau@citrix.com>
> ---
> Applies on top of Matthew's "Add autoconf to stubdom" and "Add a top
> level configure script".
>
> v2: - LATEX2HTML is unused
> - No more XenAPI or Doxygen or associated tools.
> ---
> @@ -69,6 +75,7 @@ clean:
>
> .PHONY: distclean
> distclean: clean
> + rm -rf ../config/Docs.mk config.log config.status autom4te.cache
By looking at the distclean target from tools, don't you need to remove
config.cache also?
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2013-01-18 16:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-18 14:25 [PATCH 0/4] install into /usr/local and docs/configure Ian Campbell
2013-01-18 14:25 ` [PATCH 1/4] tools: install under /usr/local by default Ian Campbell
2013-01-18 15:19 ` Roger Pau Monné
2013-01-18 15:35 ` Ian Campbell
2013-01-20 23:57 ` Matt Wilson
2013-01-18 14:25 ` [PATCH 2/4] docs: Remove xen-api docs Ian Campbell
2013-01-18 14:25 ` [PATCH 3/4] docs: drop doxygen stuff Ian Campbell
2013-01-18 14:25 ` [PATCH 4/4] docs: check for documentation generation tools in docs/configure Ian Campbell
2013-01-18 16:12 ` Roger Pau Monné [this message]
2013-01-18 16:44 ` Ian Campbell
2013-01-18 17:46 ` Roger Pau Monné
2013-01-21 9:32 ` Ian Campbell
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=50F9748A.6000906@citrix.com \
--to=roger.pau@citrix.com \
--cc=Matthew.Fioravante@jhuapl.edu \
--cc=ian.campbell@citrix.com \
--cc=msw@amazon.com \
--cc=xen-devel@lists.xen.org \
/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;
as well as URLs for NNTP newsgroup(s).