Jump to content

  • Log In with Google      Sign In   
  • Create Account


#ActualServant of the Lord

Posted 15 June 2013 - 04:07 PM

The library compile settings (32 bit or 64 bit, compiler name mangling, what underlying exception-handling method, debug mode or release mode, single-threaded or multi-threaded, etc...) need to match the executable that is linking to the library. This is why it's almost always easier to download the library source, and compile the library with the same compiler and settings that you compile your executable, so you can be confident that it lines up. Ofcourse, some libraries are a pain to compile. laugh.png

 

If you downloaded a 64 bit version of the library, but you are accidentally compiling a 32 bit executable, then there will probably be a conflict.


#2Servant of the Lord

Posted 15 June 2013 - 04:05 PM

The library compile settings (32 bit or 64 bit, compiler, debug mode or release mode, single-threaded or multi-threaded, etc...) need to match the executable that is linking to the library.

If you downloaded a 64 bit version of the library, but you are accidentally compiling a 32 bit executable, then there will probably be a conflict.


#1Servant of the Lord

Posted 15 June 2013 - 04:05 PM

The library compile settings (32 bit or 64 bit, compiler, debug more or release mode, single-threaded or multi-threaded, etc...) need to match the executable that is linking to the library.

If you downloaded a 64 bit version of the library, but you are accidentally compiling a 32 bit executable, then there will probably be a conflict.


PARTNERS