On Monday 06 October 2014 16:29:07 Mathias Gaunard wrote:
On 06/10/14 15:48, Adam Wulkiewicz wrote:
Boost sublibrary/sublib Correct me if I'm wrong. To allow dividing libraries into smaller functional parts (SVN) "sublibs" system was introduced. With it it's possible to keep the tests and examples separated for each part. In the library there must be a correct directories structure and there must exist a file called "sublibs", see (geometry, numeric, functional, etc.). Then you can see separated sublibs e.g. on the regression summary page: http://www.boost.org/development/tests/develop/developer/summary.html
This is what I was looking for.
Unfortunately, it seems it's only usable to divide tests, examples and documentation, and not headers, sources or usage requirements.
[snip]
What I would want, however, is
BOOST_ROOT/libs +-library_name +-sublib_name1
| +-include | | | +-boost | | | | | +-sublib_name1 | | | | | | | +-... | | +-test | | | +-Jamfile.v2 | | +-example | +-build | | | +-Jamfile.v2 | | +-src
+-sublib_name2
| +-include | | | +-boost | | | | | +-sublib_name2 | | | | | | | +-... | | +-test | | | +-Jamfile.v2 | | +-example | +-build | | | +-Jamfile.v2 | | +-src
+-(file)sublibs
AFAIK, a sublib can contain everything - headers, sources, docs and tests (see libs/numeric for example). I didn't try the sources and build/Jamfile.v2 in a sublib though.
Each sublibtest dir should be added to the BOOST_ROOT/status/Jamfile.v2 to run the tests for all submodules.
That's a bit tedious. Shouldn't this be automatically computed?
It'd be great if it did but currently it's not.