做个游戏

> What does > > > If I mannul set the path from D:\Cloned\wesnoth\vcpkg_installed\vcpkg\pkgs\ , it will work > > mean? setting the path like this-> set(OPENSSL_ROOT_DIR "D:\Cloned\wesnoth\vcpkg_installed\vcpkg\pkgs\openssl_x64-windows")

> Probably because you're not using the arguments to tell cmake where vcpkg is building the dependencies, like CI does: > > https://github.com/wesnoth/wesnoth/blob/837e50a3e2e3733c256b60bf9d0a8bf6d8031e83/.github/workflows/ci-main.yml#L321-L325 Do I need change this 'C:\vcpkg\scripts\buildsystems\vcpkg.cmake' path...

> I don't know, the expected way to use this is via Visual Studio. I am using VS, but I can't build with it

> I don't know, the expected way to use this is via Visual Studio. I really need a video tutorial for this

> Maybe @Vultraz can help you (I'm on Linux), but you should just need to open the repository folder in VS and click the Build button. I just found out...

> Run it from a terminal with `--no-log-to-file` and check the output. I don't think there is this option: 20240829 14:55:47 error server: unknown option: --no-log-to-file

> It shouldn’t matter if you’re using built in vcpkg or not, honestly. Wesnoth doesn’t use global vcpkg packages (that method is discouraged). Instead, it builds and installs them with...

> As Vultraz mentioned, the way Wesnoth is currently set-up does not depend on what you have installed for stand-alone vcpkg. I remember I had some trouble with initial set-up...

I tried cloning and starting from the beginning. After opening the folder in VS, CMake encountered an error with find_package, and I noticed that vcpkg hadn't downloaded the dependencies yet....

> Show the exact error. CMake Error at C:/Program Files/Microsoft Visual Studio/2022/Community/Common7/IDE/CommonExtensions/Microsoft/CMake/CMake/share/cmake-3.28/Modules/FindPackageHandleStandardArgs.cmake:230 (message): Could NOT find OpenSSL, try to set the path to OpenSSL root folder in the system variable...