I agree, it would be much better if this was picked up at compile time - took a while searching and head scratching before I figured out what the problem was. I found that it was not necessary to define these when building boost, but I'm not 100% sure whether that is necessary, I think that depends on which non-header only library use these macros, perhaps you could do a quick search of the boost directory just to make sure. 2012/2/22 Igor R <boost.lists@gmail.com>
You can get around this by increasing the maximum size a variant can handle, define the following symbols (or higher if you need):
#define BOOST_MPL_LIMIT_LIST_SIZE 30 #define BOOST_MPL_LIMIT_VECTOR_SIZE 30 #define BOOST_MPL_CFG_NO_PREPROCESSED_HEADERS
And one more question: if I define these macros in some TU of my project, in the way that affects some other boost headers I include -- should I define them when building boost as well? _______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users