Mateusz Łoskot 96df5442bc Move tests of extensions inside test/ directory (#302) ... 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)		2019-09-26 11:43:13 +02:00
..
CMakeLists.txt	Move tests of extensions inside test/ directory (#302)	2019-09-26 11:43:13 +02:00
main.cpp	Move tests of extensions inside test/ directory (#302)	2019-09-26 11:43:13 +02:00