<div dir="ltr">> Maybe you need to build also a debug version of the vcf2c.lib. You would<br>> need to change some -MT to -MTd somewhere in the <a href="http://makefile.vc/" target="_blank">makefile.vc</a>.<br><br>Yeah, that is what I thought, but I couldn't figure out what was going on. When I added it to the flags I don't think it did anything, but I probably did it wrong.<br>
<br>
<br>>I could try making binaries of Ipopt in optimized (-MT) and debug mode<br>>(-MTd) using the new Mumps and the Netlib LAPACK/BLAS, and having<br>>everything compiled with Intel C++ and Fortran compilers. Would that be<br>
>helpful?<br><br>That would be great, if we can get a visual studio sample app that has the right combination of linker settings to go with it. Also, I am not entirely sure how the threading stuff works, but if the runtime libraries are different for the -MD and -MDd (the multithreaded dll builds which seems to be the default with new projects), that might be necessary. And probably it makes sense to link in the blas/lapack separately to your projects since many would be using MKL with other libraries (e.g. boost::ublas) and would run into big conflicts. Mumps could be linked in to the library without problem for me at least, though I see no issues with for me at least.<br>
<br>I am on vacation until next week, but can test things out/pass you on my project files I had for the visual studio sample app after that.<br><br>(and I am also eagerly awaiting the discussion on the linux with the intel tool suite, MKL. That will be my next step in a few months)<br>
<br>Last, is there any move on Ipopt towards a cross-platform build environment with ipopt or COIN-OR in general? I am trying to decide between boost::build, cmake, and scons right now and would love to hook your packages in or keep things consistent where possible.<br>
<br>-Jesse<br></div>