1

I inherited an old program from a colleague that is no longer with the company. It's an CPLEX optimization we use. It was built in house in C++ using Visual Studio 2005 and CPLEX121. The server where it's located is being decommissioned and we're trying to migrate it to a new server. I'm trying to rebuild the new application in Visual Studio 2013 using CPLEX126 for the optimizations.

Error I get is:

Description:

error LNK2038: mismatch detected for '_MSC_VER': value '1600' doesn't match value '1800' in (project name).obj

File:

ilocplex.lib(ilocplex.obj)

There are quite a few of these mismatches. I'm new to Visual Studio and C++, but I've managed to work through getting the CPLEX links updated, and now this error is happening.

From this forum post: error LNK2038: mismatch detected for '_MSC_VER': value '1600' doesn't match value '1700' in CppFile1.obj

I've been able to deduce there might be something I can do to the toolset or "recompile my libraries" this seemed to work for some people on the last post, but all I need more specific help on how exactly to do that.

No, it's the object files. What the compiler emits. They appear to be inside the .lib file. You'll need to recompile it. – David Heffernan Oct 24 '13 at 20:40

Hi David, iam new to c++ .Iam basically a c# programmmer. Can you please elaborate the comments – user1654136 Oct 24 '13 at 20:43 2

The compiler is telling you to recompile Projectname1.lib with VS2012. – David Heffernan Oct 24 '13 at 20:48

I have no idea what that means and I don't have enough reputation to comment.

Also,

for each project in your solution make sure that Properties > Config. Properties > General > Platform Toolset is one for all of them, v100 for visual studio 2010, v110 for visual studio 2012 you also may be working on v100 from visual studio 2012

the response is "That worked for me"

My Project's Platform Toolset is "Visual Studio 2013 (v120)". Do I need to add some other toolset? there's no other option in the dropdown.

There is also a block of code in the .cpp file:

// set up Visual Studio version #define _VS2005_ # if _MSC_VER < 1400 # undef _VS2005_ # endif

I also don't know what this is doing to see if it is causing the error.

Community
  • 1
  • 1
jstyles3
  • 11
  • 1
  • 1
  • 3
  • Make sure the Platform Toolset is set to v120 for *each* project in the solution, and rebuild everything. If that doesn't fix the error, the problem likely is that you're linking to a library that was compiled using VS2005 (maybe *ilocplex.lib*? I can't tell for sure from the error message). You'll need to recompile the offending library using VS2013. – Praetorian Apr 17 '14 at 20:54
  • How do I recompile a library? I'm new to VS – jstyles3 Apr 17 '14 at 20:58
  • 1
    Download the source code, open the project solution, build all. – Captain Obvlious Apr 17 '14 at 21:02
  • Hopefully there is a project file (.vcproj) associated with that library. In that case, open the project file in VS2013, change Platform Toolset (if the upgrade process doesn't do so for whatever reason) and rebuild the project. If there is no project file, your best bet is to create a new project, add the source files involved to this project and compile it. MSDN should have articles on how to go about doing all this. – Praetorian Apr 17 '14 at 21:02
  • It's when I build that I get the error. – jstyles3 Apr 17 '14 at 21:24

2 Answers2

4

First - you will not be able to recompile the CPLEX library because you will not have the source code and there is no way you are going to get it unless you work in the R&D team inside IBM. So forget that line of reasoning. You are dependent on IBM providing a pre-built library that works with the version of the compiler that you are using.

When you say that you "managed to work through getting the CPLEX links updated, and now this error is happening", I am guessing that you managed to update the paths to the C++ include files that are used by the compiler, so your compilation errors have gone away. But you may not yet have updated the library paths to show the compiler the right sets of libraries to link with.

From the error you are posting, '_MSC_VER': value '1600' doesn't match value '1800', that says to me that you are trying to link with the CPLEX library built for VS2010, while your code was compiled using VS2013. See for example How to Detect if I'm Compiling Code With Visual Studio 2008?

If you are new to C++, it is plain crazy for anyone to expect you to walk into a large existing code base and try to port to new compiler and libs and get it to run straight away without doing a bit more research and background learning. Have you tried to build and run the C++ examples provided with CPLEX?

Have you read the instructions for setting up a C++ project with CPLEX? They are in a file c_cpp.html in the CPLEX folder.

Now, I don't know that CPLEX has libraries for VS2013. I haven't got 12.6 here, so I can't be sure. Have a look in your installed copy of CPLEX, probably something like:

C:\Program Files\IBM\ILOG\CPLEX_Studio126\cplex\lib

...and that should tell you what versions of VS are supported. I have x64_windows_vs2008, x64_windows_vs2010 and x64_windows_vs2012

If there isn't a copy of the library for VS2013, then I think you are going to have to go back to VS2012 or VS2010. There may be a way to configure VS2013 to make it work like VS2012 and trick it onto generating code that is compatible; but I am guessing that would not be a "supported configuration" from IBM's perspective.

The stuff about #define VS2005 is using the C++ pre-processor to define a symbol which can be used to turn on or off bits of your source code. Look for where in your source code that symbol is used. I am guessing that is entirely separate from your linking issue. You might choose to do something similar if you make changes in your code to make it work (or work better) with the newer version of the compiler and libraries.

Community
  • 1
  • 1
TimChippingtonDerrick
  • 2,042
  • 1
  • 12
  • 13
  • we've had a departure of a few individuals in quick succession, so maintenance of current projects has been the priority, not necessarily learning C++ (or C#) or building the knowledge base for these situations has been possible. I just switched the CPLEX links from the x64_windows_VS2010 folder to the x64_windows_VS2012, and now my mismatches are '1700' doesn't match '1800'. looks like this is my problem. I don't have an x64_windows_VS2013 folder installed. I'm going to try to get our guys who control the new server to see if we can get the x64_windows_VS2013 folder installed. Thanks! – jstyles3 Apr 18 '14 at 13:24
  • UPDATE: Got Visual Studio 2012 installed on the new location and am referencing the right libraries, but now i'm getting an error that reads: error LNK2038: mismatch detected for "RuntimeLibrary': value 'MD_DynamicRelease' douesn't match 'MT_StaticRelease' – jstyles3 Apr 24 '14 at 20:19
  • Use the other set of CPLEX libraries. You should have libraries in folders labelled like stat_mda and stat_mta. In general, you can link your compiled C++ code to libraries either statically or dynamically. If you link statically, then effectively copies of the library functions get copied and included directly in your executable. If instead you link dynamically, then what gets linked into your executable instead is a set of references to those functions which then get linked to a DLL at run time. See for example http://stackoverflow.com/questions/7214764/static-vs-dynamic-libraries. – TimChippingtonDerrick Apr 26 '14 at 05:17
  • (continued) When the CPLEX library itself is built, it also needs to link to the standard runtime libraries itself. The different versions that IBM supply are provided to be compatible with how different developers may want to link their own code to the other (standard) runtime libraries. If you want your own code to use dynamic linking to link to the standard runtime libs then it makes sense to use a version of CPLEX (and any other libraries) that work the same way. – TimChippingtonDerrick Apr 26 '14 at 05:23
  • However, I don't see static versions of the CPLEX libs for VS2012 in my copy of 12.5.1, so you may need to change the project settings in VS2012. Read the contents of the IBM-provided file c_cpp.html for detailed instructions on setting up the project, and look at the provided VS2012 example project settings. – TimChippingtonDerrick Apr 26 '14 at 05:28
0

Tim's answer is entirely correct, but here's the piece that he couldn't check...

There doesn't exist CPLEX libraries for VS2013, so you should not spend time looking for some... This can be seen in this report, which you can access for other platforms/versions from the CPLEX Optimization Studio Detailed System Requirements.

This means that you will have to use Visual Studio 2012 compiler. You can still use the Visual Studio 2013 environment: what you have to do is to install both versions and instruct Visual Studio 2013 to use the compiler from version 2012 by changing the Platform Toolset. But all the other libraries that your application uses must then have been compiled by the Visual Studio 2012 compiler. You can't mix and match...

Xavier Nodet
  • 5,033
  • 2
  • 37
  • 48