VC7 + STLPort (and other assorted questions)
Is there any way to force boost to build using VC7 and STLPort? I tried the obvious (settings TOOLS=msvc-stlport, and setting MSVC_DIR=<path to VC7>), but I got a ton of compiler errors that way. I ask because VC6 + STLPort 4.5.3 has some serious issues with the the VC6 compiler, causing internal compiler errors (very bad :P). Also, I keep hearing mention of a way to build the boost libs from inside the VC IDE (and the ability to build them for static linking), but I can't find project files, or a Jam option to build static. What am I missing? This is all Boost 1.28.0. Matt Holmes
"juxtaposenj" <matt@kerion.net> wrote in message news:aea7qs+hr3n@eGroups.com...
Is there any way to force boost to build using VC7 and STLPort? I tried the obvious (settings TOOLS=msvc-stlport, and setting MSVC_DIR=<path to VC7>), but I got a ton of compiler errors that way.
I think you just need to follow directions more carefully. No toolset responds to MSVC_DIR. See http://www.boost.org/tools/build/msvc-tools.html#configuration and http://www.boost.org/tools/build/msvc-stlport-tools.html One other suggestion: Try starting with just the msvc toolset, to make sure you have the configuration for that right. Then, if you want to use msvc-stlport, add the additional configuration for that. -Dave
The syntax I am using for accessing object members is really very obtuse: struct X {int i; }; vector<X> vec_X; ... std::sort(vec_X.begin(), vec_X.end(), &_1->*&X::i < &_2->*&X::i ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^ This must be a worthwhile basis for an entry into the obsfucated c++ context! Is the syntax required because the . operator cannot be overloaded? Leo
participants (2)
-
boost -
David Abrahams -
juxtaposenj