Alright, I recompiled boost with runtime-link=static but I got the same error.
>> After doing this, I guess there is some "magic" preprocessor define
you need to specify in your project, so the boost config header
becomes aware of what boost variant you are using...
I have looked for some sort of preprocessor definition for static builds, but I couldn't seem to find any. Does anyone happen to know what this is/could be?
>> I believe the only exception to this is Boost.Python, but that has special
requirements that make static linking much more tricky I believe.
I actually am linking to Boost.Python, and Boost.Filesystem (both really nice libraries). However I probably should have said earlier, but I receive 2 "Mixing a dll boost library with a
static runtime is a really bad idea..." errors. I assume 1 is for python and the other for filesystem?
Any help is appreciated, I really need these to be statically linked.