Thanks for your response Andrey. I have the following libraries in my STLport/lib directory: stlport_static.lib stlportd.5.2.lib stlportd_static.lib stlportstld.5.2.lib stlportstld_static.lib stlport.5.2.lib These are simply the libraries that are generated by following the build instructions for STLport, I didn't rename or move anything. I assumed that Boost should be easily able to make assumptions about where to find things if I don't modify them. Do you see any issues with the libs here? Are there perhaps some options missing from my command line invocation? --------- Robert Dailey On Fri, Feb 10, 2012 at 9:08 AM, Andrey Semashev <andrey.semashev@gmail.com>wrote:
On Friday, February 10, 2012 08:54:32 Robert Dailey wrote:
I've provided a lot of details here, and based on the instructions I've found (none of which are on the official boost website!), this seems to be the correct path and the build system should "just work". Can someone help me figure this out?
Just an idea of where the problem might be. STLPort supports two versions of debug builds - a traditional debug build (which should be binary compatible with release builds, IIRC) and a debug build with additional checking, enabled by defining _STLP_DEBUG macro. From your errors it looks like the compiler tries to find the latter one (the one with stlportstld in its name). Maybe you're trying to link with the other version (stlportd) or the compiler simply can't find the correct library.
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost