Configuration fails on Windows 11 (VS Community 2022; could not find git for clone of googletest-populate

[MGM175]

Like in title. Attempted to run the compilation script as prescribed in README, but in the end, the error occurs. I'm attaching a dump from my terminal if it could help.

-- Running vcpkg install
Detecting compiler hash for triplet x64-windows...
All requested packages are currently installed.
Total install time: 300 ns
The package boost is compatible with built-in CMake targets:

find_package(Boost REQUIRED [COMPONENTS <libs>...])
target_link_libraries(main PRIVATE Boost::boost Boost::<lib1> Boost::<lib2> ...)

The package zlib is compatible with built-in CMake targets:

find_package(ZLIB REQUIRED)
target_link_libraries(main PRIVATE ZLIB::ZLIB)

The package openssl is compatible with built-in CMake targets:

find_package(OpenSSL REQUIRED)
target_link_libraries(main PRIVATE OpenSSL::SSL OpenSSL::Crypto)

expat provides CMake targets:

# this is heuristically generated, and may not be correct
find_package(expat CONFIG REQUIRED)
target_link_libraries(main PRIVATE expat::expat)

The package freeglut is compatible with built-in CMake targets:

find_package(GLUT REQUIRED)
target_link_libraries(main PRIVATE GLUT::GLUT)

The package libjpeg-turbo is compatible with built-in CMake targets:

find_package(JPEG REQUIRED)
target_link_libraries(main PRIVATE ${JPEG_LIBRARIES})
target_include_directories(main PRIVATE ${JPEG_INCLUDE_DIR})

libpng provides CMake targets:

# this is heuristically generated, and may not be correct
find_package(libpng CONFIG REQUIRED)
target_link_libraries(main PRIVATE png)

libvorbis provides CMake targets:

# this is heuristically generated, and may not be correct
find_package(Vorbis CONFIG REQUIRED)
target_link_libraries(main PRIVATE Vorbis::vorbis Vorbis::vorbisenc Vorbis::vorbisfile)

The package openal-soft provides CMake targets:

find_package(OpenAL CONFIG REQUIRED)
target_link_libraries(main PRIVATE OpenAL::OpenAL)

opengl-registry is header-only and can be used from CMake via:

find_path(OPENGL_REGISTRY_INCLUDE_DIRS "GL/glcorearb.h")
target_include_directories(main PRIVATE ${OPENGL_REGISTRY_INCLUDE_DIRS})

sdl2 provides CMake targets:

# this is heuristically generated, and may not be correct
find_package(SDL2 CONFIG REQUIRED)
target_link_libraries(main PRIVATE SDL2::SDL2 SDL2::SDL2main)

-- Running vcpkg install - done
-- Found Boost: C:/Users/spyde/source/repos/Vega-Strike-Engine-Source/build/vcpkg_installed/x64-windows/include (found version "1.77.0")
-- Found Boost: C:/Users/spyde/source/repos/Vega-Strike-Engine-Source/build/vcpkg_installed/x64-windows/include (found version "1.77.0") found components: python310 log log_setup date_time system filesystem thread chrono atomic regex
-- Found Vorbis: C:/Users/spyde/source/repos/Vega-Strike-Engine-Source/build/vcpkg_installed/x64-windows/lib/vorbis.lib;C:/Users/spyde/source/repos/Vega-Strike-Engine-Source/build/vcpkg_installed/x64-windows/lib/vorbisfile.lib;C:/Users/spyde/source/repos/Vega-Strike-Engine-Source/build/vcpkg_installed/x64-windows/lib/ogg.lib
-- Configuring incomplete, errors occurred!
Wersja programu MSBuild 17.7.2+d6990bcfa dla .NET Framework
MSBUILD : error MSB1009: plik projektu nie istnieje.
Przełącznik: ALL_BUILD.vcxproj

Directory: C:\Users\spyde\source\repos\Vega-Strike-Engine-Source

Mode LastWriteTime Length Name

---

d----- 05.11.2023 10:26 bin
0 File(s) copied
0 File(s) copied

[BenjamenMeyer]

@MGM175 are you using our master or the 0.8.x release? 0.8.x might not compile so well (kind of works, but not officially supported for that release); master should be mostly there but there is still potential for issues. Windows support is a work in progress and we hope to have it mostly ironed out for our next 0.9.x release.

[stephengtuggy]

@MGM175 do you have Git for Windows installed?

[MGM175]

Yes, 2.42.0.windows.2.

[stephengtuggy]

Hmm. Interesting. And is Git in your path? (Just double-checking.)

[MGM175]

Yes, it is.
PATH=(...);C:\Program Files\Git\cmd;(...)

@MGM175 are you using our master or the 0.8.x release? 0.8.x might not compile so well (kind of works, but not officially supported for that release); master should be mostly there but there is still potential for issues. Windows support is a work in progress and we hope to have it mostly ironed out for our next 0.9.x release.

Yes, it was 0.8.0. Perhaps I'll try with newest build then.

[BenjamenMeyer]

@MGM175 you should have more success on current master; still won't be perfect but should get a lot further more repeatably. Any help with getting it working well would be appreciated to as it's something we need for our next release.

[MGM175]

Sorry for not responding after so long time, but after reinstalling VS 2022 Community Edition, adding Classic Desktop C++ programs set + Git for Windws, along with 114 dependencies on the newer machine for a 1.5 hours of total time. In the end, the compilation ends with:

CMake Error at CMakeLists.txt:120 (PROJECT):
  Generator

    Visual Studio 16 2019

  could not find any instance of Visual Studio.



-- Configuring incomplete, errors occurred!
CMake Error:
  Generator

    Visual Studio 16 2019

  could not find any instance of Visual Studio.

I'll try to modify build.ps1 to force VS 2022.

UPDATE: modification was successful, yet the proper VS 2022 run ended with this output:

Preset CMake variables:

  CMAKE_BUILD_TYPE="Release"
  CMAKE_TOOLCHAIN_FILE:FILEPATH="C:\Program Files\Microsoft Visual Studio\2022\Community\VC\vcpkg/scripts/buildsystems/vcpkg.cmake"
  ENABLE_PIE:BOOL="FALSE"
  VCPKG_HOST_TRIPLET="x64-windows-win10"
  VCPKG_TARGET_TRIPLET="x64-windows-win10"

Preset environment variables:

  VCPKG_HOST_TRIPLET="x64-windows-win10"
  VCPKG_TARGET_TRIPLET="x64-windows-win10"

-- CMAKE_SOURCE_DIR = C:/vegastrike/engine
-- GIT_ROOT_DIR = C:/vegastrike/engine/..
-- Running vcpkg install
Fetching registry information from https://github.com/microsoft/vcpkg (HEAD)...
boost-assign does not exist
boost-atomic does not exist
boost-chrono does not exist
boost-date-time does not exist
boost-filesystem does not exist
boost-format does not exist
boost-iostreams does not exist
boost-log does not exist
boost-python does not exist
boost-system does not exist
boost-thread does not exist
egl-registry does not exist
expat does not exist
freeglut does not exist
libjpeg-turbo does not exist
libpng does not exist
libvorbis does not exist
openal-soft does not exist
opengl does not exist
openssl does not exist
sdl1 does not exist
sdl2 does not exist
zlib does not exist
-- Running vcpkg install - failed
CMake Error at C:/Program Files/Microsoft Visual Studio/2022/Community/VC/vcpkg/scripts/buildsystems/vcpkg.cmake:899 (message):
  vcpkg install failed.  See logs for more information:
  C:\vegastrike\build\VS2022Win64-pie-disabled-release\vcpkg-manifest-install.log
Call Stack (most recent call first):
  C:/Program Files/Microsoft Visual Studio/2022/Community/Common7/IDE/CommonExtensions/Microsoft/CMake/CMake/share/cmake-3.29/Modules/CMakeDetermineSystem.cmake:146 (include)
  CMakeLists.txt:120 (PROJECT)


-- Configuring incomplete, errors occurred!
Change Dir: 'C:/vegastrike/build/VS2022Win64-pie-disabled-release'

Run Build Command(s): "C:/Program Files/Microsoft Visual Studio/2022/Community/MSBuild/Current/Bin/amd64/MSBuild.exe" ALL_BUILD.vcxproj /p:Configuration=Release /p:Platform=X64 /p:VisualStudioVersion=17.0 /v:n
Wersja programu MSBuild 17.11.9+a69bbaaf5 dla .NET Framework
MSBUILD : error MSB1009: plik projektu nie istnieje.
Przełącznik: ALL_BUILD.vcxproj



    Directory: C:\vegastrike


Mode                 LastWriteTime         Length Name
----                 -------------         ------ ----
d-----        02.10.2024     15:18                bin
VERBOSE: Performing the operation "Copy File" on target "Item: C:\vegastrike\build\VS2022Win64-pie-disabled-release\CMakeCache.txt Destination: C:\vegastrike\bin\CMakeCache.txt".
VERBOSE: Performing the operation "Copy File" on target "Item: C:\vegastrike\build\VS2022Win64-pie-disabled-release\vcpkg-manifest-install.log Destination: C:\vegastrike\bin\vcpkg-manifest-install.log".

Below here is the CMakeCache from above's run.
CMakeCache.txt
Now I'm cleaning out everything, since I'm running out of space.

[BenjamenMeyer]

@MGM175 if you have all the dependencies installed, then try going into the source and doing the following:

> mkdir build
> cd build
build > cmake ../engine

and see what that gives you. You could also specify -G to cmake and specify the VS 2022 as the generator; but you'll need to run cmake to see what the list of generators you have are.

Based on your second comment, it looks like it isn't finding the dependencies for some reason; which may also be why our own Windows CI stuff is failing if something changed in the dependency system for Windows. I'm presently trying to figure it out via the GitHub Actions as I don't use Windows myself.