11 Mar
2018
11 Mar
'18
3:29 p.m.
Daniel James wrote:
It isn't good that we only find these errors in release candidates. Is it possible for the testers to do a binary build before running the tests?
That's what check_build does:
http://www.boost.org/development/tests/master/developer/check_build.html
That's useful, although perhaps a bit obscure. Ideally we want to build the libraries exactly as the user does. If there's a problem with the super project's jamfiles would that catch it?
No, it wouldn't. We do have a Travis job that builds the libraries exactly as the user does, but that's only for one specific configuration (gcc/cxxstd=11). So if the superproject Jamfiles are broken on f.ex. msvc-12.0, none of these will catch it. It's still better than nothing though.