I need help compiling on new machine targeting older machine

[Michael Sherwin]

I have MSVC 2005. For 64 bit compiles the target machine is set to x64 and for 32 bit compiles the target is x86. I started from a fresh project and did not change any parameters. The problem is that on my Q6600 with Windows 7 I get a side by side configuration error on starting my engine. I see nowhere in MSVC 2005 where the hardware MSVC is running on makes a difference to the code produced. Can anyone help? This is not just for me. There are others having this problem trying to run the new version of RomiChess. Thanks

[jdart]

Why on earth are you using MSVC 2005 (maybe you mean 2015)?

Visual Studio Community Edition 2017 is available and free:

https://www.visualstudio.com/vs/community/

It supports cross-compilation (for example, x32 target on x64 host). If you want to build a Windows-NT compatible binary, though, there are some additional steps needed.

--Jon

[Michael Sherwin]

Always worked great until now! But why should it matter? My Q6600 executables run just fine on both computers. But compiles on my i7 won't run on my Q6600. The settings are exactly the same. The code produced should be exactly the same. But obviously the code is not exactly the same. And I want to know why. However, I'll update to the newer version. Or at least try. The last time I updated it was to MSVC 2013 and I could not get my code to compile properly in MSVC 2013.

[Michael Sherwin]

At least I found out why. A dynamic link library in windows 10 that MSVC 2005 links to is not backward compatible with windows 7 or vista. However the dll in 7 and vista is forward compatible with 10, lol. Would installing MSVC 2017 fix that issue? Idk.

[brianr]

Suggest looking at static linking...

[Michael Sherwin]

Suggest looking at static linking...

I tried that. Now it will run on the Q6600w7 and crashes. So I downloaded MSVC 2017. It seems MSVC 2017 no longer supports unnamed structures. Romi's whole data structure is built upon unnamed structures. I love unnamed structures! It lets me write something.d instead of something.a.b.c.d. I'll just make my final compiles on the Q6600 and continue to use MSVC 2005.