Open TheElementalOfDestruction opened 4 years ago
Hi. We are able to build RetDec on Windows via MS Visual Studio (see e.g. this AppVeyor build and this TeamCity build), so RetDec should be buildable under Windows and MS Visual Studio.
That being said, I have taken a look at the output you have provided (thank you for it!). Here are my remarks:
18>C:\devkitPro\msys2\usr\include\sys/_types.h(94): error C2144: syntax error: '__int64' should be preceded by ';' [C:\Users\Creat
ion\Downloads\git\retdec-vs\build\src\crypto\retdec-crypto.vcxproj]
It seems that your MSYS2 header files are somehow used instead of Visual Studio's headers. This leads me to believe that there is something wrong with your installation of either Visual Studio or MSYS2.
"C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\CommonExtensions\Microsoft\CMake\CMake\bin\cmake.exe"
but you force CMake to generate solutions for Visual Studio 2015:
-G"Visual Studio 14 2015 Win64"
Is there a reason for that?
"C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\CommonExtensions\Microsoft\CMake\CMake\bin\cmake.exe"
We have no experience with that. Would it be possible for you to install standalone CMake and use that instead?
I actually was able to compile it fine on a different machine, so that machine is the problem.
As for the specific version of compiler, I jus used what was stated in the install instructions. Also, I'm having trouble either with the most recent edition of the compiler (the llvm2hll or whatever is giving me "out of memory" errors even though I tell it to have no maximum and it has a 200gb paging file that it has used in the past) or with changing the mode to debug. There is also the fact that in my test build I quadrupled the stack size. Any one of those could be the problem. It's the same file from my most recent error report involving a stack overflow. One version of the program using the older compiler add default build settings will give me stack overflow while this version tries to load the config and throws an out of memory error. I'm going to be looking into this further to isolate the issue to one (or perhaps it is only the combination of them) change, and I'll get back to you on that.
Unfortunately it takes me around a couple hours to run a full compilation, so this may take some time.
Okay, can confirm that the compiler is NOT a problem.
Also, @s3rvac, can I recommend that we increase the default windows stack size, at least temporarily given the amount of stack space errors?
We can increase the default stack size on Windows (we actually already do that, see the /STACK
argument in src/llvmir2hlltool/CMakeLists.txt
). However, the question is how much. I have seen cases when a decompilation needed even 100 MB of stack space, but I am not sure if having such a big stack by default is advisable.
Platform: Windows 10 method: visual studio cmake
Commands I am using:
Output of commands (when I ran them the second time):