thalium / icebox

Virtual Machine Introspection, Tracing & Debugging
MIT License
567 stars 86 forks source link

virtualbox compile error #22

Closed eix128 closed 4 years ago

eix128 commented 4 years ago

D:\repo\icebox\third_party\virtualbox>cscript configure.vbs --with-MinGW-w64=D:/Tools/msys64/mingw64 --with-libSDL=%SDL_LIB% --with-openssl=%OPENSSL_DIR% --with-openssl32=%OPENSSL32_DIR% --with-qt5=%QT_DIR%/qtbase --with-python=c:/Python38 --with-libcurl=%CURL_DIR%/builds/libcurl-vc10-x64-release-dll-ipv6-sspi-winssl --with-libcurl32=%CURL_DIR%/builds/libcurl-vc10-x86-release-dll-ipv6-sspi-winssl Microsoft (R) Windows Script Host Version 5.812 Copyright (C) Microsoft Corporation. All rights reserved.

Shell inheritance test: OK Source path: OK Checking for kBuild... Target architecture: amd64. Host architecture: amd64. Found kBuild: D:/repo/icebox/third_party/virtualbox/kBuild Found kBuild binaries: D:/repo/icebox/third_party/virtualbox/kBuild/bin/win.x86 Checking for Windows DDK v7.1... Found Windows DDK v7.1: D:/Tools/WinDDK/7600.16385.1 Checking for Visual C++... error: Executing '' (which we believe to be the Visual C++ compiler driver) failed.

But someone said how to fix the issue: https://forums.virtualbox.org/viewtopic.php?f=10&t=84382

This problem is caused by LANGUAGE difference of Visual C++ Compiler.

I'm a Chinese, so the compiler info is written by Chinese , but the configure.vbs uses English text info to check the compiler version.

What I've done is that I edited the configure.vbs in LINE 1067

if (InStr(1, gstrShellOutput, "编译器 16.") <= 0) And (InStr(1, g_strShellOutput, "编译器 17.") <= 0) then 'MsgError "The Visual C++ compiler we found ('" & strPathVC & "') isn't 10.0 or 11.0. Check the build requirements." MsgError "g_strShellOutput is " & g_strShellOutput exit sub end if

' ' Ok, emit build config variables. ' if InStr(1, g_strShellOutput, "编译器 16.") > 0 then CfgPrint "PATH_TOOL_VCC100 := " & g_strPathVCC


In Chinese, "编译器" means compiler, after this alter, I have successfully passes the compiler check.

bamiaux commented 4 years ago

Thanks for creating the issue, you need to report it back upstream to VirtualBox. Once fixed & released, we will synchronize back with this new VirtualBox version.