[cairo] [PATCH v2 3/3] README : Update README file related to usage of FORMAT make variable
Bryce Harrington
bryce at osg.samsung.com
Thu Aug 14 16:16:55 PDT 2014
On Wed, Aug 06, 2014 at 09:49:59AM +0530, Ravi Nanjundappa wrote:
> Reformatted the README file to simplify the sentences.
>
> Signed-off-by: Ravi Nanjundappa <nravi.n at samsung.com>
Merged after fixing trailing whitespace.
> ---
> test/README | 17 ++++++++++++-----
> 1 file changed, 12 insertions(+), 5 deletions(-)
>
> diff --git a/test/README b/test/README
> index e8e7189..8b60ce2 100644
> --- a/test/README
> +++ b/test/README
> @@ -41,14 +41,21 @@ There are some mechanisms to limit the tests run during "make test".
> These come very handy when doing development, but should not be used
> to circumvent the "pass" requirements listed below.
>
> -To limit the backends that the tests are run against, use the
> -TARGETS make variable, that can also be passed to make.
> -It should contain a (space-, comma-, etc-separated) list of backends to test.
> -To limit the tests run, use the CAIRO_TESTS environment variable, which
> -should be a space-separated list of tests to run. For example:
> +make's TARGETS environment variable can be used to limit the backends when
> +running the tests. It should contain a (space-, comma-separated) list of
> +backends. CAIRO_TESTS environment variable, which is a comma-, space-seperated
> +lists, can be used to limit the tests run.
> +For example:
>
> CAIRO_TESTS="zero-alpha" make test TARGETS=image,ps
>
> +make's FORMAT variable can also be used to limit the content formats when
> +running the tests. It should contain a (space-, comma-separated) list of
> +content formats to test.
> +For example:
> +
> + CAIRO_TESTS="zero-alpha" make test TARGETS=image,ps FORMAT="rgb,rgba"
> +
> Another very handy mechanism when trying to fix bugs is:
>
> make retest
> --
> 1.7.9.5
>
> --
> cairo mailing list
> cairo at cairographics.org
> http://lists.cairographics.org/mailman/listinfo/cairo
More information about the cairo
mailing list