Is there a way to change _ITERATOR_DEBUG_LEVEL=2 to =0 when compiling the libmongocxx on Windows (visual studio 14)

[William Bouchard]

Hello,

As I said in the subject I'm looking for a way to change the _ITERATOR_DEBUG_LEVEL from 2 to 0 in the static version of libmongocxx and libbsoncxx.

The reason is I'm using this lib in Unreal Engine 4 and I'm getting this kind of error:

 Error libbsoncxx.lib : error LNK2038: mismatch detected for '_ITERATOR_DEBUG_LEVEL': value '2' doesn't match value '0' in SharedPCH.Engine.h.obj

 Error libmongocxx.lib : error LNK2038: mismatch detected for '_ITERATOR_DEBUG_LEVEL': value '2' doesn't match value '0' in SharedPCH.Engine.h.obj

Is there a way to do that?

[Sam Rossi]

Hi William! I think this is a Visual Studio setting, not a driver configuration. From looking at other instances where people have had the same problem, it looks the debug level is set to 2 for debug builds and 0 for release builds. Is it possible you compiled libmongocxx and libbsoncxxx is a different mode (debug vs. release) than your own application?

[William Bouchard]

Thank you for your answer.

 It seems that even if I compile the mongocxx and bsoncxx static libs in Release mode via CMake, the debug level is set to 2, while in my project, the debug level is set to 0.

[Sam Rossi]

Just to make sure, you've compiled libbson and libmongoc in release mode as well?

[William Bouchard]

Hi,

Sorry for my time away, I'm back on this problem.

So, you were right, I was compiling libbson and libmongoc in Debug mode instead of Release.

That did correct the error, but I got some new ones.

I got more than 2000 error like this one : error LNK2001: unresolved external symbol __imp_mongoc_read_prefs_new

exactly like in this subject: https://groups.google.com/d/msg/mongodb-user/iUaqAMScXMM/vGGMXoqWDQAJ.

I tried with the mongo-c-driver version 1.7 and 1.6.3, but it changes nothing.

Maybe you have an idea ?

Thanks for helping :)

[Sam Rossi]

Hi William,

As discussed in the thread you linked to, this is a bug that will be fixed in the mongoc 1.7.0 release, which is currently in RC. For testing purposes, you can try using the latest mongoc RC (along with the master branch of mongocxxx rather than 3.1.x), but for use in production, you'll need to dynamically link until both mongoc 1.7.0 and mongocxx 3.2.0 are released.

[William Bouchard]

Okey, thank you for your help.