From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Xen-devel <xen-devel@lists.xen.org>
Cc: Wei Liu <wei.liu2@citrix.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
Ian Campbell <Ian.Campbell@citrix.com>
Subject: Re: [PATCH v2 6/7] docs/build: Move install checks into individual build targets
Date: Tue, 21 Apr 2015 16:50:37 +0100 [thread overview]
Message-ID: <553671CD.3060307@citrix.com> (raw)
In-Reply-To: <1429631225-19956-1-git-send-email-andrew.cooper3@citrix.com>
On 21/04/15 16:47, Andrew Cooper wrote:
> For top-level targets which use more than a single program to produce content
> (txt already, pdf once pandoc is supported), these current checks are
> unsuitable.
>
> By moving the the install checks to the rules which actually use the programs,
> it is now possible to build a subset of a top-level target depending on the
> installed programs.
>
> As a bonus, it removes the need to recurse for txt, man-pages and pdf targets.
>
> A side effect of this is that every individual source which cannot be
> generated will have a specific message logged, giving the file and program.
> As such, these message are updated to consistently report the target file
> which was not generated.
>
> Finally, update "ifdef foo" to "ifneq($(foo),)" to be more resilient to errors
> caused by having foo defined as an empty string.
>
> Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
>
Alternatively, the entire v2 series can be obtained from
git://xenbits.xen.org/people/andrewcoop/xen.git docs-cleanup-v2
~Andrew
next prev parent reply other threads:[~2015-04-21 15:50 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-20 10:49 [PATCH 0/7] docs/build fixes Andrew Cooper
2015-04-20 10:49 ` [PATCH 1/7] docs/build: Misc cleanup Andrew Cooper
2015-04-21 14:08 ` Ian Campbell
2015-04-20 10:49 ` [PATCH 2/7] docs/build: Do not open-code $* Andrew Cooper
2015-04-20 11:48 ` Jan Beulich
2015-04-20 11:55 ` Andrew Cooper
2015-04-20 12:13 ` Jan Beulich
2015-04-21 14:10 ` Ian Campbell
2015-04-20 10:49 ` [PATCH 3/7] docs/build: Move two rules for consistency, and comment sections Andrew Cooper
2015-04-21 14:11 ` Ian Campbell
2015-04-20 10:49 ` [PATCH 4/7] docs/build: Do not use move-if-changed Andrew Cooper
2015-04-21 14:12 ` Ian Campbell
2015-04-21 15:00 ` Andrew Cooper
2015-04-21 15:03 ` Ian Campbell
2015-04-20 10:49 ` [PATCH 5/7] docs/build: Do not create directories if we are not going to use them Andrew Cooper
2015-04-21 14:13 ` Ian Campbell
2015-04-20 10:49 ` [PATCH 6/7] docs/build: Move install checks into individual build targets Andrew Cooper
2015-04-20 11:57 ` Jan Beulich
2015-04-20 12:01 ` Andrew Cooper
2015-04-21 14:15 ` Ian Campbell
2015-04-21 14:18 ` Jan Beulich
2015-04-21 14:23 ` Ian Campbell
2015-04-21 14:55 ` Andrew Cooper
2015-04-21 15:47 ` [PATCH v2 " Andrew Cooper
2015-04-21 15:50 ` Andrew Cooper [this message]
2015-04-21 15:47 ` [PATCH v2 7/7] docs/build: Support generation of pandoc documents Andrew Cooper
2015-04-20 10:49 ` [PATCH " Andrew Cooper
2015-04-21 14:15 ` Ian Campbell
2015-04-22 14:22 ` [PATCH 0/7] docs/build fixes 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=553671CD.3060307@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=wei.liu2@citrix.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.