Every thing should go right into a “CMakeLists.txt”, whether or not you add the .cpp/.h to the basis CMakeLists file, otherwise you break it up and add CMakeLists.txt to sub-directories, and reference them from the basis one, it’s solely as much as you.
When you make any modifications to CMakeLists.txt, you will need to do considered one of two issues, both re-run the cmake command in a console window to re-create the Visible Studio answer and challenge recordsdata, or proper click on the “ZERO_CHECK” challenge and construct that (which ought to do the identical factor as operating the cmake command through the CLI). If for any motive you get errors, then likelihood is you’ve up to date one thing that requires you to delete the [build_folder]/CMakeCache.txt file, after which re-do one of many above steps.
Android Studio doesn’t require you to manually run cmake, because it handles that activity mechanically inside the IDE whenever you do a gradle sync.
For Xcode, it’s the identical course of as Home windows, the place you manually must run the cmake command to recreate the challenge recordsdata on any modifications to “CMakeLists.txt”.
To save lots of myself time, I simply created a batch file and put it within the root listing of my challenge, and after I must, I merely run it to re-run cmake and refresh the construct folder.
For instance, to create a Visible studio 2019 (x86/Win32) answer in a listing named “build-win32”:
IF EXIST .build-win32 GOTO RUNCMAKE
mkdir build-win32
:RUNCMAKE
cmake -S . -B build-win32 -G "Visible Studio 16 2019" -Tv142 -A Win32
For Visible Studio 2022, you are able to do this:
IF EXIST .build-win32 GOTO RUNCMAKE
mkdir build-win32
:RUNCMAKE
cmake -S . -B build-win32 -G "Visible Studio 17 2022" -A Win32
When you put the above code in one thing like “vs-run-cmake.bat” or related, drop that file in your challenge folder. Simply run this file any time you make modifications to “CMakeLists.txt” to refresh the VS answer recordsdata.
