[Ipopt] Help with IPOPT linking problems on Windows MSVC

[Jesse Perla]

> Maybe you need to build also a debug version of the vcf2c.lib. You would
> need to change some -MT to -MTd somewhere in the makefile.vc.

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.


>I could try making binaries of Ipopt in optimized (-MT) and debug mode
>(-MTd) using the new Mumps and the Netlib LAPACK/BLAS, and having
>everything compiled with Intel C++ and Fortran compilers. Would that be
>helpful?

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.

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.

(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)

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.

-Jesse
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://list.coin-or.org/pipermail/ipopt/attachments/20080828/2266a421/attachment.html