|
Boost : |
Subject: Re: [boost] [gil][test] HOWTO set up the Boost testing process for projects with extra prerequisites ?
From: Steven Watanabe (watanabesj_at_[hidden])
Date: 2017-11-17 16:42:49
AMDG
On 11/17/2017 09:29 AM, Stefan Seefeld via Boost wrote:
>
> I just merged some work to GIL's `develop` branch. This notably involves
> improvements to the testing infrastructure. Testing GIL is a bit
> involved, as it requires various backend libraries (PNG, JPEG, TIFF,
> etc.) to be installed. While the stand-alone testing works fine
> (https://github.com/boostorg/gil/blob/develop/.travis.yml#L304-L306),
> the integrated testing will thus fail, until the testing logic is
> augmented by the necessary instructions to a) install the prerequisites
> and b) invoke the build system with the appropriate flags
> (https://github.com/boostorg/gil/blob/develop/io/test/Jamfile#L13-L22)
>
Please use the Boost.Build modules for these libraries
instead. You can make the tests run only when the
corresponding libraries are available, like this:
using zlib ;
run png_test.cpp
: # args
: # input-files
: # requirements
[ ac.check-library /zlib//zlib : <library>/zlib//zlib : <build>no ]
# in English, if the library is found, use it, otherwise,
# skip this test
;
> Thus my question: do we have any documentation that explains how to do
> this ? What do I (as GIL maintainer) or any testers need to do for the
> integrated testing to work ?
>
> (I can't resist: all these libraries that have special requirements
> really shouldn't be built and tested in such a monolithic process. It's
> a burden to all tester, maintainers, and packagers. It would be far
> better to handle them more independently.)
>
In Christ,
Steven Watanabe
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk