Scanning dependencies of target all-generatedīut then touch the file ‘gen1’, or overwrite it with something other text, or change the value of SPECIAL_TEXT in CMakeLists.txt to something else, and you will see this: Generating gen1 The first time you build it: Scanning dependencies of target gen1-wrapper This is subtly wrong, even though you did what you were told, and wrapped the custom command in a custom target. # Toplevel CMakeLists.txtĬmake -E echo "Generate my C code" > foo.c
#CMAKE ADD EXECUTABLE CODE#
Custom commands in different directoriesĪnother use case for add_custom_command() is generating source code files using 3rd party tools. Or, you might want to remove the ALL from your custom target, so that you have to explicitly run make docs to generate the documentation. In practice, you might also want to make the custom command depend on all your source code, so it gets regenerated every time you change the code. But as a special case, you can use add_custom_target(ALL) to create a new target attached to the “all” target: add_custom_target(
How about using add_dependencies()? No, you can’t use that with any of the built in targets. So we need to add a dependency between docs/doxygen.stamp and the “all” target. Nothing depends on the documentation, so it isn’t built. But actually, here’s what to expect: nothing! If you build this, you get no output. We have to create a ‘stamp’ file because Doxygen generates lots of different files, and we can’t really tell CMake what to expect. "Generating API documentation with Doxygen" You may live to regret ever letting it in. This is where add_custom_command() enters your life. If your project is a good one then maybe you use a documentation tool like GTK-Doc or Doxygen to generate documentation from the code. There are also “install” and “test” targets built in ( but no “clean” target). What is “all”, in the dependency graph to the left? It’s a built in target, and it’s the default target. When you run CMake, both of them get built.
You have a library, and a program that depends on it. This is CMake at its simplest (and best). Here is a hopefully complete list of things you might want to do in CMake that involve custom commands and custom targets depending on each other, and some explainations as to why things don’t work the way that you might expect.
What makes it so hard is that there’s not one limitation, but several. But files aren’t targets and have all sorts of exciting limitations to make you forget everything you ever new about dependency management. If you want to generate some kind of file at build time, in some manner other than compiling C or C++ code, then you need to use a custom command to generate the file. If you’ve tried do anything non-trivial in CMake using the add_custom_command() command, you may have got stuck in this horrible swamp of confusion. Unfortunately, not everything is a target though! As I said in my last post about CMake, targets are everything in CMake.
0 kommentar(er)
