CMake/MinimalExamples: Difference between revisions
From KitwarePublic
< CMake
Jump to navigationJump to search
(Give hope to newbies by showing the CMakeLists.txt need not be complex) |
No edit summary |
||
| Line 1: | Line 1: | ||
CMake has lots of documentation, but when learning a new feature (or just starting out), there is no substitute for trying it out in isolation. | CMake has lots of good [http://www.cmake.org/documentation/ documentation], but when learning a new feature (or just starting out), there is no substitute for trying it out in isolation. | ||
That way, if anything goes wrong, you have fewer lines of CMakeList.txt to look through for problems. | That way, if anything goes wrong, you have fewer lines of CMakeList.txt to look through for problems. | ||
Revision as of 17:49, 5 November 2014
CMake has lots of good documentation, but when learning a new feature (or just starting out), there is no substitute for trying it out in isolation. That way, if anything goes wrong, you have fewer lines of CMakeList.txt to look through for problems.
For instance, here is the simplest possible CMakeLists.txt for a "Hello, World" project:
add_executable(hello hello.c)
And here's the simplest possible one for a shared library:
add_library(hellolib SHARED hellolib.c)
That's right - CMakeLists.txt can be a single line. And if that's all you need, that's all you should use!
