[Scip] Question on using 3.0.0 in windows

Fri Oct 19 14:29:08 MEST 2012

Hello Michael:

Thanks for the information. This was useful.

I believe I found what the problem with the DLL (or .exe) is. The distribution archive (scip-3.0.0.win.x86.vc10.opt.spx.lib.zip) has a DLL: scip-3.0.0.win.x86.vc10.opt.spx.dll). However, Windows is attempting to load the same DLL with the name: scip-3.0.0.win.x86.vc10.opt.spx.mt.exe. The way to deal with that is to actually rename the distributed DLL to that name and that takes care of it. This is unusual since it should have been built with the appropriate name (as DLL not .exe) from the beginning, but the simple rename is enough. This may be useful to some of the other Windows users, or maybe you can fix the build to take care of this automatically for the next release (as already is in 2.1.1).

Thanks for your help.

Guillermo

From: Michael Winkler [mailto:michael.winkler at zib.de]
Sent: Thursday, October 18, 2012 8:55 AM
To: Guillermo Irisarri
Cc: Stefan Heinz; Scip at zib.de
Subject: Re: Question on using 3.0.0 in windows

Hi Guillermo,

there are still some problems using methods which are only defines in OPT mode. This is a windows library problem and will hopefully be fixed with the next release.

But if you are writing your code in C/C++, you should include the SCIP header files in your code and compile with the -DNDEBUG flag. Then methods like SCIPinfinity() should be replace by the preprocessor. (Btw. DBL_MAX is not a good infinity, SCIPs standard infinity is 1e20)

The second error I do not understand, running an executable leads to not finding another executable. There I have no clue.

To your third point, can you please check what the retcode is, that SCIPcreate() is returning, which lead to the execption?

Best, Michael

Am 18.10.2012 15:05, schrieb Guillermo Irisarri:

Hello Michael/Stefan:

I wonder whether you had the opportunity to look at my question from a previous email:

In the meantime, I have a question about the usage if SCIP 3.0.0 in Windows (32) systems. I tried the new binary and could not make it work. 1) The linker found an unresolved reference for SCIPinfinity. I replaced that by DBL_MAX for the time being to get through that part, 2.) When running the application Windows complains about not finding the "scip-3.0.0.win.x86.vc10.opt.spx.mt.exe", which is strange since this is the SCIP interactive application. I put that in the path, anyway, 3) The application started and failed with an exception in the first call to SCIP_CALL_EXC(SCIPcreate(&scip)).

I did not see these problems with the scip-2.1.1 where the only thing I needed was the DLL scip-2.1.1.win.x86.vc10.opt.spx.dll (and the corresponding library). Is there something else needed besides the DLL/Lib?

I have tried various ways around the issues and have not been able to find a solution.

First, using SCIPinfinity gives an undefined external. For instance with the Queens problem as a test, and from Microsoft VS 10:

1>------ Build started: Project: Queens, Configuration: Debug Win32 ------

1>Build started 10/18/2012 7:48:48 AM.

1>InitializeBuildStatus:

1>  Creating "Debug\Queens.unsuccessfulbuild" because "AlwaysCreate" was specified.

1>ClCompile:

1>  All outputs are up-to-date.

1>  Queens.cpp

1>ManifestResourceCompile:

1>  All outputs are up-to-date.

1>Queens.obj : error LNK2001: unresolved external symbol _SCIPinfinity

1>F:\ Queens\Debug\Queens.exe : fatal error LNK1120: 1 unresolved externals

1>

1>Build FAILED.

1>

1>Time Elapsed 00:00:03.23

========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========

This can be overcome (temporarily at least) replacing SCIPinfinity with DBL_MAX or something like that (just to be able to continue the debug). However, after a successful build and when starting the execution I get:

[cid:image001.png at 01CDADCB.6D185550]

I have the DLL in place. It is strange that it is asking for the .exe which is the SCIP shell.

If I put the executable along with the DLL it starts but then fails with:

[cid:image002.png at 01CDADCB.6D185550]

When trying to execute: SCIP_CALL_EXC( SCIPcreate(& _scip) );

I don't see why the .exe is needed since the DLL should be all that is required (same as 2.1.1) I wonder if I am doing something unusual or if there are other people with the same issues in Windows systems.

If you have a chance, please let me know.

Thanks

Guillermo

-----Original Message-----
From: Guillermo Irisarri
Sent: Friday, October 12, 2012 7:20 AM
To: 'michael.winkler at zib.de<mailto:michael.winkler at zib.de>'
Cc: Stefan Heinz; Scip at zib.de<mailto:Scip at zib.de>
Subject: RE: [Scip] Quick question on how to get infesibility info from presolver or after solve returns infeasible

Hello Michael:

Thank you very much for your answer. I will try the MinUC suggestion.

In the meantime, I have a question about the usage if SCIP 3.0.0 in Windows (32) systems. I tried the new binary and could not make it work. 1) The linker found an unresolved reference for SCIPinfinity. I replaced that by DBL_MAX for the time being to get through that part, 2) When running the application Windows complains about not finding the "scip-3.0.0.win.x86.vc10.opt.spx.mt.exe", which is strange since this is the SCIP interactive application. I put that in the path, anyway, 3) The application started and failed with an exception in the first call to SCIP_CALL_EXC(SCIPcreate(&scip)).

I did not see these problems with the scip-2.1.1 where the only thing I needed was the DLL scip-2.1.1.win.x86.vc10.opt.spx.dll (and the corresponding library). Is there something else needed besides the DLL/Lib?

I appreciate it very much if you let me know what may be happening here.

Thanks

Guillermo

-----
Open Access Technology International, Inc.
e-mail: Guillermo.Irisarri at oati.net<mailto:P at oati.net>
3660 Technology Drive NE
Minneapolis, MN 55418
CONFIDENTIAL INFORMATION:  This email and any attachment(s) contain confidential and/or proprietary information of Open Access Technology International, Inc.  Do not copy or distribute without the prior written consent of OATI.  If you are not a named recipient to the message, please notify the sender immediately and do not retain the message in any form, printed or electronic.
-----

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://listserv.zib.de/mailman/private/scip/attachments/20121019/46555d2a/attachment.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 8317 bytes
Desc: image001.png
Url : http://listserv.zib.de/mailman/private/scip/attachments/20121019/46555d2a/image001.png
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 8832 bytes
Desc: image002.png
Url : http://listserv.zib.de/mailman/private/scip/attachments/20121019/46555d2a/image002.png