There is an API change in unit_test_log_formatter from Boost.Test.
Details
boost::unit_test::unit_test_log_formatter::log_build_info now expects a second argument.
Motivation and Context
There is now a preprocessor define to support building also with Boost.Test from 1.70.
How Has This Been Tested?
Manual build with Boost 1.71. There's no package for Boost >= for trusty (as used on travis).
Types of changes
[x] Bug fix (non-breaking change which fixes an issue).
Checklist:
[x] It is my own work, its copyright is implicitly assigned to the project and no substantial part of it has been copied from other sources (including Stack Overflow). In rare occasions this is acceptable, like in CMake modules where the original copyright information should be kept.
[x] I'm using the same code standards as the existing code (indentation, spacing, variable naming, ...).
[ ] I've added tests for my code.
[x] I have verified whether my change requires changes to the documentation
[x] My change either requires no documentation change or I've updated the documentation accordingly.
[x] My branch has been rebased to master, keeping only relevant commits.
Coverage remained the same at 62.47% when pulling 3af03a8f65affe72ca9099d924bee8ab88e64c16 on LukasWoodtli:BoostTestApiChange into dd424c1a900cb41c5db9d481714eb3471ce195e3 on cucumber:master.
Summary
There is an API change in
unit_test_log_formatter
from Boost.Test.Details
boost::unit_test::unit_test_log_formatter::log_build_info
now expects a second argument.Motivation and Context
There is now a preprocessor define to support building also with Boost.Test from 1.70.
How Has This Been Tested?
Manual build with Boost 1.71. There's no package for Boost >= for trusty (as used on travis).
Types of changes
Checklist: