6232f719a5
Now that we use a CMakePresets.json file for CI, it makes sense to support users having their own presets in a CMakeUserPresets.json file. From CMake documentation: > CMakePresets.json may be checked into a version control system, and > CMakeUserPresets.json should NOT be checked in. For example, if a > project is using Git, CMakePresets.json may be tracked, and > CMakeUserPresets.json should be added to the .gitignore.
46 lines
403 B
Plaintext
46 lines
403 B
Plaintext
# Prerequisites
|
|
*.d
|
|
|
|
# Compiled Object files
|
|
*.slo
|
|
*.lo
|
|
*.o
|
|
*.obj
|
|
|
|
# Precompiled Headers
|
|
*.gch
|
|
*.pch
|
|
|
|
# Compiled Dynamic libraries
|
|
*.so
|
|
*.dylib
|
|
*.dll
|
|
|
|
# Fortran module files
|
|
*.mod
|
|
*.smod
|
|
|
|
# Compiled Static libraries
|
|
*.lai
|
|
*.la
|
|
*.a
|
|
*.lib
|
|
|
|
# Executables
|
|
*.exe
|
|
*.out
|
|
*.app
|
|
|
|
# Build folders
|
|
build/
|
|
cmake-build-*/
|
|
|
|
# Cache/IDE folders
|
|
.cache/
|
|
.vscode/
|
|
.idea/
|
|
.vs/
|
|
|
|
# User configuration
|
|
CMakeUserPresets.json
|