[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH v2 6/7] docs/build: Move install checks into individual build targets



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@xxxxxxxxxx>
>

Alternatively, the entire v2 series can be obtained from

git://xenbits.xen.org/people/andrewcoop/xen.git docs-cleanup-v2

~Andrew

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.