96df5442bc
Split header tests accordingly i.e. test core headers as part of
core tests, numeric extension headers as part of numeric tests, etc.
It extends the convention of sub-directories already established in
`include/boost/gil` directory. It is sensible to follow it in other
areas of the source tree (i.e. `test/`, `doc/` and `benchmark/`).
Another important reason to move the tests is to enable removal of
the top-level `Jamfile` with all its definitions of test-specific
requirements.
The top-level `Jamfile` is not advised, especially if it specifies
build requirements like C++ language version.
Those affect non-tests builds e.g. documentation, causing failures
during generation of HTML documentation (leads to missing docs).
(cherry picked from develop branch commit 4ed7701b47)
20 lines
553 B
C++
20 lines
553 B
C++
//
|
|
// Copyright (c) 2018 Mateusz Loskot <mateusz@loskot.net>
|
|
// Copyright (c) 2007-2015 Andrey Semashev
|
|
//
|
|
// Distributed under the Boost Software License, Version 1.0. (See
|
|
// accompanying file LICENSE_1_0.txt or copy at
|
|
// http://www.boost.org/LICENSE_1_0.txt)
|
|
|
|
// This file contains a test boilerplate for checking that every public header
|
|
// is self-contained and does not have any missing #include-s.
|
|
|
|
#define BOOST_GIL_TEST_INCLUDE_HEADER() <boost/gil/BOOST_GIL_TEST_HEADER>
|
|
|
|
#include BOOST_GIL_TEST_INCLUDE_HEADER()
|
|
|
|
int main()
|
|
{
|
|
return 0;
|
|
}
|