On Sat, Apr 16, 2011 at 1:13 AM, alfC <alfredo.correa@gmail.com> wrote:
On Apr 4, 4:39 pm, Michael Caisse <bo...@objectmodelingdesigns.com> wrote:
Taking a look at the testing Jamfile it looks like the following will do it:
: <define>BOOST_SPIRIT_USE_PHOENIX_V3=1 <define>BOOST_PROTO_MAX_ARITY=11 <define>BOOST_PROTO_MAX_LOGICAL_ARITY=11 <define>BOOST_MPL_LIMIT_METAFUNCTION_ARITY=12
that helped in some cases, in other cases I had to add something like #define BOOST_PHOENIX_COMPOSITE_LIMIT 9 to avoid boost/phoenix/core/limits.hpp:118:5: error: #error "BOOST_RESULT_OF_NUM_ARGS < BOOST_PHOENIX_COMPOSITE_LIMIT + 1"
but I still have problems, for example: In file included from /usr/include/boost/mpl/arithmetic.hpp:23, from /usr/include/boost/units/static_rational.hpp:16, from /usr/include/boost/units/ heterogeneous_system.hpp:34, from /usr/include/boost/units/detail/ conversion_impl.hpp:20, from /usr/include/boost/units/conversion.hpp:17, from /usr/include/boost/units/quantity.hpp:29, from /usr/include/boost/units/systems/si.hpp:19, from ./document.cpp:15: /usr/include/boost/mpl/multiplies.hpp:38: error: wrong number of template arguments (12, should be 5)
Yeah ... the preprocessor limits ... the best is to include boost/phoenix/core/limits.hpp before anything else ... sadly it sometimes depends on the include order ...