src/Release).įor generators which don’t support multi-configuration builds in one build directory, you’ll have to make multiple build directories for each build type. If in Ninja, GNU make and so on, your example_exe will be located in /src/, in Visual Studio it will be localted in /src// (e.g.
#Chai3d cmake linux dependencies how to
It’s actually a bit more complex, but it’s okay to think about it as “include” at the beginning.įor example, if you have an examples directory, it’s good to have a examples/CMakeLists.txt which will just be a bunch of add_subdirectory calls for each sub-directory and example/some_example/CMakeLists.txt will be a build script which contains information on how to build some_example.Ĭmake -build. I’ve seen a lot of people getting VERSION from a current Git tag or some changelog file, but we’ll not go here in this tutorial.Īdd_subdirectory() is like an “include” and can be thought of as an inclusion of /CMakeLists.txt into another CMake file. It can be used to generate “version” headers (here’s an example of how to do it), write some output in a terminal and so on. VERSION option specifies a current version of your project. If you’re doing C or C++ project, it’s optional to specify it, but it’s still useful as a “meta-data” for people who’re reading your CMake build.
By default it’s C and CXX, but there are a lot of other options available for you (like CUDA or Fortran). LANGUAGES option in a project call defines a language which your project uses so that CMake knows what kind of builds to generate. it can run unit tests, linters and so on).
The target can be an executable, a library or even something which doesn’t produce any files after it’s built (e.g. One project can have multiple “targets” (which roughly correspond to “projects” in VS). The project is similar to a concept of “solution” in Visual Studio terminology. Project( example LANGUAGES CXX VERSION 1.0 )
0 kommentar(er)
