mirror of
				https://github.com/TheLartians/ModernCppStarter.git
				synced 2025-10-31 02:01:33 +01:00 
			
		
		
		
	docs: fix typos.
This commit is contained in:
		
							parent
							
								
									363bf94ac1
								
							
						
					
					
						commit
						3220574fc8
					
				
					 2 changed files with 2 additions and 2 deletions
				
			
		|  | @ -47,7 +47,7 @@ add_library(Greeter ${headers} ${sources}) | ||||||
| 
 | 
 | ||||||
| set_target_properties(Greeter PROPERTIES CXX_STANDARD 17) | set_target_properties(Greeter PROPERTIES CXX_STANDARD 17) | ||||||
| 
 | 
 | ||||||
| # beeing a cross-platform target, we enforce enforce standards conformance on MSVC | # beeing a cross-platform target, we enforce standards conformance on MSVC | ||||||
| target_compile_options(Greeter PUBLIC "$<$<BOOL:${MSVC}>:/permissive->") | target_compile_options(Greeter PUBLIC "$<$<BOOL:${MSVC}>:/permissive->") | ||||||
| 
 | 
 | ||||||
| # Link dependencies (if required) | # Link dependencies (if required) | ||||||
|  |  | ||||||
|  | @ -107,7 +107,7 @@ Glob is considered bad because any changes to the source file structure [might n | ||||||
| 
 | 
 | ||||||
| > I want create additional targets that depend on my library. Should I modify the main CMakeLists to include them? | > I want create additional targets that depend on my library. Should I modify the main CMakeLists to include them? | ||||||
| 
 | 
 | ||||||
| Always avoid including derived projects from the from the libraries CMakeLists (even though it is a common sight in the C++ world), as this effectively inverts the dependency tree and makes the build system hard to reason about. | Always avoid including derived projects from the libraries CMakeLists (even though it is a common sight in the C++ world), as this effectively inverts the dependency tree and makes the build system hard to reason about. | ||||||
| Instead, create a new directory or project with a CMakeLists that adds the library as a dependency (e.g. like the [standalone](standalone/CMakeLists.txt) directory). | Instead, create a new directory or project with a CMakeLists that adds the library as a dependency (e.g. like the [standalone](standalone/CMakeLists.txt) directory). | ||||||
| Depending type it might make sense move these components into a separate repositories and reference a specific commit or version of the library. | Depending type it might make sense move these components into a separate repositories and reference a specific commit or version of the library. | ||||||
| This has the advantage that individual libraries and components can be improved and updated independently. | This has the advantage that individual libraries and components can be improved and updated independently. | ||||||
|  |  | ||||||
		Loading…
	
	Add table
		Add a link
		
	
		Reference in a new issue