forked from boostorg/utility
9d1284ef6d8f51ac15b6f9de44cadc11a38bdbf4
This partly re-applies 5ae025b56a with the
following changes:
- Use path-constant to deduce the path relative to the point of execution
rather than the Jamfile.
- Use that path only to list source files to be passed to Doxygen.
- Keep the project rule, but remove the duplicate requirements that are
explicitly specified in standalone_main.
Hopefully, this should work around the problem of Reference generation
in the official docs.
Boost.Utility, part of collection of the Boost C++ Libraries, provides a number of smaller components, too small to be called libraries in their own right. See the documentation for the list of components.
Directories
- doc - Documentation sources
- include - Interface headers of Boost.Utility
- test - Boost.Utility unit tests
More information
- Documentation
- Report bugs. Be sure to mention Boost version, Boost.Utility component, platform and compiler you're using. A small compilable code sample to reproduce the problem is always good as well.
- Submit your patches as pull requests against develop branch. Note that by submitting patches you agree to license your modifications under the Boost Software License, Version 1.0.
Build status
| Branch | GitHub Actions | AppVeyor | Test Matrix | Dependencies |
|---|---|---|---|---|
master |
||||
develop |
License
Distributed under the Boost Software License, Version 1.0.
Description
Languages
C++
90.2%
HTML
9.6%
CMake
0.2%
