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
Copy file name to clipboardExpand all lines: README.md
+29-21Lines changed: 29 additions & 21 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -308,45 +308,53 @@ This project uses [CMake](https://cmake.org/) as a build system.
308
308
## Windows
309
309
310
310
### Visual Studio
311
-
Visual Studio has support for CMake since Visual Studio 2017. To open the project, run Visual Studio and under `File > Open > CMake...`
312
-
select the CMakeList.txt from this directory.
311
+
Visual Studio has built-in support for CMake projects. After opening the project, you should be able to select from the presets
312
+
defined in the `CMakePresets.json` file.
313
313
314
-
The CMakeSettings.json in this project should already define both a 32 and 64 bit configuration.
315
-
You can add new configurations in the combo box that contains the x64 config. Here you can change the build type to Release or RelWithDebInfo and duplicate the config
316
-
for a 32 bit build.
314
+
After selecting a preset, Visual Studio should automatically download the required dependencies using vcpkg.
317
315
318
-
To build the project, you can then simply run `` from the toolbar. The output files are placed in the `out/build/{ConfigurationName}/` subfolder
316
+
To build the project, you can then run `Build > Build All` from the toolbar. The output files are placed in the `out/build/{ConfigurationName}/` subfolder
319
317
of this project.
320
318
319
+
The CMakeSettings.json in this project should already define both a 32- and 64-bit configuration.
320
+
You can add new configurations in the combo box that contains the x64 config. Here you can change the build type to Release or RelWithDebInfo and duplicate the config
321
+
for a 32-bit build.
321
322
322
-
### CLion
323
-
Simply open the project in CLion and import the CMake project. Assuming you have a [valid toolchain](https://www.jetbrains.com/help/clion/how-to-create-toolchain-in-clion.html) setup,
324
-
you can simply build the project using `Build > Build Project` in the toolbar.
323
+
To build the project, you can then simply run `Build > Build All` from the toolbar. The output files are placed in the `out/build/{ConfigurationName}/` subfolder
324
+
of this project.
325
325
326
-
To compile for 32 bit rather than 64 bit, you can select a 32 bit VS toolchain, rather than the 64 bit one.
326
+
### CLion
327
+
Before opening the project in CLion, ensure that you have a [valid toolchain](https://www.jetbrains.com/help/clion/how-to-create-toolchain-in-clion.html) set up.
327
328
328
-
The output files are placed within the `cmake-build-debug/` directory of this project.
329
+
After opening the project in CLion, you should get a dialog showing you the available presets.
330
+
Select the preset for 32- or 64-bit (depending on which you want to build) and press the duplicate button.
331
+
Then, in the options for your new preset, select the correct toolchain (again, either 32- or 64-bit) and select to
332
+
explicitly use `Ninja` as the generator.
333
+
After applying and setting it as the active preset, you can build the project using `Build > Build Project` in the toolbar.
329
334
335
+
The output files are placed within the `cmake-build-*-release/` directory of this project.
330
336
331
337
## Linux
332
338
333
-
334
339
### Prerequisites
335
-
To compile the project, you will need CMake and a functioning c++ compiler. For example, under Ubuntu, the following packages
340
+
To compile the project, you will need CMake and a functioning C++ compiler. For example, under Ubuntu, the following packages
0 commit comments