[Ipopt] Help with IPOPT linking problems on Windows MSVC/Intel C++

[Stefan Vigerske]

Hi,

> Based on Damien's suggestion I tried different permutations of nodefaultlib
> to no avail.  I am taking one last crack at linking to this in a debug build
> before getting into the building world (release is working sufficiently for
> now I believe)
>  * I changed the /Code Generation/Runtime Library to Multi-threaded Debug
> (/MTd)  from the default dll version
>  * I link to just libipopt.lib (adding in others didn't seem to help).

I lost track already. How was that one build, multithreaded or 
multithreaded-debug?

> If anyone has any last minute suggestions on a permuation, I would love to
> give it a shot.  Otherwise, do you suggest I try to make the windows
> binaries with Visual Studio or MingGW instructions?  Which do you think is
> easier to get working for building the 4 permutations of builds
> (debug/release and multithreaded/multithreaded-dll)?  Also, do you expect
> that I will have trouble with the multi-threaded dll build?  I am using /MDd
> for my other libraries and am worried I may run into the opposite problem
> changing those over.

If possible, then you should have all libraries build with the same 
flag, that is all debug, or all multithreaded-dll, or whatever...
If you build Ipopt with Visual Studio and wanna use MUMPS, then I don't 
know how VS will know how to compile this Fortran90 package.
When you follow the MinGW instruction, you can overwrite compiler flags 
(CFLAGS, CXXFLAGS, FFLAGS) to make sure that they all use the same 
-MT/-MTd/... flags. It should be correct already for the default build 
(=-MT), but for the debug build I'm not sure.

Stefan