You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Invoke cmake -G Ninja -DCMAKE_TOOLCHAIN_FILE={where your vcpkg clone is located}\scripts\buildsystems\vcpkg.cmake -S . -B {wherever you want binaries} to configure the project. For example, cmake -G Ninja -DCMAKE_TOOLCHAIN_FILE=C:\Dev\vcpkg\scripts\buildsystems\vcpkg.cmake -S . -B out\build\x64
appears several paragraphs above the instructions of how to run tests. If Python 3.8 is not already installed when the configuration step is completed, it is likely that the user will need to reconfigure in order for CMake to be able to find the correct Python executable. It would be good to mention that possibility following the "Acquire Python..." step.
The text was updated successfully, but these errors were encountered:
That seems like a viable option. In that case, I think we should also update step 1 of How To Build With A Native Tools Command Prompt to include installing Python 3.8 along with CMake, Ninja, and VS 2019.
In How To Run The Tests With A Native Tools Command Prompt, step 3 says
However, the configuring step (step 10 in How To Build With A Native Tools Command Prompt) which says
appears several paragraphs above the instructions of how to run tests. If Python 3.8 is not already installed when the configuration step is completed, it is likely that the user will need to reconfigure in order for CMake to be able to find the correct Python executable. It would be good to mention that possibility following the "Acquire Python..." step.
The text was updated successfully, but these errors were encountered: