Michcol94
Active Member
- Joined
- Sep 2, 2021
- Messages
- 159
- Solutions
- 2
- Reaction score
- 30
A bug happened!
copilot
otclient.vcxproj
1. Abseil:x64-windows-static installation error in buildtrees/abseil/x64-windows-static-dbg
Symptoms
When attempting to install abseil:x64-windows-static, an error occurs:
`CMake Error at scripts/cmake/vcpkg_execute_build_process.cmake:134 (message):
Command failed: .../cmake.exe --build . --config Debug --target install -- -v -j25
Working Directory: .../vcpkg/buildtrees/abseil/x64-windows-static-dbg
See logs for more information:
.../buildtrees/abseil/install-x64-windows-static-dbg-out.log
.../buildtrees/abseil/install-x64-windows-static-dbg-err.log
CMake Error at cmake_install.cmake:76 (file):
file INSTALL cannot find ".../buildtrees/abseil/x64-windows-static-dbg/options-pinned.h": File exists.
FAILED: CMakeFiles/install.util
ninja: build stopped: subcommand failed.
`
2. MSB4011 Warning about multiple vcpkg.targets file imports
Symptoms
When building a project in Visual Studio, a warning similar to the one below appears:
3. Błędy konfiguracji toolchaina CMake z vcpkg
Objawy
Błędy/ostrzeżenia w stylu:
when i open otclient local folder in visual studio:
chatgpt
While building the project, you can see that CMake failed to find C/C++ compilers – the messages are: "CMAKE_C_COMPILER not set, after EnableLanguage" and "CMAKE_CXX_COMPILER not set, after EnableLanguage"
github.com
. In practice, these errors appear because an earlier step of installing dependencies via vcpkg failed. The logs indicate that the Abseil package (Google's large CPP library) needed by OTClient failed to build. Specifically, the Abseil configuration report shows the error:
This means that the Abseil build attempted to build tests that depend on GoogleTest (gmock), but the library was not found. This is a known issue with the vcpkg port of Abseil – building the static Abseil library requires disabling tests or manually adding GoogleTest, which is not supported by default.
copilot
otclient.vcxproj
1. Abseil:x64-windows-static installation error in buildtrees/abseil/x64-windows-static-dbg
Symptoms
When attempting to install abseil:x64-windows-static, an error occurs:
`CMake Error at scripts/cmake/vcpkg_execute_build_process.cmake:134 (message):
Command failed: .../cmake.exe --build . --config Debug --target install -- -v -j25
Working Directory: .../vcpkg/buildtrees/abseil/x64-windows-static-dbg
See logs for more information:
.../buildtrees/abseil/install-x64-windows-static-dbg-out.log
.../buildtrees/abseil/install-x64-windows-static-dbg-err.log
CMake Error at cmake_install.cmake:76 (file):
file INSTALL cannot find ".../buildtrees/abseil/x64-windows-static-dbg/options-pinned.h": File exists.
FAILED: CMakeFiles/install.util
ninja: build stopped: subcommand failed.
`
2. MSB4011 Warning about multiple vcpkg.targets file imports
Symptoms
When building a project in Visual Studio, a warning similar to the one below appears:
warning MSB4011: "C:\Users\<username>\AppData\Local\vcpkg\vcpkg.user.props(3,3): warning MSB4011: "D:\vcpkg\scripts\buildsystems\msbuild\vcpkg.props" cannot be imported again. It was already imported at "D:\MyApp\Directory.Build.props". This is most likely a build authoring error. This subsequent import will be ignored.3. Błędy konfiguracji toolchaina CMake z vcpkg
Objawy
Błędy/ostrzeżenia w stylu:
- Nieznalezienie narzędzi (Compiler not found, Visual Studio toolchain not found)
- Kompilator nie wspiera wersji C++ wymaganej przez OtClient (np. CMAKE_CXX_STANDARD 20)
- Błędny triplet, np. x64-windows vs. x64-windows-static
- CMake nie odnajduje odpowiedniej instancji vcpkg, pojawiają się błędy z narzędziem lub ścieżką
when i open otclient local folder in visual studio:
chatgpt
While building the project, you can see that CMake failed to find C/C++ compilers – the messages are: "CMAKE_C_COMPILER not set, after EnableLanguage" and "CMAKE_CXX_COMPILER not set, after EnableLanguage"
github.com
. In practice, these errors appear because an earlier step of installing dependencies via vcpkg failed. The logs indicate that the Abseil package (Google's large CPP library) needed by OTClient failed to build. Specifically, the Abseil configuration report shows the error:
The link interface of target ‘test_allocator’ contains: GTest::gmock but the target was not foundThis means that the Abseil build attempted to build tests that depend on GoogleTest (gmock), but the library was not found. This is a known issue with the vcpkg port of Abseil – building the static Abseil library requires disabling tests or manually adding GoogleTest, which is not supported by default.