mirror of
https://github.com/ttroy50/cmake-examples.git
synced 2025-12-18 12:14:36 +03:00
spelling fixes
This commit is contained in:
@@ -49,7 +49,7 @@ the sources in the +add_library+ call.
|
||||
|
||||
[NOTE]
|
||||
====
|
||||
As mentioned in the prevoius example, we pass the source files directly to the
|
||||
As mentioned in the previous example, we pass the source files directly to the
|
||||
+add_library+ call, as recommended for modern CMake.
|
||||
====
|
||||
|
||||
@@ -73,7 +73,7 @@ This will cause the included directory used in the following places:
|
||||
The meaning of scopes are:
|
||||
|
||||
* +PRIVATE+ - the directory is added to this target's include directories
|
||||
* +INTERFACE+ - the directory is added to the include directores for any targets that link this library.
|
||||
* +INTERFACE+ - the directory is added to the include directories for any targets that link this library.
|
||||
* +PUBLIC+ - As above, it is included int his library and also any targets that link this library.
|
||||
|
||||
|
||||
@@ -113,7 +113,7 @@ target_link_libraries( hello_binary
|
||||
----
|
||||
|
||||
This tells CMake to link the hello_library against the hello_binary executable
|
||||
during link time. It will also propogate any include directries with +PUBLIC+ or +INTERFACE+ scope
|
||||
during link time. It will also propagate any include directories with +PUBLIC+ or +INTERFACE+ scope
|
||||
from the linked library target.
|
||||
|
||||
An example of this being called by the compiler is
|
||||
|
||||
@@ -39,7 +39,7 @@ target_compile_definitions(cmake_examples_compile_flags
|
||||
|
||||
This will cause the compiler to add the definition +-DEX3+ when compiling the target.
|
||||
|
||||
In the target was a library, and the scope +PUBLIC+ or +INTERFACE+ has been choosen the definition would also be included in any executables that link this target.
|
||||
In the target was a library, and the scope +PUBLIC+ or +INTERFACE+ has been chosen the definition would also be included in any executables that link this target.
|
||||
|
||||
For compiler options you can also use the +target_compile_options()+ link:https://cmake.org/cmake/help/v3.0/command/target_compile_options.html[function].
|
||||
|
||||
@@ -70,7 +70,7 @@ For more details, see https://cmake.org/cmake/help/v3.0/command/set.html[here]
|
||||
====
|
||||
|
||||
|
||||
Once set the +CMAKE_C_FLAGS+ and +CMAKE_CXX_FLAGS+ will set a compler flag / definiton globally for all targets in this directory or any included sub-directories. This method is not recommended for general usage now and the +target_compile_definitions+ function is preferred.
|
||||
Once set the +CMAKE_C_FLAGS+ and +CMAKE_CXX_FLAGS+ will set a compler flag / definition globally for all targets in this directory or any included sub-directories. This method is not recommended for general usage now and the +target_compile_definitions+ function is preferred.
|
||||
|
||||
### Set CMake Flags
|
||||
|
||||
|
||||
@@ -95,7 +95,7 @@ Most modern CMake libraries link:https://cmake.org/cmake/help/v3.6/prop_tgt/IMPO
|
||||
The benefit of imported targets are that they can also populate include directories and linked libraries.
|
||||
|
||||
For example, starting from v3.5+ of CMake, the
|
||||
Boost module supports this. Similar to using your own ALIAS target for libraires, an +ALIAS+ in a module can make referencing found targets eaiser.
|
||||
Boost module supports this. Similar to using your own ALIAS target for libraires, an +ALIAS+ in a module can make referencing found targets easier.
|
||||
|
||||
In the case of Boost, all targets are exported using the `Boost::` identifier and then the name
|
||||
of the subsystem. For example you can use:
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
#!/bin/bash
|
||||
# Ubuntu supports multiple versions of clang to be installed at the same time.
|
||||
# The tests need to determin the clang binary before calling cmake
|
||||
# The tests need to determine the clang binary before calling cmake
|
||||
clang_bin=`which clang`
|
||||
clang_xx_bin=`which clang++`
|
||||
|
||||
|
||||
@@ -6,7 +6,7 @@ toc::[]
|
||||
|
||||
# Introduction
|
||||
|
||||
This example shows a common method to set the C++ Standard. This can be used with most versions of CMake. However, if you are targetting a recent version of CMake there are more convenient methods available.
|
||||
This example shows a common method to set the C++ Standard. This can be used with most versions of CMake. However, if you are targeting a recent version of CMake there are more convenient methods available.
|
||||
|
||||
The files in this tutorial are below:
|
||||
|
||||
|
||||
@@ -9,7 +9,7 @@ project (hello_cpp11)
|
||||
# Add an executable
|
||||
add_executable(hello_cpp11 main.cpp)
|
||||
|
||||
# set the C++ standard to the approriate standard for using auto
|
||||
# set the C++ standard to the appropriate standard for using auto
|
||||
target_compile_features(hello_cpp11 PUBLIC cxx_auto_type)
|
||||
|
||||
# Print the list of known compile features for this version of CMake
|
||||
|
||||
@@ -6,7 +6,7 @@ set compile flags, create and link executables and libraries, and install them.
|
||||
The examples included are
|
||||
|
||||
- link:A-hello-cmake[hello-cmake]. A hello world example.
|
||||
- link:B-hello-headers[hello-headers]. A slightly more complicated hello world example, using seperate source and include folders.
|
||||
- link:B-hello-headers[hello-headers]. A slightly more complicated hello world example, using separate source and include folders.
|
||||
- link:C-static-library[static-library]. An example using a static library.
|
||||
- link:D-shared-library[shared-library]. An example using a shared library.
|
||||
- link:E-installing[installing]. Shows how to create a 'make install' target that will install binaries and libraries.
|
||||
|
||||
Reference in New Issue
Block a user