You can also add this to your search path manually, including MyLib_PATH, and CMake gives the user nice help output if the configure file is not found.
CMAKE INSTALL COMMAND INSTALL
When CMake searches for a package, it will look in the current install prefix and several standard places. That's it! Now once you install a package, there will be files in lib/cmake/MyLib that CMake will search for (specifically, MyLibConfig.cmake and MyLibConfigVersion.cmake), and the targets file that config uses should be there as well. # Any extra setup # Add the targets file include( "$/MyLibConfigVersion.cmake" # Capturing values from configure (optional) set(my-config-var Same syntax as find_package The contents that look like this: include(CMakeFindDependencyMacro) in file, and you will want to use the syntax. If you want to capture configure time variables, you can use a. Then write a custom MyLibConfig.cmake file in your source tree somewhere. If you have no dependencies, just use MyLibConfig.cmake instead of MyLibTargets.cmake here. This file will take the targets you exported and put them in a file. The later option is what you'll need if you have any dependencies, even just OpenMP, so I'll illustrate that method.įirst, make an install targets file (very similar to the one you made in the build directory): install( EXPORT MyLibTargets You need to make a MyLibConfig.cmake, but you can do it either by exporting your targets directly to it, or by writing it by hand, then including the targets file. That looks like this: include(CMakePackageConfigHelpers) It's usually a good idea to give CMake access to the version, so that find_package can have a version specified. It only sets the includes destination on the exported target (which is often already set by target_include_directories, so check the MyLibTargets file and make sure you don't have the include directory included twice if you want clean cmake files). The includes destination is special since a target does not install includes. The various destinations are only needed if you have a library, static library, or program to install.
Your basic target install command looks like this: install(TARGETS MyLib Use the binary installer, since it can optionally add CMake to the system path. CMake command line support is provided for Windows, Android, and iOS.
Pass the name of the library target to target_link_libraries to use the respective library.Install commands cause a file or target to be "installed" into the install tree when you make install. CMake supports RAD Studio’s Clang-enhanced compilers, and for Win32 uses the new Clang-enhanced driver, bcc32x. The target names start with Qt5::, followed by the module name.
Imported library targetsĮach Qt module that is loaded defines a CMake library target. For more details, see CMake AUTOMOC documentation. The CMAKE_AUTOMOC setting runs moc automatically when required.
0 kommentar(er)
