CMake/MinimalExamples: Difference between revisions
From KitwarePublic
< CMake
Jump to navigationJump to search
(Add explicit preformat markup) |
(Remove leading space rectangles from preformatted blocks) |
||
Line 5: | Line 5: | ||
<pre> | <pre> | ||
add_executable(hello hello.c) | |||
</pre> | </pre> | ||
Line 11: | Line 11: | ||
<pre> | <pre> | ||
add_library(hellolib SHARED hellolib.c) | |||
</pre> | </pre> | ||
Revision as of 18:33, 24 April 2018
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!