Cmake - Revision history

Ted: Multiple executables from one CMakeLists.txt file

2026-04-13T21:41:50Z

Multiple executables from one CMakeLists.txt file

Ted: Add section "Understanding Cmake Targets in General"

2025-12-22T19:25:21Z

Add section "Understanding Cmake Targets in General"

Ted at 19:24, 22 December 2025

2025-12-22T19:24:45Z

Ted: Add link to Coderefinery article on Cmake

2025-12-22T18:59:12Z

Add link to Coderefinery article on Cmake

Ted: Add subsection and note on cmake command taget_link_libraries()

2025-11-10T18:44:06Z

Add subsection and note on cmake command taget_link_libraries()

Ted: /* ^ cmake Commands */

2025-09-29T06:50:22Z

^ cmake Commands

Ted: Add reference to cmake target_compile_definitions()

2025-09-25T18:57:43Z

Add reference to cmake target_compile_definitions()

Ted: /* ^ To Create Libraries In A Build */

2025-09-25T18:50:53Z

^ To Create Libraries In A Build

Ted: Add section "To Create Libraries In A Build"

2025-09-25T18:49:36Z

Add section "To Create Libraries In A Build"

Ted: Refine notes on cmake build strategy

2025-09-25T18:32:45Z

Refine notes on cmake build strategy

@@ Line 130: / Line 130: @@
 *  https://cmake.org/cmake/help/latest/manual/cmake-buildsystem.7.html#target-commands
-== [[#top|^]] Understanding Cmake Targets in General ==
+== [[#top|^]] Multiple Executables ==
-*  https://cmake.org/cmake/help/latest/manual/cmake-buildsystem.7.html#target-commands
+Multiple executables from one CMakeLists.txt file
 == DESPUES DE ESTO REVISTAR TODO - 2025 Q3 ==

← Older revision		Revision as of 19:25, 22 December 2025
Line 125:		Line 125:

	Cmake documentation at [https://cmake.org/cmake/help/latest/command/target_link_libraries.html target_link_libraries() documentation] describes the "item" parameters of this cmake command as being one of four or five application or programmatic entities. Most of these it refers to as libraries themselves. From observation of several uses the "items" parameters of ``target_link_libraries()`` appear that they can be either libraries or application modules which depend on the compiled code referred to by the first parameter passed to target_link_libraries().		Cmake documentation at [https://cmake.org/cmake/help/latest/command/target_link_libraries.html target_link_libraries() documentation] describes the "item" parameters of this cmake command as being one of four or five application or programmatic entities. Most of these it refers to as libraries themselves. From observation of several uses the "items" parameters of ``target_link_libraries()`` appear that they can be either libraries or application modules which depend on the compiled code referred to by the first parameter passed to target_link_libraries().
		+
		+	== [[#top\|^]] Understanding Cmake Targets in General ==
		+
		+	* https://cmake.org/cmake/help/latest/manual/cmake-buildsystem.7.html#target-commands

	== [[#top\|^]] Understanding Cmake Targets in General ==		== [[#top\|^]] Understanding Cmake Targets in General ==

← Older revision		Revision as of 19:24, 22 December 2025
Line 125:		Line 125:

	Cmake documentation at [https://cmake.org/cmake/help/latest/command/target_link_libraries.html target_link_libraries() documentation] describes the "item" parameters of this cmake command as being one of four or five application or programmatic entities. Most of these it refers to as libraries themselves. From observation of several uses the "items" parameters of ``target_link_libraries()`` appear that they can be either libraries or application modules which depend on the compiled code referred to by the first parameter passed to target_link_libraries().		Cmake documentation at [https://cmake.org/cmake/help/latest/command/target_link_libraries.html target_link_libraries() documentation] describes the "item" parameters of this cmake command as being one of four or five application or programmatic entities. Most of these it refers to as libraries themselves. From observation of several uses the "items" parameters of ``target_link_libraries()`` appear that they can be either libraries or application modules which depend on the compiled code referred to by the first parameter passed to target_link_libraries().
		+
		+	== [[#top\|^]] Understanding Cmake Targets in General ==
		+
		+	* https://cmake.org/cmake/help/latest/manual/cmake-buildsystem.7.html#target-commands

	== DESPUES DE ESTO REVISTAR TODO - 2025 Q3 ==		== DESPUES DE ESTO REVISTAR TODO - 2025 Q3 ==

@@ Line 21: / Line 21: @@
 * Cmake language is composed of comments, commands and variables.
-(2) Cmake variables come in three types
+(2) Cmake variables come in three types (these notes on variables to be moved to another section of this page).
 *  ${variable}
@@ Line 28: / Line 28: @@
 *  $CACHE{variable}
 <!-- spacer -->

@@ Line 107: / Line 107: @@
+       )
-  (4)  target_link_libraries(<name_of_library> PUBLIC|INTERFACE|PRIVATE
+  (4)  target_link_libraries(<name_of_library> PUBLIC|INTERFACE|PRIVATE <names_of_targets_in_need_of_library>)
 </pre>
@@ Line 117: / Line 117: @@
 *  https://cmake.org/cmake/help/latest/command/target_compile_definitions.html
 == DESPUES DE ESTO REVISTAR TODO - 2025 Q3 ==

← Older revision		Revision as of 06:50, 29 September 2025
Line 66:		Line 66:

	* https://discourse.cmake.org/t/how-to-find-all-the-include-folders-for-a-target-for-a-static-analyzer/3233/3		* https://discourse.cmake.org/t/how-to-find-all-the-include-folders-for-a-target-for-a-static-analyzer/3233/3
		+
		+	A forum post discussing how to make cmake generate info to go into a file at build time:
		+
		+	* https://stackoverflow.com/questions/13419255/how-to-get-cmake-to-create-timestamp-file-after-an-actual-build-link-do-nothin

	<!-- odne komentar -->		<!-- odne komentar -->

← Older revision		Revision as of 18:57, 25 September 2025
Line 111:		Line 111:

	* https://cmake.org/cmake/help/latest/prop_tgt/INTERFACE_LINK_LIBRARIES.html#prop_tgt:INTERFACE_LINK_LIBRARIES		* https://cmake.org/cmake/help/latest/prop_tgt/INTERFACE_LINK_LIBRARIES.html#prop_tgt:INTERFACE_LINK_LIBRARIES
		+
		+	* https://cmake.org/cmake/help/latest/command/target_compile_definitions.html

	== DESPUES DE ESTO REVISTAR TODO - 2025 Q3 ==		== DESPUES DE ESTO REVISTAR TODO - 2025 Q3 ==

← Older revision		Revision as of 18:49, 25 September 2025
Line 84:		Line 84:

	(Q1) Why in cmake projects can there end up being so many distinctly named "projects"?		(Q1) Why in cmake projects can there end up being so many distinctly named "projects"?
		+
		+	== [[#top\|^]] To Create Libraries In A Build ==
		+
		+	Cmake supports the specification and building of library object files as part of a project. Further, cmake supports the defining and declaring of where and how these libraries will be linked to other targets in the given project. To create a library, a typical pattern of cmake function calls includes:
		+
		+	<pre>
		+	(1) add_library(<name_of_library> OBJECT)
		+
		+	(2) target_include_directories(<name_of_library>
		+	PUBLIC include_path
		+	PRIVATE include_path_private
		+	)
		+
		+	(3) target_sources(<name_of_library PRIVATE
		+	source_file_1.c
		+	source_file_2.c
		+	. . .
		+	)
		+
		+	(4) target_link_libraries(<name_of_library> PUBLIC\|INTERFACE\|PRIVATE
		+	</pre>
		+
		+	* https://cmake.org/cmake/help/latest/manual/cmake-buildsystem.7.html#target-usage-requirements

	== DESPUES DE ESTO REVISTAR TODO - 2025 Q3 ==		== DESPUES DE ESTO REVISTAR TODO - 2025 Q3 ==

@@ Line 71: / Line 71: @@
 == [[#top|^]] Project Organization and Cmake ==
-In the [https://cmake.org/cmake/help/book/mastering-cmake/ "Mastering Cmake"] online book Cmake team speaks to Cmake's built in strategy of creating a dedicated build directory at the root of a given project.  This dedicated build directory keeps all build artifacts separate from project sources, and allows for a straightforward (read simple) and safe way of deleting builds without impacting project source files.  This strategy can be achieved with other build systems like GNU `make`, but cmake operates on projects this way by default.
+In the [https://cmake.org/cmake/help/book/mastering-cmake/ "Mastering Cmake"] online book Cmake team speaks to Cmake's strategy to create a dedicated build directory at the root of a given project.  This dedicated build directory keeps all build artifacts separate from project sources, and allows for a simple and safe way to deleting build generated files without impacting project sources.  This strategy can be achieved with other build systems like GNU `make`, but cmake operates on projects this way by default.
-There's more to project organization than choosing an area for build output (artifacts).  In particular when a final compiled ready-to-execute image involves two or more applications within, a project's organization becomes more complex.  This so whether projects utilize cmake or another build system.
+There's more to project organization than choosing an area for build output (artifacts).  In particular when a final compiled image involves two or more applications, a project's organization becomes more complex.  This so whether projects utilize cmake or another build system.
 Some links to project organization forum posts follow here: