we used to compile boost regex in boost version 1.36 with the following command:
bjam.exe -sHAVE_ICU=1 -sICU_PATH=../../../../icu -sBOOST_REGEX_RECURSIVE toolset=msvc-7.1 threading=multi python-debugging=on link=shared variant=debug --without-mpi libs\regex\build
When switching to boost 1.38, we realized that BOOST_REGEX_RECURSIVE is not passed/picked up anymore when using the same command (apart compiler version to compile (verified with some added pragma messages):
How should this be configured nowadays? Or did it never work that way but the default behaviour changed? Maybe the user-config.jam file should be used, but I didn't find an example of how to do this.
I'm not sure that ever worked, but in any case: bjam.exe -sICU_PATH=../../../../icu define=BOOST_REGEX_RECURSIVE=1 toolset=msvc-7.1 threading=multi python-debugging=on link=shared variant=debug --without-mpi libs\regex\build Will do what you want (mixing HAVE_ICU with ICU_PATH isn't such a good idea either BTW). Also BOOST_REGEX_RECURSIVE is the default mode for Boost.Regex under vc-7.1 anyway, although that changes for more recent VC++ versions. HTH, John.