So it's not compiler agnostic and hence is unportable...
I have used some libraries on Windows and never encountered that error. Thus we can probably assume some libraries have it on, some have it off and others don't care.In other normal libraries it turned ON - but in Qt it turned OFF. So when I link another libraries with Qt Applications - linker writes errors.
Many people successfully use Boost with Qt so I don't think it's a common problem. Sometimes you just need to rebuild something (be it Qt or any other lib) because the default options are not satisfactory. Is it that much of a problem?Try to link boost with Qt Application for example - and you got link errors!!!!!
Bookmarks