Emil Dotchevski wrote:
This ought to be part of all Boost testing, provided that the Boost community cares about -fno-rtti (I can say this the other way around too, if we're not testing the no-RTTI configuration of Boost, then we don't care about that configuration.)
In reality, the total number of build combinations far exceeds anyone's ability to test them all. Possible attributes are wchar exits or not rtti exists or not dynamic vs static C++ runtime dynamic vs static library version debug vs release optimisations platform supports throw or not version of STL being used (stlport, built in or ?) I'm sure there a lot more. However you look at it, the number of possible combinations is too large to test them all a head of time. What is really needed is a way for customers (whoops users) a) install the system b) run the tests on the libraries he plans to use with the attributes/options he wants. a) is addressed via the bjam install. b) b could be addressed just be upgrading the documentation on how to do this. My prefered method of doing this is described in the library status/test description. I don't know if there is anyway to find this through the boost documention page. Users should be encourged to run the tests when they install and report any issues. This should be part of the installation procedure. Robert Ramey