title: Building a correctly linked executable to avoid error 0xc000007b
body: <p>I am building a 32-bit executable with VS 2012's default build settings. It works correctly on one 64-bit computer (development machine); on another 64-bit computer, the program crashes with error 0xc000007b. </p>
  
  <p>A bit of study and using a dependency walker indicates the problem is that the executable is loading 64-bit dlls rather than 32-bit dlls.</p>
  
  <p>I am reasonably sure that this is solvable by configuring the build to statically link required code rather than calling out to the DLLs.</p>
  
  <p>1). Is this solution a reasonably correct and portable solution?</p>
  
  <p>2). How do I configure VS 2012 to link statically as above?</p>
  
  <p>N.b: this is a C++ native program.</p>