rayelliott
/
barrier
mirror of https://github.com/debauchee/barrier.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
barrier/tool/win/cmake/doc/cmake-2.8/cmake-modules.html

1246 lines
237 KiB
HTML
Raw Blame History

<html><head><title>cmake-modules - cmake</title></head><body>
<h2><a name="section_Index"/>Master Index CMake 2.8.0</h2>
<ul>
<li><a href="#section_Introduction"<b>Introduction</b></a></li>
<li><a href="#section_Description"<b>Description</b></a></li>
<li><a href="#section_Standard CMake Modules"<b>Standard CMake Modules</b></a></li>
<li><a href="#section_Copyright"<b>Copyright</b></a></li>
<li><a href="#section_See Also"<b>See Also</b></a></li>
</ul>
<h2><a name="section_Introduction"/>Introduction</h2>
<ul>
</ul>
<p>cmake-modules - Reference of available CMake modules.
<h2><a name="section_Description"/>Description</h2>
<ul>
</ul>
<p>The "cmake" executable is the CMake command-line interface. It may be used to configure projects in scripts. Project configuration settings may be specified on the command line with the -D option. The -i option will cause cmake to interactively prompt for such settings.
<p>CMake is a cross-platform build system generator. Projects specify their build process with platform-independent CMake listfiles included in each directory of a source tree with the name CMakeLists.txt. Users build a project by using CMake to generate a build system for a native tool on their platform.
<h2><a name="section_Standard CMake Modules"/>Standard CMake Modules</h2>
<ul>
<li><a href="#module:AddFileDependencies"><b><code>AddFileDependencies</code></b></a></li> <li><a href="#module:BundleUtilities"><b><code>BundleUtilities</code></b></a></li> <li><a href="#module:CMakeBackwardCompatibilityCXX"><b><code>CMakeBackwardCompatibilityCXX</code></b></a></li> <li><a href="#module:CMakeDependentOption"><b><code>CMakeDependentOption</code></b></a></li> <li><a href="#module:CMakeDetermineVSServicePack"><b><code>CMakeDetermineVSServicePack</code></b></a></li> <li><a href="#module:CMakeFindFrameworks"><b><code>CMakeFindFrameworks</code></b></a></li> <li><a href="#module:CMakeForceCompiler"><b><code>CMakeForceCompiler</code></b></a></li> <li><a href="#module:CMakePrintSystemInformation"><b><code>CMakePrintSystemInformation</code></b></a></li> <li><a href="#module:CMakeVerifyManifest"><b><code>CMakeVerifyManifest</code></b></a></li> <li><a href="#module:CPack"><b><code>CPack</code></b></a></li> <li><a href="#module:CPackDeb"><b><code>CPackDeb</code></b></a></li> <li><a href="#module:CPackRPM"><b><code>CPackRPM</code></b></a></li> <li><a href="#module:CTest"><b><code>CTest</code></b></a></li> <li><a href="#module:CTestScriptMode"><b><code>CTestScriptMode</code></b></a></li> <li><a href="#module:CheckCCompilerFlag"><b><code>CheckCCompilerFlag</code></b></a></li> <li><a href="#module:CheckCSourceCompiles"><b><code>CheckCSourceCompiles</code></b></a></li> <li><a href="#module:CheckCSourceRuns"><b><code>CheckCSourceRuns</code></b></a></li> <li><a href="#module:CheckCXXCompilerFlag"><b><code>CheckCXXCompilerFlag</code></b></a></li> <li><a href="#module:CheckCXXSourceCompiles"><b><code>CheckCXXSourceCompiles</code></b></a></li> <li><a href="#module:CheckCXXSourceRuns"><b><code>CheckCXXSourceRuns</code></b></a></li> <li><a href="#module:CheckFortranFunctionExists"><b><code>CheckFortranFunctionExists</code></b></a></li> <li><a href="#module:CheckFunctionExists"><b><code>CheckFunctionExists</code></b></a></li> <li><a href="#module:CheckIncludeFile"><b><code>CheckIncludeFile</code></b></a></li> <li><a href="#module:CheckIncludeFileCXX"><b><code>CheckIncludeFileCXX</code></b></a></li> <li><a href="#module:CheckIncludeFiles"><b><code>CheckIncludeFiles</code></b></a></li> <li><a href="#module:CheckLibraryExists"><b><code>CheckLibraryExists</code></b></a></li> <li><a href="#module:CheckStructHasMember"><b><code>CheckStructHasMember</code></b></a></li> <li><a href="#module:CheckSymbolExists"><b><code>CheckSymbolExists</code></b></a></li> <li><a href="#module:CheckTypeSize"><b><code>CheckTypeSize</code></b></a></li> <li><a href="#module:CheckVariableExists"><b><code>CheckVariableExists</code></b></a></li> <li><a href="#module:Dart"><b><code>Dart</code></b></a></li> <li><a href="#module:Documentation"><b><code>Documentation</code></b></a></li> <li><a href="#module:ExternalProject"><b><code>ExternalProject</code></b></a></li> <li><a href="#module:FeatureSummary"><b><code>FeatureSummary</code></b></a></li> <li><a href="#module:FindALSA"><b><code>FindALSA</code></b></a></li> <li><a href="#module:FindASPELL"><b><code>FindASPELL</code></b></a></li> <li><a href="#module:FindAVIFile"><b><code>FindAVIFile</code></b></a></li> <li><a href="#module:FindBISON"><b><code>FindBISON</code></b></a></li> <li><a href="#module:FindBLAS"><b><code>FindBLAS</code></b></a></li> <li><a href="#module:FindBZip2"><b><code>FindBZip2</code></b></a></li> <li><a href="#module:FindBoost"><b><code>FindBoost</code></b></a></li> <li><a href="#module:FindBullet"><b><code>FindBullet</code></b></a></li> <li><a href="#module:FindCABLE"><b><code>FindCABLE</code></b></a></li> <li><a href="#module:FindCUDA"><b><code>FindCUDA</code></b></a></li> <li><a href="#module:FindCURL"><b><code>FindCURL</code></b></a></li> <li><a href="#module:FindCVS"><b><code>FindCVS</code></b></a></li> <li><a href="#module:FindCoin3D"><b><code>FindCoin3D</code></b></a></li> <li><a href="#module:FindCups"><b><code>FindCups</code></b></a></li> <li><a href="#module:FindCurses"><b><code>FindCurses</code></b></a></li> <li><a href="#module:FindCxxTest"><b><code>FindCxxTest</code></b></a></li> <li><a href="#module:FindCygwin"><b><code>FindCygwin</code></b></a></li> <li><a href="#module:FindDCMTK"><b><code>FindDCMTK</code></b></a></li> <li><a href="#module:FindDart"><b><code>FindDart</code></b></a></li> <li><a href="#module:FindDevIL"><b><code>FindDevIL</code></b></a></li> <li><a href="#module:FindDoxygen"><b><code>FindDoxygen</code></b></a></li> <li><a href="#module:FindEXPAT"><b><code>FindEXPAT</code></b></a></li> <li><a href="#module:FindFLEX"><b><code>FindFLEX</code></b></a></li> <li><a href="#module:FindFLTK"><b><code>FindFLTK</code></b></a></li> <li><a href="#module:FindFLTK2"><b><code>FindFLTK2</code></b></a></li> <li><a href="#module:FindFreetype"><b><code>FindFreetype</code></b></a></li> <li><a href="#module:FindGCCXML"><b><code>FindGCCXML</code></b></a></li> <li><a href="#module:FindGDAL"><b><code>FindGDAL</code></b></a></li> <li><a href="#module:FindGIF"><b><code>FindGIF</code></b></a></li> <li><a href="#module:FindGLUT"><b><code>FindGLUT</code></b></a></li> <li><a href="#module:FindGTK"><b><code>FindGTK</code></b></a></li> <li><a href="#module:FindGTK2"><b><code>FindGTK2</code></b></a></li> <li><a href="#module:FindGTest"><b><code>FindGTest</code></b></a></li> <li><a href="#module:FindGettext"><b><code>FindGettext</code></b></a></li> <li><a href="#module:FindGnuTLS"><b><code>FindGnuTLS</code></b></a></li> <li><a href="#module:FindGnuplot"><b><code>FindGnuplot</code></b></a></li> <li><a href="#module:FindHDF5"><b><code>FindHDF5</code></b></a></li> <li><a href="#module:FindHSPELL"><b><code>FindHSPELL</code></b></a></li> <li><a href="#module:FindHTMLHelp"><b><code>FindHTMLHelp</code></b></a></li> <li><a href="#module:FindITK"><b><code>FindITK</code></b></a></li> <li><a href="#module:FindImageMagick"><b><code>FindImageMagick</code></b></a></li> <li><a href="#module:FindJNI"><b><code>FindJNI</code></b></a></li> <li><a href="#module:FindJPEG"><b><code>FindJPEG</code></b></a></li> <li><a href="#module:FindJasper"><b><code>FindJasper</code></b></a></li> <li><a href="#module:FindJava"><b><code>FindJava</code></b></a></li> <li><a href="#module:FindKDE3"><b><code>FindKDE3</code></b></a></li> <li><a href="#module:FindKDE4"><b><code>FindKDE4</code></b></a></li> <li><a href="#module:FindLAPACK"><b><code>FindLAPACK</code></b></a></li> <li><a href="#module:FindLATEX"><b><code>FindLATEX</code></b></a></li> <li><a href="#module:FindLibXml2"><b><code>FindLibXml2</code></b></a></li> <li><a href="#module:FindLibXslt"><b><code>FindLibXslt</code></b></a></li> <li><a href="#module:FindLua50"><b><code>FindLua50</code></b></a></li> <li><a href="#module:FindLua51"><b><code>FindLua51</code></b></a></li> <li><a href="#module:FindMFC"><b><code>FindMFC</code></b></a></li> <li><a href="#module:FindMPEG"><b><code>FindMPEG</code></b></a></li> <li><a href="#module:FindMPEG2"><b><code>FindMPEG2</code></b></a></li> <li><a href="#module:FindMPI"><b><code>FindMPI</code></b></a></li> <li><a href="#module:FindMatlab"><b><code>FindMatlab</code></b></a></li> <li><a href="#module:FindMotif"><b><code>FindMotif</code></b></a></li> <li><a href="#module:FindOpenAL"><b><code>FindOpenAL</code></b></a></li> <li><a href="#module:FindOpenGL"><b><code>FindOpenGL</code></b></a></li> <li><a href="#module:FindOpenMP"><b><code>FindOpenMP</code></b></a></li> <li><a href="#module:FindOpenSSL"><b><code>FindOpenSSL</code></b></a></li> <li><a href="#module:FindOpenSceneGraph"><b><code>FindOpenSceneGraph</code></b></a></li> <li><a href="#module:FindOpenThreads"><b><code>FindOpenThreads</code></b></a></li> <li><a href="#module:FindPHP4"><b><code>FindPHP4</code></b></a></li> <li><a href="#module:FindPNG"><b><code>FindPNG</code></b></a></li> <li><a href="#module:FindPackageHandleStandardArgs"><b><code>FindPackageHandleStandardArgs</code></b></a></li> <li><a href="#module:FindPackageMessage"><b><code>FindPackageMessage</code></b></a></li> <li><a href="#module:FindPerl"><b><code>FindPerl</code></b></a></li> <li><a href="#module:FindPerlLibs"><b><code>FindPerlLibs</code></b></a></li> <li><a href="#module:FindPhysFS"><b><code>FindPhysFS</code></b></a></li> <li><a href="#module:FindPike"><b><code>FindPike</code></b></a></li> <li><a href="#module:FindPkgConfig"><b><code>FindPkgConfig</code></b></a></li> <li><a href="#module:FindProducer"><b><code>FindProducer</code></b></a></li> <li><a href="#module:FindProtobuf"><b><code>FindProtobuf</code></b></a></li> <li><a href="#module:FindPythonInterp"><b><code>FindPythonInterp</code></b></a></li> <li><a href="#module:FindPythonLibs"><b><code>FindPythonLibs</code></b></a></li> <li><a href="#module:FindQt"><b><code>FindQt</code></b></a></li> <li><a href="#module:FindQt3"><b><code>FindQt3</code></b></a></li> <li><a href="#module:FindQt4"><b><code>FindQt4</code></b></a></li> <li><a href="#module:FindQuickTime"><b><code>FindQuickTime</code></b></a></li> <li><a href="#module:FindRTI"><b><code>FindRTI</code></b></a></li> <li><a href="#module:FindRuby"><b><code>FindRuby</code></b></a></li> <li><a href="#module:FindSDL"><b><code>FindSDL</code></b></a></li> <li><a href="#module:FindSDL_image"><b><code>FindSDL_image</code></b></a></li> <li><a href="#module:FindSDL_mixer"><b><code>FindSDL_mixer</code></b></a></li> <li><a href="#module:FindSDL_net"><b><code>FindSDL_net</code></b></a></li> <li><a href="#module:FindSDL_sound"><b><code>FindSDL_sound</code></b></a></li> <li><a href="#module:FindSDL_ttf"><b><code>FindSDL_ttf</code></b></a></li> <li><a href="#module:FindSWIG"><b><code>FindSWIG</code></b></a></li> <li><a href="#module:FindSelfPackers"><b><code>FindSelfPackers</code></b></a></li> <li><a href="#module:FindSquish"><b><code>FindSquish</code></b></a></li> <li><a href="#module:FindSubversion"><b><code>FindSubversion</code></b></a></li> <li><a href="#module:FindTCL"><b><code>FindTCL</code></b></a></li> <li><a href="#module:FindTIFF"><b><code>FindTIFF</code></b></a></li> <li><a href="#module:FindTclStub"><b><code>FindTclStub</code></b></a></li> <li><a href="#module:FindTclsh"><b><code>FindTclsh</code></b></a></li> <li><a href="#module:FindThreads"><b><code>FindThreads</code></b></a></li> <li><a href="#module:FindUnixCommands"><b><code>FindUnixCommands</code></b></a></li> <li><a href="#module:FindVTK"><b><code>FindVTK</code></b></a></li> <li><a href="#module:FindWget"><b><code>FindWget</code></b></a></li> <li><a href="#module:FindWish"><b><code>FindWish</code></b></a></li> <li><a href="#module:FindX11"><b><code>FindX11</code></b></a></li> <li><a href="#module:FindXMLRPC"><b><code>FindXMLRPC</code></b></a></li> <li><a href="#module:FindZLIB"><b><code>FindZLIB</code></b></a></li> <li><a href="#module:Findosg"><b><code>Findosg</code></b></a></li> <li><a href="#module:FindosgAnimation"><b><code>FindosgAnimation</code></b></a></li> <li><a href="#module:FindosgDB"><b><code>FindosgDB</code></b></a></li> <li><a href="#module:FindosgFX"><b><code>FindosgFX</code></b></a></li> <li><a href="#module:FindosgGA"><b><code>FindosgGA</code></b></a></li> <li><a href="#module:FindosgIntrospection"><b><code>FindosgIntrospection</code></b></a></li> <li><a href="#module:FindosgManipulator"><b><code>FindosgManipulator</code></b></a></li> <li><a href="#module:FindosgParticle"><b><code>FindosgParticle</code></b></a></li> <li><a href="#module:FindosgProducer"><b><code>FindosgProducer</code></b></a></li> <li><a href="#module:FindosgShadow"><b><code>FindosgShadow</code></b></a></li> <li><a href="#module:FindosgSim"><b><code>FindosgSim</code></b></a></li> <li><a href="#module:FindosgTerrain"><b><code>FindosgTerrain</code></b></a></li> <li><a href="#module:FindosgText"><b><code>FindosgText</code></b></a></li> <li><a href="#module:FindosgUtil"><b><code>FindosgUtil</code></b></a></li> <li><a href="#module:FindosgViewer"><b><code>FindosgViewer</code></b></a></li> <li><a href="#module:FindosgVolume"><b><code>FindosgVolume</code></b></a></li> <li><a href="#module:FindosgWidget"><b><code>FindosgWidget</code></b></a></li> <li><a href="#module:Findosg_functions"><b><code>Findosg_functions</code></b></a></li> <li><a href="#module:FindwxWidgets"><b><code>FindwxWidgets</code></b></a></li> <li><a href="#module:FindwxWindows"><b><code>FindwxWindows</code></b></a></li> <li><a href="#module:FortranCInterface"><b><code>FortranCInterface</code></b></a></li> <li><a href="#module:GetPrerequisites"><b><code>GetPrerequisites</code></b></a></li> <li><a href="#module:InstallRequiredSystemLibraries"><b><code>InstallRequiredSystemLibraries</code></b></a></li> <li><a href="#module:MacroAddFileDependencies"><b><code>MacroAddFileDependencies</code></b></a></li> <li><a href="#module:SelectLibraryConfigurations"><b><code>SelectLibraryConfigurations</code></b></a></li> <li><a href="#module:SquishTestScript"><b><code>SquishTestScript</code></b></a></li> <li><a href="#module:TestBigEndian"><b><code>TestBigEndian</code></b></a></li> <li><a href="#module:TestCXXAcceptsFlag"><b><code>TestCXXAcceptsFlag</code></b></a></li> <li><a href="#module:TestForANSIForScope"><b><code>TestForANSIForScope</code></b></a></li> <li><a href="#module:TestForANSIStreamHeaders"><b><code>TestForANSIStreamHeaders</code></b></a></li> <li><a href="#module:TestForSSTREAM"><b><code>TestForSSTREAM</code></b></a></li> <li><a href="#module:TestForSTDNamespace"><b><code>TestForSTDNamespace</code></b></a></li> <li><a href="#module:UseEcos"><b><code>UseEcos</code></b></a></li> <li><a href="#module:UsePkgConfig"><b><code>UsePkgConfig</code></b></a></li> <li><a href="#module:UseQt4"><b><code>UseQt4</code></b></a></li> <li><a href="#module:UseSWIG"><b><code>UseSWIG</code></b></a></li> <li><a href="#module:Use_wxWindows"><b><code>Use_wxWindows</code></b></a></li> <li><a href="#module:UsewxWidgets"><b><code>UsewxWidgets</code></b></a></li></ul>
<p>The following modules are provided with CMake. They can be used with INCLUDE(ModuleName).
<pre> CMake Modules - Modules coming with CMake, the Cross-Platform Makefile Generator.</pre>
<p>This is the documentation for the modules and scripts coming with CMake. Using these modules you can check the computer system for installed software packages, features of the compiler and the existance of headers to name just a few.
<ul>
<li>
<a name="module:AddFileDependencies"><b><code>AddFileDependencies</code></b></a>: ADD_FILE_DEPENDENCIES(source_file depend_files...)<br>
<p>Adds the given files as dependencies to source_file<br>
</li>
<li>
<a name="module:BundleUtilities"><b><code>BundleUtilities</code></b></a>: <br>
<p>BundleUtilities.cmake<br><p>A collection of CMake utility functions useful for dealing with .app bundles on the Mac and bundle-like directories on any OS.<br><p>The following functions are provided by this script:<br><pre> get_bundle_main_executable<br> get_dotapp_dir<br> get_bundle_and_executable<br> get_bundle_all_executables<br> get_item_key<br> clear_bundle_keys<br> set_bundle_key_values<br> get_bundle_keys<br> copy_resolved_item_into_bundle<br> fixup_bundle_item<br> fixup_bundle<br> copy_and_fixup_bundle<br> verify_bundle_prerequisites<br> verify_bundle_symlinks<br> verify_app<br></pre>
<p><br><p>Requires CMake 2.6 or greater because it uses function, break and PARENT_SCOPE. Also depends on GetPrerequisites.cmake.
</li>
<li>
<a name="module:CMakeBackwardCompatibilityCXX"><b><code>CMakeBackwardCompatibilityCXX</code></b></a>: define a bunch of backwards compatibility variables<br>
<pre> CMAKE_ANSI_CXXFLAGS - flag for ansi c++ <br> CMAKE_HAS_ANSI_STRING_STREAM - has &lt;strstream&gt;<br> INCLUDE(TestForANSIStreamHeaders)<br> INCLUDE(CheckIncludeFileCXX)<br> INCLUDE(TestForSTDNamespace)<br> INCLUDE(TestForANSIForScope)<br></pre>
</li>
<li>
<a name="module:CMakeDependentOption"><b><code>CMakeDependentOption</code></b></a>: Macro to provide an option dependent on other options.<br>
<p>This macro presents an option to the user only if a set of other conditions are true. When the option is not presented a default value is used, but any value set by the user is preserved for when the option is presented again. Example invocation:<br><pre> CMAKE_DEPENDENT_OPTION(USE_FOO "Use Foo" ON<br> "USE_BAR;NOT USE_ZOT" OFF)<br></pre>
<p>If USE_BAR is true and USE_ZOT is false, this provides an option called USE_FOO that defaults to ON. Otherwise, it sets USE_FOO to OFF. If the status of USE_BAR or USE_ZOT ever changes, any value for the USE_FOO option is saved so that when the option is re-enabled it retains its old value.
</li>
<li>
<a name="module:CMakeDetermineVSServicePack"><b><code>CMakeDetermineVSServicePack</code></b></a>: Includes a public function for assisting users in trying to determine the<br>
<p>Visual Studio service pack in use.<br><p>Sets the passed in variable to one of the following values or an empty string if unknown.<br><pre> vc80<br> vc80sp1<br> vc90<br> vc90sp1<br></pre>
<p><br><p>Usage: ===========================<br><pre> if(MSVC)<br> include(CMakeDetermineVSServicePack)<br> DetermineVSServicePack( my_service_pack )<br></pre>
<p><br><pre> if( my_service_pack )<br> message(STATUS "Detected: ${my_service_pack}")<br> endif()<br> endif()<br></pre>
<p><br><p>===========================
</li>
<li>
<a name="module:CMakeFindFrameworks"><b><code>CMakeFindFrameworks</code></b></a>: helper module to find OSX frameworks
</li>
<li>
<a name="module:CMakeForceCompiler"><b><code>CMakeForceCompiler</code></b></a>: <br>
<p>This module defines macros intended for use by cross-compiling toolchain files when CMake is not able to automatically detect the compiler identification.<br><p>Macro CMAKE_FORCE_C_COMPILER has the following signature:<br><pre> CMAKE_FORCE_C_COMPILER(&lt;compiler&gt; &lt;compiler-id&gt;)<br></pre>
<p>It sets CMAKE_C_COMPILER to the given compiler and the cmake internal variable CMAKE_C_COMPILER_ID to the given compiler-id. It also bypasses the check for working compiler and basic compiler information tests.<br><p>Macro CMAKE_FORCE_CXX_COMPILER has the following signature:<br><pre> CMAKE_FORCE_CXX_COMPILER(&lt;compiler&gt; &lt;compiler-id&gt;)<br></pre>
<p>It sets CMAKE_CXX_COMPILER to the given compiler and the cmake internal variable CMAKE_CXX_COMPILER_ID to the given compiler-id. It also bypasses the check for working compiler and basic compiler information tests.<br><p>So a simple toolchain file could look like this:<br><pre> INCLUDE (CMakeForceCompiler)<br> SET(CMAKE_SYSTEM_NAME Generic)<br> CMAKE_FORCE_C_COMPILER (chc12 MetrowerksHicross)<br> CMAKE_FORCE_CXX_COMPILER (chc12 MetrowerksHicross)<br></pre>
</li>
<li>
<a name="module:CMakePrintSystemInformation"><b><code>CMakePrintSystemInformation</code></b></a>: print system information<br>
<p>This file can be used for diagnostic purposes just include it in a project to see various internal CMake variables.
</li>
<li>
<a name="module:CMakeVerifyManifest"><b><code>CMakeVerifyManifest</code></b></a>: <br>
<p>CMakeVerifyManifest.cmake<br><p>This script is used to verify that embeded manifests and side by side manifests for a project match. To run this script, cd to a directory and run the script with cmake -P. On the command line you can pass in versions that are OK even if not found in the .manifest files. For example, cmake -Dallow_versions=8.0.50608.0 -PCmakeVerifyManifest.cmake could be used to allow an embeded manifest of 8.0.50608.0 to be used in a project even if that version was not found in the .manifest file.
</li>
<li>
<a name="module:CPack"><b><code>CPack</code></b></a>: Build binary and source package installers<br>
<p><br><p>The CPack module generates binary and source installers in a variety of formats using the cpack program. Inclusion of the CPack module adds two new targets to the resulting makefiles, package and package_source, which build the binary and source installers, respectively. The generated binary installers contain everything installed via CMake's INSTALL command (and the deprecated INSTALL_FILES, INSTALL_PROGRAMS, and INSTALL_TARGETS commands).<br><p>For certain kinds of binary installers (including the graphical installers on Mac OS X and Windows), CPack generates installers that allow users to select individual application components to install. The contents of each of the components are identified by the COMPONENT argument of CMake's INSTALL command. These components can be annotated with user-friendly names and descriptions, inter-component dependencies, etc., and grouped in various ways to customize the resulting installer. See the cpack_add_* commands, described below, for more information about component-specific installations.<br><p>Before including the CPack module, there are a variety of variables that can be set to customize the resulting installers. The most commonly-used variables are:<br><pre> CPACK_PACKAGE_NAME - The name of the package (or application). If<br> not specified, defaults to the project name.<br></pre>
<p><br><pre> CPACK_PACKAGE_VENDOR - The name of the package vendor (e.g.,<br> "Kitware").<br></pre>
<p><br><pre> CPACK_PACKAGE_VERSION_MAJOR - Package major Version<br></pre>
<p><br><pre> CPACK_PACKAGE_VERSION_MINOR - Package minor Version<br></pre>
<p><br><pre> CPACK_PACKAGE_VERSION_PATCH - Package patch Version<br></pre>
<p><br><pre> CPACK_PACKAGE_DESCRIPTION_FILE - A text file used to describe the<br> project. Used, for example, the introduction screen of a<br> CPack-generated Windows installer to describe the project.<br></pre>
<p><br><pre> CPACK_PACKAGE_DESCRIPTION_SUMMARY - Short description of the<br> project (only a few words).<br></pre>
<p><br><pre> CPACK_PACKAGE_FILE_NAME - The name of the package file to generate,<br> not including the extension. For example, cmake-2.6.1-Linux-i686.<br></pre>
<p><br><pre> CPACK_PACKAGE_INSTALL_DIRECTORY - Installation directory on the<br> target system, e.g., "CMake 2.5".<br></pre>
<p><br><pre> CPACK_RESOURCE_FILE_LICENSE - License file for the project, which<br> will typically be displayed to the user (often with an explicit<br> "Accept" button, for graphical installers) prior to installation.<br></pre>
<p><br><pre> CPACK_RESOURCE_FILE_README - ReadMe file for the project, which<br> typically describes in some detail<br></pre>
<p><br><pre> CPACK_RESOURCE_FILE_WELCOME - Welcome file for the project, which<br> welcomes users to this installer. Typically used in the graphical<br> installers on Windows and Mac OS X.<br></pre>
<p><br><pre> CPACK_MONOLITHIC_INSTALL - Disables the component-based <br> installation mechanism, so that all components are always installed.<br></pre>
<p><br><pre> CPACK_GENERATOR - List of CPack generators to use. If not<br> specified, CPack will create a set of options (e.g.,<br> CPACK_BINARY_NSIS) allowing the user to enable/disable individual<br> generators.<br></pre>
<p><br><pre> CPACK_OUTPUT_CONFIG_FILE - The name of the CPack configuration file<br> for binary installers that will be generated by the CPack<br> module. Defaults to CPackConfig.cmake.<br></pre>
<p><br><pre> CPACK_PACKAGE_EXECUTABLES - Lists each of the executables along<br> with a text label, to be used to create Start Menu shortcuts on<br> Windows. For example, setting this to the list ccmake;CMake will<br> create a shortcut named "CMake" that will execute the installed<br> executable ccmake.<br></pre>
<p><br><pre> CPACK_STRIP_FILES - List of files to be stripped. Starting with<br> CMake 2.6.0 CPACK_STRIP_FILES will be a boolean variable which<br> enables stripping of all files (a list of files evaluates to TRUE<br> in CMake, so this change is compatible).<br></pre>
<p><br><p>The following CPack variables are specific to source packages, and will not affect binary packages:<br><pre> CPACK_SOURCE_PACKAGE_FILE_NAME - The name of the source package,<br> e.g., cmake-2.6.1<br></pre>
<p><br><pre> CPACK_SOURCE_STRIP_FILES - List of files in the source tree that<br> will be stripped. Starting with CMake 2.6.0<br> CPACK_SOURCE_STRIP_FILES will be a boolean variable which enables<br> stripping of all files (a list of files evaluates to TRUE in CMake,<br> so this change is compatible).<br></pre>
<p><br><pre> CPACK_SOURCE_GENERATOR - List of generators used for the source<br> packages. As with CPACK_GENERATOR, if this is not specified then<br> CPack will create a set of options (e.g., CPACK_SOURCE_ZIP)<br> allowing users to select which packages will be generated.<br></pre>
<p><br><pre> CPACK_SOURCE_OUTPUT_CONFIG_FILE - The name of the CPack<br> configuration file for source installers that will be generated by<br> the CPack module. Defaults to CPackSourceConfig.cmake.<br></pre>
<p><br><pre> CPACK_SOURCE_IGNORE_FILES - Pattern of files in the source tree<br> that won't be packaged when building a source package. This is a<br> list of patterns, e.g., /CVS/;/\\.svn/;\\.swp$;\\.#;/#;.*~;cscope.*<br></pre>
<p><br><p>The following variables are specific to the graphical installers built on Windows using the Nullsoft Installation System.<br><pre> CPACK_PACKAGE_INSTALL_REGISTRY_KEY - Registry key used when<br> installing this project.<br></pre>
<p><br><pre> CPACK_NSIS_MUI_ICON - The icon file (.ico) for the generated<br> install program.<br></pre>
<p><br><pre> CPACK_NSIS_MUI_UNIICON - The icon file (.ico) for the generated<br> uninstall program.<br></pre>
<p><br><pre> CPACK_PACKAGE_ICON - A branding image that will be displayed inside<br> the installer.<br></pre>
<p><br><pre> CPACK_NSIS_EXTRA_INSTALL_COMMANDS - Extra NSIS commands that will<br> be added to the install Section.<br></pre>
<p><br><pre> CPACK_NSIS_EXTRA_UNINSTALL_COMMANDS - Extra NSIS commands that will<br> be added to the uninstall Section.<br></pre>
<p><br><pre> CPACK_NSIS_COMPRESSOR - The arguments that will be passed to the<br> NSIS SetCompressor command.<br></pre>
<p><br><pre> CPACK_NSIS_MODIFY_PATH - If this is set to "ON", then an extra page<br> will appear in the installer that will allow the user to choose<br> whether the program directory should be added to the system PATH<br> variable.<br></pre>
<p><br><pre> CPACK_NSIS_DISPLAY_NAME - The display name string that appears in<br> the Windows Add/Remove Program control panel<br></pre>
<p><br><pre> CPACK_NSIS_PACKAGE_NAME - The title displayed at the top of the<br> installer.<br></pre>
<p><br><pre> CPACK_NSIS_INSTALLED_ICON_NAME - A path to the executable that<br> contains the installer icon.<br></pre>
<p><br><pre> CPACK_NSIS_HELP_LINK - URL to a web site providing assistance in<br> installing your application.<br></pre>
<p><br><pre> CPACK_NSIS_URL_INFO_ABOUT - URL to a web site providing more<br> information about your application.<br></pre>
<p><br><pre> CPACK_NSIS_CONTACT - Contact information for questions and comments<br> about the installation process.<br></pre>
<p><br><pre> CPACK_NSIS_CREATE_ICONS_EXTRA - Additional NSIS commands for<br> creating start menu shortcuts.<br></pre>
<p><br><pre> CPACK_NSIS_DELETE_ICONS_EXTRA -Additional NSIS commands to<br> uninstall start menu shortcuts.<br></pre>
<p><br><p>The following variable is specific to installers build on Mac OS X using PackageMaker:<br><pre> CPACK_OSX_PACKAGE_VERSION - The version of Mac OS X that the<br> resulting PackageMaker archive should be compatible<br> with. Different versions of Mac OS X support different<br> features. For example, CPack can only build component-based<br> installers for Mac OS X 10.4 or newer, and can only build<br> installers that download component son-the-fly for Mac OS X 10.5<br> or newer. If left blank, this value will be set to the minimum<br> version of Mac OS X that supports the requested features. Set this<br> variable to some value (e.g., 10.4) only if you want to guarantee<br> that your installer will work on that version of Mac OS X, and<br> don't mind missing extra features available in the installer<br> shipping with later versions of Mac OS X.<br></pre>
<p><br><p>The following variables are for advanced uses of CPack:<br><pre> CPACK_CMAKE_GENERATOR - What CMake generator should be used if the<br> project is CMake project. Defaults to the value of CMAKE_GENERATOR;<br> few users will want to change this setting.<br></pre>
<p><br><pre> CPACK_INSTALL_CMAKE_PROJECTS - List of four values that specify<br> what project to install. The four values are: Build directory,<br> Project Name, Project Component, Directory. If omitted, CPack will<br> build an installer that installers everything.<br></pre>
<p><br><pre> CPACK_SYSTEM_NAME - System name, defaults to the value of<br> ${CMAKE_SYSTEM_NAME}.<br></pre>
<p><br><pre> CPACK_PACKAGE_VERSION - Package full version, used internally. By<br> default, this is built from CPACK_PACKAGE_VERSION_MAJOR,<br> CPACK_PACKAGE_VERSION_MINOR, and CPACK_PACKAGE_VERSION_PATCH.<br></pre>
<p><br><pre> CPACK_TOPLEVEL_TAG - Directory for the installed files.<br></pre>
<p><br><pre> CPACK_INSTALL_COMMANDS - Extra commands to install components.<br></pre>
<p><br><pre> CPACK_INSTALL_DIRECTORIES - Extra directories to install.<br></pre>
<p><br><p>Component-specific installation allows users to select specific sets of components to install during the install process. Installation components are identified by the COMPONENT argument of CMake's INSTALL commands, and should be further described by the following CPack commands:<br><pre> cpack_add_component - Describes a CPack installation component<br> named by the COMPONENT argument to a CMake INSTALL command.<br></pre>
<p><br><pre> cpack_add_component(compname<br> [DISPLAY_NAME name]<br> [DESCRIPTION description]<br> [HIDDEN | REQUIRED | DISABLED ]<br> [GROUP group]<br> [DEPENDS comp1 comp2 ... ]<br> [INSTALL_TYPES type1 type2 ... ]<br> [DOWNLOADED]<br> [ARCHIVE_FILE filename])<br></pre>
<p><br><pre> The cmake_add_component command describes an installation<br> component, which the user can opt to install or remove as part of<br> the graphical installation process. compname is the name of the<br> component, as provided to the COMPONENT argument of one or more<br> CMake INSTALL commands.<br></pre>
<p><br><pre> DISPLAY_NAME is the displayed name of the component, used in<br> graphical installers to display the component name. This value can<br> be any string.<br></pre>
<p><br><pre> DESCRIPTION is an extended description of the component, used in<br> graphical installers to give the user additional information about<br> the component. Descriptions can span multiple lines using "\n" as<br> the line separator. Typically, these descriptions should be no<br> more than a few lines long.<br></pre>
<p><br><pre> HIDDEN indicates that this component will be hidden in the<br> graphical installer, so that the user cannot directly change<br> whether it is installed or not.<br></pre>
<p><br><pre> REQUIRED indicates that this component is required, and therefore<br> will always be installed. It will be visible in the graphical<br> installer, but it cannot be unselected. (Typically, required<br> components are shown greyed out).<br></pre>
<p><br><pre> DISABLED indicates that this component should be disabled<br> (unselected) by default. The user is free to select this component<br> for installation, unless it is also HIDDEN.<br></pre>
<p><br><pre> DEPENDS lists the components on which this component depends. If<br> this component is selected, then each of the components listed<br> must also be selected. The dependency information is encoded<br> within the installer itself, so that users cannot install<br> inconsitent sets of components.<br></pre>
<p><br><pre> GROUP names the component group of which this component is a<br> part. If not provided, the component will be a standalone<br> component, not part of any component group. Component groups are<br> described with the cpack_add_component_group command, detailed<br> below.<br></pre>
<p><br><pre> INSTALL_TYPES lists the installation types of which this component<br> is a part. When one of these installations types is selected, this<br> component will automatically be selected. Installation types are<br> described with the cpack_add_install_type command, detailed below.<br></pre>
<p><br><pre> DOWNLOADED indicates that this component should be downloaded<br> on-the-fly by the installer, rather than packaged in with the<br> installer itself. For more information, see the cpack_configure_downloads<br> command.<br></pre>
<p><br><pre> ARCHIVE_FILE provides a name for the archive file created by CPack<br> to be used for downloaded components. If not supplied, CPack will<br> create a file with some name based on CPACK_PACKAGE_FILE_NAME and<br> the name of the component. See cpack_configure_downloads for more<br> information.<br></pre>
<p><br><pre> cpack_add_component_group - Describes a group of related CPack<br> installation components.<br></pre>
<p><br><pre> cpack_add_component_group(groupname<br> [DISPLAY_NAME name]<br> [DESCRIPTION description]<br> [PARENT_GROUP parent]<br> [EXPANDED]<br> [BOLD_TITLE])<br></pre>
<p><br><pre> The cpack_add_component_group describes a group of installation<br> components, which will be placed together within the listing of<br> options. Typically, component groups allow the user to<br> select/deselect all of the components within a single group via a<br> single group-level option. Use component groups to reduce the<br> complexity of installers with many options. groupname is an<br> arbitrary name used to identify the group in the GROUP argument of<br> the cpack_add_component command, which is used to place a<br> component in a group. The name of the group must not conflict with<br> the name of any component.<br></pre>
<p><br><pre> DISPLAY_NAME is the displayed name of the component group, used in<br> graphical installers to display the component group name. This<br> value can be any string.<br></pre>
<p><br><pre> DESCRIPTION is an extended description of the component group,<br> used in graphical installers to give the user additional<br> information about the components within that group. Descriptions<br> can span multiple lines using "\n" as the line<br> separator. Typically, these descriptions should be no more than a<br> few lines long.<br></pre>
<p><br><pre> PARENT_GROUP, if supplied, names the parent group of this group. <br> Parent groups are used to establish a hierarchy of groups, <br> providing an arbitrary hierarchy of groups.<br></pre>
<p><br><pre> EXPANDED indicates that, by default, the group should show up as<br> "expanded", so that the user immediately sees all of the<br> components within the group. Otherwise, the group will initially<br> show up as a single entry.<br></pre>
<p><br><pre> BOLD_TITLE indicates that the group title should appear in bold,<br> to call the user's attention to the group.<br></pre>
<p><br><pre> cpack_add_install_type - Add a new installation type containing a<br> set of predefined component selections to the graphical installer.<br> <br> cpack_add_install_type(typename<br> [DISPLAY_NAME name]) <br></pre>
<p><br><pre> The cpack_add_install_type command identifies a set of preselected<br> components that represents a common use case for an<br> application. For example, a "Developer" install type might include<br> an application along with its header and library files, while an<br> "End user" install type might just include the application's<br> executable. Each component identifies itself with one or more<br> install types via the INSTALL_TYPES argument to<br> cpack_add_component.<br></pre>
<p><br><pre> DISPLAY_NAME is the displayed name of the install type, which will<br> typically show up in a drop-down box within a graphical<br> installer. This value can be any string.<br></pre>
<p><br><pre> cpack_configure_downloads - Configure CPack to download selected<br> components on-the-fly as part of the installation process.<br></pre>
<p><br><pre> cpack_configure_downloads(site<br> [UPLOAD_DIRECTORY dirname]<br> [ALL]<br> [ADD_REMOVE|NO_ADD_REMOVE])<br></pre>
<p><br><pre> The cpack_configure_downloads command configures installation-time<br> downloads of selected components. For each downloadable component,<br> CPack will create an archive containing the contents of that<br> component, which should be uploaded to the given site. When the<br> user selects that component for installation, the installer will<br> download and extract the component in place. This feature is<br> useful for creating small installers that only download the<br> requested components, saving bandwidth. Additionally, the<br> installers are small enough that they will be installed as part of<br> the normal installation process, and the "Change" button in<br> Windows Add/Remove Programs control panel will allow one to add or<br> remove parts of the application after the original<br> installation. On Windows, the downloaded-components functionality<br> requires the ZipDLL plug-in for NSIS, available at:<br></pre>
<p><br><pre> <a href="http://nsis.sourceforge.net/ZipDLL_plug-in">http://nsis.sourceforge.net/ZipDLL_plug-in</a><br></pre>
<p><br><pre> On Mac OS X, installers that download components on-the-fly can<br> only be built and installed on system using Mac OS X 10.5 or<br> later.<br></pre>
<p><br><pre> The site argument is a URL where the archives for downloadable <br> components will reside, e.g., <a href="http://www.cmake.org/files/2.6.1/installer/">http://www.cmake.org/files/2.6.1/installer/</a><br> All of the archives produced by CPack should be uploaded to that location.<br></pre>
<p><br><pre> UPLOAD_DIRECTORY is the local directory where CPack will create the <br> various archives for each of the components. The contents of this<br> directory should be uploaded to a location accessible by the URL given<br> in the site argument. If omitted, CPack will use the directory <br> CPackUploads inside the CMake binary directory to store the generated<br> archives.<br></pre>
<p><br><pre> The ALL flag indicates that all components be downloaded. Otherwise, only <br> those components explicitly marked as DOWNLOADED or that have a specified <br> ARCHIVE_FILE will be downloaded. Additionally, the ALL option implies<br> ADD_REMOVE (unless NO_ADD_REMOVE is specified).<br></pre>
<p><br><pre> ADD_REMOVE indicates that CPack should install a copy of the installer<br> that can be called from Windows' Add/Remove Programs dialog (via the <br> "Modify" button) to change the set of installed components. NO_ADD_REMOVE<br> turns off this behavior. This option is ignored on Mac OS X.<br></pre>
</li>
<li>
<a name="module:CPackDeb"><b><code>CPackDeb</code></b></a>: The builtin (binary) CPack Deb generator (Unix only)<br>
<p>CPackDeb may be used to create Deb package using CPack. CPackDeb is a CPack generator thus it uses the CPACK_XXX variables used by CPack : <a href="http://www.cmake.org/Wiki/CMake:CPackConfiguration">http://www.cmake.org/Wiki/CMake:CPackConfiguration</a><br><p>However CPackRPM has specific features which are controlled by the specifics CPACK_RPM_XXX variables.You'll find a detailed usage on the wiki: <br><pre> <a href="http://www.cmake.org/Wiki/CMake:CPackPackageGenerators">http://www.cmake.org/Wiki/CMake:CPackPackageGenerators</a>#DEB_.28UNIX_only.29<br></pre>
<p>However as a handy reminder here comes the list of specific variables:<br><pre> CPACK_DEBIAN_PACKAGE_NAME<br> Mandatory : YES<br> Default : CPACK_PACKAGE_NAME (lower case)<br> The debian package summary<br></pre>
<p>CPACK_DEBIAN_PACKAGE_VERSION<br><pre> Mandatory : YES<br> Default : CPACK_PACKAGE_VERSION<br> The debian package version<br></pre>
<p>CPACK_DEBIAN_PACKAGE_ARCHITECTURE)<br><pre> Mandatory : YES<br> Default : Output of dpkg --print-architecture or i386<br> The debian package architecture<br></pre>
<p>CPACK_DEBIAN_PACKAGE_DEPENDS<br><pre> Mandatory : NO<br> Default : -<br> May be used to set deb dependencies. <br></pre>
<p>CPACK_DEBIAN_PACKAGE_MAINTAINER<br><pre> Mandatory : YES<br> Default : CPACK_PACKAGE_CONTACT<br> The debian package maintainer<br></pre>
<p>CPACK_DEBIAN_PACKAGE_DESCRIPTION<br><pre> Mandatory : YES<br> Default : CPACK_PACKAGE_DESCRIPTION_SUMMARY<br> The debian package description<br></pre>
<p>CPACK_DEBIAN_PACKAGE_SECTION<br><pre> Mandatory : YES<br> Default : 'devel'<br> The debian package section<br></pre>
<p>CPACK_DEBIAN_PACKAGE_PRIORITY<br><pre> Mandatory : YES<br> Default : 'optional'<br> The debian package priority<br></pre>
</li>
<li>
<a name="module:CPackRPM"><b><code>CPackRPM</code></b></a>: The builtin (binary) CPack RPM generator (Unix only)<br>
<p>CPackRPM may be used to create RPM package using CPack. CPackRPM is a CPack generator thus it uses the CPACK_XXX variables used by CPack : <a href="http://www.cmake.org/Wiki/CMake:CPackConfiguration">http://www.cmake.org/Wiki/CMake:CPackConfiguration</a><br><p>However CPackRPM has specific features which are controlled by the specifics CPACK_RPM_XXX variables.You'll find a detailed usage on the wiki: <br><pre> <a href="http://www.cmake.org/Wiki/CMake:CPackPackageGenerators">http://www.cmake.org/Wiki/CMake:CPackPackageGenerators</a>#RPM_.28Unix_Only.29<br></pre>
<p>However as a handy reminder here comes the list of specific variables:<br><pre> CPACK_RPM_PACKAGE_SUMMARY <br> Mandatory : YES<br> Default : CPACK_PACKAGE_DESCRIPTION<br> The RPM package summary<br> CPACK_RPM_PACKAGE_NAME<br> Mandatory : YES<br> Default : CPACK_PACKAGE_NAME<br> The RPM package name<br> CPACK_RPM_PACKAGE_VERSION<br> Mandatory : YES<br> Default : CPACK_PACKAGE_VERSION<br> The RPM package version<br> CPACK_RPM_PACKAGE_ARCHITECTURE<br> Mandatory : NO<br> Default : -<br> The RPM package architecture. This may be set to "noarch" if you <br> know you are building a noarch package.<br> CPACK_RPM_PACKAGE_RELEASE<br> Mandatory : YES<br> Default : 1<br> The RPM package release. This is the numbering of the RPM package <br> itself, i.e. the version of the packaging and not the version of the <br> content (see CPACK_RPM_PACKAGE_VERSION). One may change the default <br> value if the previous packaging was buggy and/or you want to put here<br> a fancy Linux distro specific numbering.<br> CPACK_RPM_PACKAGE_LICENSE<br> Mandatory : YES<br> Default : "unknown"<br> The RPM package license policy.<br> CPACK_RPM_PACKAGE_GROUP<br> Mandatory : YES<br> Default : "unknown"<br> The RPM package group.<br> CPACK_RPM_PACKAGE_VENDOR <br> Mandatory : YES<br> Default : CPACK_PACKAGE_VENDOR if set or"unknown"<br> The RPM package group.<br> CPACK_RPM_PACKAGE_DESCRIPTION<br> Mandatory : YES<br> Default : CPACK_PACKAGE_DESCRIPTION_FILE if set or "no package description available"<br> CPACK_RPM_PACKAGE_REQUIRES<br> Mandatory : NO<br> Default : -<br> May be used to set RPM dependencies. <br> CPACK_RPM_SPEC_INSTALL_POST<br> Mandatory : NO<br> Default : -<br> May be used to set an RPM post-install command inside the spec file. <br> For example setting it to "/bin/true" may be used to prevent <br> rpmbuild to strip binaries.<br> CPACK_RPM_SPEC_MORE_DEFINE<br> Mandatory : NO<br> Default : -<br> May be used to add any %define lines to the generated spec file.<br> CPACK_RPM_PACKAGE_DEBUG<br> Mandatory : NO<br> Default : -<br> May be set when invoking cpack in order to trace debug informations <br> during CPack RPM run. For example you may launch CPack like this <br> cpack -D CPACK_RPM_PACKAGE_DEBUG=1 -G RPM<br></pre>
</li>
<li>
<a name="module:CTest"><b><code>CTest</code></b></a>: Configure a project for testing with CTest/CDash<br>
<p>This file configures a project to use the CTest/CDash/Dart testing/dashboard process. This module should be included in the CMakeLists.txt file at the top of a project. Typical usage:<br><pre> INCLUDE(CTest)<br> IF(BUILD_TESTING)<br> # ... testing related CMake code ...<br> ENDIF(BUILD_TESTING)<br></pre>
<p>The BUILD_TESTING option is created by the CTest module to determine whether testing support should be enabled. The default is ON.
</li>
<li>
<a name="module:CTestScriptMode"><b><code>CTestScriptMode</code></b></a>: <br>
<p>This file is read by ctest in script mode (-S)
</li>
<li>
<a name="module:CheckCCompilerFlag"><b><code>CheckCCompilerFlag</code></b></a>: Check whether the C compiler supports a given flag.<br>
<p>CHECK_C_COMPILER_FLAG(&lt;flag&gt; &lt;var&gt;)<br><pre> &lt;flag&gt; - the compiler flag<br> &lt;var&gt; - variable to store the result<br></pre>
<p>This internally calls the check_c_source_compiles macro. See help for CheckCSourceCompiles for a listing of variables that can modify the build.
</li>
<li>
<a name="module:CheckCSourceCompiles"><b><code>CheckCSourceCompiles</code></b></a>: Check if the given C source code compiles.<br>
<p>CHECK_C_SOURCE_COMPILES(&lt;code&gt; &lt;var&gt; [FAIL_REGEX &lt;fail-regex&gt;])<br><pre> &lt;code&gt; - source code to try to compile<br> &lt;var&gt; - variable to store whether the source code compiled<br> &lt;fail-regex&gt; - fail if test output matches this regex<br></pre>
<p>The following variables may be set before calling this macro to modify the way the check is run:<br><pre> CMAKE_REQUIRED_FLAGS = string of compile command line flags<br> CMAKE_REQUIRED_DEFINITIONS = list of macros to define (-DFOO=bar)<br> CMAKE_REQUIRED_INCLUDES = list of include directories<br> CMAKE_REQUIRED_LIBRARIES = list of libraries to link<br></pre>
</li>
<li>
<a name="module:CheckCSourceRuns"><b><code>CheckCSourceRuns</code></b></a>: Check if the given C source code compiles and runs.<br>
<p>CHECK_C_SOURCE_RUNS(&lt;code&gt; &lt;var&gt;)<br><pre> &lt;code&gt; - source code to try to compile<br> &lt;var&gt; - variable to store the result<br> (1 for success, empty for failure)<br></pre>
<p>The following variables may be set before calling this macro to modify the way the check is run:<br><pre> CMAKE_REQUIRED_FLAGS = string of compile command line flags<br> CMAKE_REQUIRED_DEFINITIONS = list of macros to define (-DFOO=bar)<br> CMAKE_REQUIRED_INCLUDES = list of include directories<br> CMAKE_REQUIRED_LIBRARIES = list of libraries to link<br></pre>
</li>
<li>
<a name="module:CheckCXXCompilerFlag"><b><code>CheckCXXCompilerFlag</code></b></a>: Check whether the CXX compiler supports a given flag.<br>
<p>CHECK_CXX_COMPILER_FLAG(&lt;flag&gt; &lt;var&gt;)<br><pre> &lt;flag&gt; - the compiler flag<br> &lt;var&gt; - variable to store the result<br></pre>
<p>This internally calls the check_cxx_source_compiles macro. See help for CheckCXXSourceCompiles for a listing of variables that can modify the build.
</li>
<li>
<a name="module:CheckCXXSourceCompiles"><b><code>CheckCXXSourceCompiles</code></b></a>: Check if the given C++ source code compiles.<br>
<p>CHECK_CXX_SOURCE_COMPILES(&lt;code&gt; &lt;var&gt; [FAIL_REGEX &lt;fail-regex&gt;])<br><pre> &lt;code&gt; - source code to try to compile<br> &lt;var&gt; - variable to store whether the source code compiled<br> &lt;fail-regex&gt; - fail if test output matches this regex<br></pre>
<p>The following variables may be set before calling this macro to modify the way the check is run:<br><pre> CMAKE_REQUIRED_FLAGS = string of compile command line flags<br> CMAKE_REQUIRED_DEFINITIONS = list of macros to define (-DFOO=bar)<br> CMAKE_REQUIRED_INCLUDES = list of include directories<br> CMAKE_REQUIRED_LIBRARIES = list of libraries to link<br></pre>
</li>
<li>
<a name="module:CheckCXXSourceRuns"><b><code>CheckCXXSourceRuns</code></b></a>: Check if the given C++ source code compiles and runs.<br>
<p>CHECK_CXX_SOURCE_RUNS(&lt;code&gt; &lt;var&gt;)<br><pre> &lt;code&gt; - source code to try to compile<br> &lt;var&gt; - variable to store the result<br> (1 for success, empty for failure)<br></pre>
<p>The following variables may be set before calling this macro to modify the way the check is run:<br><pre> CMAKE_REQUIRED_FLAGS = string of compile command line flags<br> CMAKE_REQUIRED_DEFINITIONS = list of macros to define (-DFOO=bar)<br> CMAKE_REQUIRED_INCLUDES = list of include directories<br> CMAKE_REQUIRED_LIBRARIES = list of libraries to link<br></pre>
</li>
<li>
<a name="module:CheckFortranFunctionExists"><b><code>CheckFortranFunctionExists</code></b></a>: macro which checks if the Fortran function exists<br>
<p>CHECK_FORTRAN_FUNCTION_EXISTS(FUNCTION VARIABLE)<br><pre> FUNCTION - the name of the Fortran function<br> VARIABLE - variable to store the result<br></pre>
<p><br><p>The following variables may be set before calling this macro to modify the way the check is run:<br><pre> CMAKE_REQUIRED_LIBRARIES = list of libraries to link<br></pre>
</li>
<li>
<a name="module:CheckFunctionExists"><b><code>CheckFunctionExists</code></b></a>: macro which checks if the function exists<br>
<p>CHECK_FUNCTION_EXISTS(FUNCTION VARIABLE)<br><pre> FUNCTION - the name of the function<br> VARIABLE - variable to store the result<br></pre>
<p><br><p>The following variables may be set before calling this macro to modify the way the check is run:<br><pre> CMAKE_REQUIRED_FLAGS = string of compile command line flags<br> CMAKE_REQUIRED_DEFINITIONS = list of macros to define (-DFOO=bar)<br> CMAKE_REQUIRED_INCLUDES = list of include directories<br> CMAKE_REQUIRED_LIBRARIES = list of libraries to link<br></pre>
</li>
<li>
<a name="module:CheckIncludeFile"><b><code>CheckIncludeFile</code></b></a>: macro which checks the include file exists.<br>
<p>CHECK_INCLUDE_FILE(INCLUDE VARIABLE)<br><pre> INCLUDE - name of include file<br> VARIABLE - variable to return result<br> <br></pre>
<p>an optional third argument is the CFlags to add to the compile line or you can use CMAKE_REQUIRED_FLAGS<br><p>The following variables may be set before calling this macro to modify the way the check is run:<br><pre> CMAKE_REQUIRED_FLAGS = string of compile command line flags<br> CMAKE_REQUIRED_DEFINITIONS = list of macros to define (-DFOO=bar)<br> CMAKE_REQUIRED_INCLUDES = list of include directories<br></pre>
<p><br>
</li>
<li>
<a name="module:CheckIncludeFileCXX"><b><code>CheckIncludeFileCXX</code></b></a>: Check if the include file exists.<br>
<pre> CHECK_INCLUDE_FILE_CXX(INCLUDE VARIABLE)<br></pre>
<p><br><pre> INCLUDE - name of include file<br> VARIABLE - variable to return result<br> <br></pre>
<p>An optional third argument is the CFlags to add to the compile line or you can use CMAKE_REQUIRED_FLAGS.<br><p>The following variables may be set before calling this macro to modify the way the check is run:<br><pre> CMAKE_REQUIRED_FLAGS = string of compile command line flags<br> CMAKE_REQUIRED_DEFINITIONS = list of macros to define (-DFOO=bar)<br> CMAKE_REQUIRED_INCLUDES = list of include directories<br></pre>
<p><br>
</li>
<li>
<a name="module:CheckIncludeFiles"><b><code>CheckIncludeFiles</code></b></a>: Check if the files can be included<br>
<p><br><p>CHECK_INCLUDE_FILES(INCLUDE VARIABLE)<br><pre> INCLUDE - list of files to include<br> VARIABLE - variable to return result<br></pre>
<p><br><p>The following variables may be set before calling this macro to modify the way the check is run:<br><pre> CMAKE_REQUIRED_FLAGS = string of compile command line flags<br> CMAKE_REQUIRED_DEFINITIONS = list of macros to define (-DFOO=bar)<br> CMAKE_REQUIRED_INCLUDES = list of include directories<br></pre>
</li>
<li>
<a name="module:CheckLibraryExists"><b><code>CheckLibraryExists</code></b></a>: Check if the function exists.<br>
<p>CHECK_LIBRARY_EXISTS (LIBRARY FUNCTION LOCATION VARIABLE)<br><pre> LIBRARY - the name of the library you are looking for<br> FUNCTION - the name of the function<br> LOCATION - location where the library should be found<br> VARIABLE - variable to store the result<br></pre>
<p><br><p>The following variables may be set before calling this macro to modify the way the check is run:<br><pre> CMAKE_REQUIRED_FLAGS = string of compile command line flags<br> CMAKE_REQUIRED_DEFINITIONS = list of macros to define (-DFOO=bar)<br> CMAKE_REQUIRED_LIBRARIES = list of libraries to link<br></pre>
</li>
<li>
<a name="module:CheckStructHasMember"><b><code>CheckStructHasMember</code></b></a>: Check if the given struct or class has the specified member variable<br>
<p>CHECK_STRUCT_HAS_MEMBER (STRUCT MEMBER HEADER VARIABLE)<br><pre> STRUCT - the name of the struct or class you are interested in<br> MEMBER - the member which existence you want to check<br> HEADER - the header(s) where the prototype should be declared<br> VARIABLE - variable to store the result<br></pre>
<p><br><p>The following variables may be set before calling this macro to modify the way the check is run:<br><pre> CMAKE_REQUIRED_FLAGS = string of compile command line flags<br> CMAKE_REQUIRED_DEFINITIONS = list of macros to define (-DFOO=bar)<br> CMAKE_REQUIRED_INCLUDES = list of include directories<br></pre>
<p><br><p>Example: CHECK_STRUCT_HAS_MEMBER("struct timeval" tv_sec sys/select.h HAVE_TIMEVAL_TV_SEC)
</li>
<li>
<a name="module:CheckSymbolExists"><b><code>CheckSymbolExists</code></b></a>: Check if the symbol exists in include files<br>
<p>CHECK_SYMBOL_EXISTS(SYMBOL FILES VARIABLE)<br><pre> SYMBOL - symbol<br> FILES - include files to check<br> VARIABLE - variable to return result<br></pre>
<p><br><p>The following variables may be set before calling this macro to modify the way the check is run:<br><pre> CMAKE_REQUIRED_FLAGS = string of compile command line flags<br> CMAKE_REQUIRED_DEFINITIONS = list of macros to define (-DFOO=bar)<br> CMAKE_REQUIRED_INCLUDES = list of include directories<br> CMAKE_REQUIRED_LIBRARIES = list of libraries to link<br></pre>
</li>
<li>
<a name="module:CheckTypeSize"><b><code>CheckTypeSize</code></b></a>: Check sizeof a type<br>
<pre> CHECK_TYPE_SIZE(TYPE VARIABLE [BUILTIN_TYPES_ONLY])<br></pre>
<p>Check if the type exists and determine size of type. if the type exists, the size will be stored to the variable. This also calls check_include_file for sys/types.h stdint.h and stddef.h, setting HAVE_SYS_TYPES_H, HAVE_STDINT_H, and HAVE_STDDEF_H. This is because many types are stored in these include files. <br><pre> VARIABLE - variable to store size if the type exists.<br> HAVE_${VARIABLE} - does the variable exists or not<br> BUILTIN_TYPES_ONLY - The third argument is optional and if <br> it is set to the string BUILTIN_TYPES_ONLY<br> this macro will not check for any header files.<br></pre>
<p>The following variables may be set before calling this macro to modify the way the check is run:<br><pre> CMAKE_REQUIRED_FLAGS = string of compile command line flags<br> CMAKE_REQUIRED_DEFINITIONS = list of macros to define (-DFOO=bar)<br> CMAKE_REQUIRED_INCLUDES = list of include directories<br> CMAKE_REQUIRED_LIBRARIES = list of libraries to link<br></pre>
</li>
<li>
<a name="module:CheckVariableExists"><b><code>CheckVariableExists</code></b></a>: Check if the variable exists.<br>
<pre> CHECK_VARIABLE_EXISTS(VAR VARIABLE)<br> <br> VAR - the name of the variable<br> VARIABLE - variable to store the result<br></pre>
<p><br><p>This macro is only for C variables.<br><p>The following variables may be set before calling this macro to modify the way the check is run:<br><pre> CMAKE_REQUIRED_FLAGS = string of compile command line flags<br> CMAKE_REQUIRED_DEFINITIONS = list of macros to define (-DFOO=bar)<br> CMAKE_REQUIRED_LIBRARIES = list of libraries to link<br></pre>
</li>
<li>
<a name="module:Dart"><b><code>Dart</code></b></a>: Configure a project for testing with CTest or old Dart Tcl Client<br>
<p>This file is the backwards-compatibility version of the CTest module. It supports using the old Dart 1 Tcl client for driving dashboard submissions as well as testing with CTest. This module should be included in the CMakeLists.txt file at the top of a project. Typical usage:<br><pre> INCLUDE(Dart)<br> IF(BUILD_TESTING)<br> # ... testing related CMake code ...<br> ENDIF(BUILD_TESTING)<br></pre>
<p>The BUILD_TESTING option is created by the Dart module to determine whether testing support should be enabled. The default is ON.
</li>
<li>
<a name="module:Documentation"><b><code>Documentation</code></b></a>: DocumentationVTK.cmake<br>
<p>This file provides support for the VTK documentation framework. It relies on several tools (Doxygen, Perl, etc).
</li>
<li>
<a name="module:ExternalProject"><b><code>ExternalProject</code></b></a>: Create custom targets to build projects in external trees<br>
<p>The 'ExternalProject_Add' function creates a custom target to drive download, update/patch, configure, build, install and test steps of an external project:<br><pre> ExternalProject_Add(&lt;name&gt; # Name for custom target<br> [DEPENDS projects...] # Targets on which the project depends<br> [PREFIX dir] # Root dir for entire project<br> [LIST_SEPARATOR sep] # Sep to be replaced by ; in cmd lines<br> [TMP_DIR dir] # Directory to store temporary files<br> [STAMP_DIR dir] # Directory to store step timestamps<br> #--Download step--------------<br> [DOWNLOAD_DIR dir] # Directory to store downloaded files<br> [DOWNLOAD_COMMAND cmd...] # Command to download source tree<br> [CVS_REPOSITORY cvsroot] # CVSROOT of CVS repository<br> [CVS_MODULE mod] # Module to checkout from CVS repo<br> [CVS_TAG tag] # Tag to checkout from CVS repo<br> [SVN_REPOSITORY url] # URL of Subversion repo<br> [SVN_REVISION rev] # Revision to checkout from Subversion repo<br> [URL /.../src.tgz] # Full path or URL of source<br> #--Update/Patch step----------<br> [UPDATE_COMMAND cmd...] # Source work-tree update command<br> [PATCH_COMMAND cmd...] # Command to patch downloaded source<br> #--Configure step-------------<br> [SOURCE_DIR dir] # Source dir to be used for build<br> [CONFIGURE_COMMAND cmd...] # Build tree configuration command<br> [CMAKE_COMMAND /.../cmake] # Specify alternative cmake executable<br> [CMAKE_GENERATOR gen] # Specify generator for native build<br> [CMAKE_ARGS args...] # Arguments to CMake command line<br> #--Build step-----------------<br> [BINARY_DIR dir] # Specify build dir location<br> [BUILD_COMMAND cmd...] # Command to drive the native build<br> [BUILD_IN_SOURCE 1] # Use source dir for build dir<br> #--Install step---------------<br> [INSTALL_DIR dir] # Installation prefix<br> [INSTALL_COMMAND cmd...] # Command to drive install after build<br> #--Test step---------------<br> [TEST_BEFORE_INSTALL 1] # Add test step executed before install step<br> [TEST_AFTER_INSTALL 1] # Add test step executed after install step<br> [TEST_COMMAND cmd...] # Command to drive test<br> )<br></pre>
<p>The *_DIR options specify directories for the project, with default directories computed as follows. If the PREFIX option is given to ExternalProject_Add() or the EP_PREFIX directory property is set, then an external project is built and installed under the specified prefix:<br><pre> TMP_DIR = &lt;prefix&gt;/tmp<br> STAMP_DIR = &lt;prefix&gt;/src/&lt;name&gt;-stamp<br> DOWNLOAD_DIR = &lt;prefix&gt;/src<br> SOURCE_DIR = &lt;prefix&gt;/src/&lt;name&gt;<br> BINARY_DIR = &lt;prefix&gt;/src/&lt;name&gt;-build<br> INSTALL_DIR = &lt;prefix&gt;<br></pre>
<p>Otherwise, if the EP_BASE directory property is set then components of an external project are stored under the specified base:<br><pre> TMP_DIR = &lt;base&gt;/tmp/&lt;name&gt;<br> STAMP_DIR = &lt;base&gt;/Stamp/&lt;name&gt;<br> DOWNLOAD_DIR = &lt;base&gt;/Download/&lt;name&gt;<br> SOURCE_DIR = &lt;base&gt;/Source/&lt;name&gt;<br> BINARY_DIR = &lt;base&gt;/Build/&lt;name&gt;<br> INSTALL_DIR = &lt;base&gt;/Install/&lt;name&gt;<br></pre>
<p>If no PREFIX, EP_PREFIX, or EP_BASE is specified then the default is to set PREFIX to "&lt;name&gt;-prefix". Relative paths are interpreted with respect to the build directory corresponding to the source directory in which ExternalProject_Add is invoked.<br><p>If SOURCE_DIR is explicitly set to an existing directory the project will be built from it. Otherwise a download step must be specified using one of the DOWNLOAD_COMMAND, CVS_*, SVN_*, or URL options. The URL option may refer locally to a directory or source tarball, or refer to a remote tarball (e.g. <a href="http://.../src.tgz">http://.../src.tgz</a>).<br><p>The 'ExternalProject_Add_Step' function adds a custom step to an external project:<br><pre> ExternalProject_Add_Step(&lt;name&gt; &lt;step&gt; # Names of project and custom step<br> [COMMAND cmd...] # Command line invoked by this step<br> [COMMENT "text..."] # Text printed when step executes<br> [DEPENDEES steps...] # Steps on which this step depends<br> [DEPENDERS steps...] # Steps that depend on this step<br> [DEPENDS files...] # Files on which this step depends<br> [ALWAYS 1] # No stamp file, step always runs<br> [WORKING_DIRECTORY dir] # Working directory for command<br> )<br></pre>
<p>The command line, comment, and working directory of every standard and custom step is processed to replace tokens &lt;SOURCE_DIR&gt;, &lt;BINARY_DIR&gt;, &lt;INSTALL_DIR&gt;, and &lt;TMP_DIR&gt; with corresponding property values.<br><p>The 'ExternalProject_Get_Property' function retrieves external project target properties:<br><pre> ExternalProject_Get_Property(&lt;name&gt; [prop1 [prop2 [...]]])<br></pre>
<p>It stores property values in variables of the same name. Property names correspond to the keyword argument names of 'ExternalProject_Add'.
</li>
<li>
<a name="module:FeatureSummary"><b><code>FeatureSummary</code></b></a>: Macros for generating a summary of enabled/disabled features<br>
<p><br><p>PRINT_ENABLED_FEATURES()<br><pre> Print a summary of all enabled features. By default all successfull<br> FIND_PACKAGE() calls will appear here, except the ones which used the<br> QUIET keyword. Additional features can be added by appending an entry<br> to the global ENABLED_FEATURES property. If SET_FEATURE_INFO() is<br> used for that feature, the output will be much more informative.<br></pre>
<p><br><p>PRINT_DISABLED_FEATURES()<br><pre> Same as PRINT_ENABLED_FEATURES(), but for disabled features. It can<br> be extended the same way by adding to the global property <br> DISABLED_FEATURES.<br></pre>
<p><br><p>SET_FEATURE_INFO(NAME DESCRIPTION [URL [COMMENT] ] )<br><pre> Use this macro to set up information about the named feature, which will<br> then be displayed by PRINT_ENABLED/DISABLED_FEATURES().<br> Example: SET_FEATURE_INFO(LibXml2 "XML processing library." <br> "<a href="http://xmlsoft.org/">http://xmlsoft.org/</a>")<br></pre>
<p><br>
</li>
<li>
<a name="module:FindALSA"><b><code>FindALSA</code></b></a>: Find alsa<br>
<p>Find the alsa libraries (asound)<br><pre> This module defines the following variables:<br> ALSA_FOUND - True if ALSA_INCLUDE_DIR &amp; ALSA_LIBRARY are found<br> ALSA_LIBRARIES - Set when ALSA_LIBRARY is found<br> ALSA_INCLUDE_DIRS - Set when ALSA_INCLUDE_DIR is found<br></pre>
<p><br><pre> ALSA_INCLUDE_DIR - where to find asoundlib.h, etc.<br> ALSA_LIBRARY - the asound library<br></pre>
<p><br>
</li>
<li>
<a name="module:FindASPELL"><b><code>FindASPELL</code></b></a>: Try to find ASPELL<br>
<p>Once done this will define<br><pre> ASPELL_FOUND - system has ASPELL<br> ASPELL_INCLUDE_DIR - the ASPELL include directory<br> ASPELL_LIBRARIES - The libraries needed to use ASPELL<br> ASPELL_DEFINITIONS - Compiler switches required for using ASPELL<br></pre>
</li>
<li>
<a name="module:FindAVIFile"><b><code>FindAVIFile</code></b></a>: Locate AVIFILE library and include paths<br>
<p>AVIFILE (<a href="http://avifile.sourceforge.net/">http://avifile.sourceforge.net/</a>)is a set of libraries for i386 machines to use various AVI codecs. Support is limited beyond Linux. Windows provides native AVI support, and so doesn't need this library. This module defines<br><pre> AVIFILE_INCLUDE_DIR, where to find avifile.h , etc.<br> AVIFILE_LIBRARIES, the libraries to link against<br> AVIFILE_DEFINITIONS, definitions to use when compiling<br> AVIFILE_FOUND, If false, don't try to use AVIFILE<br></pre>
</li>
<li>
<a name="module:FindBISON"><b><code>FindBISON</code></b></a>: Find bison executable and provides macros to generate custom build rules<br>
<p>The module defines the following variables:<br><pre> BISON_EXECUTABLE - path to the bison program<br> BISON_VERSION - version of bison<br> BISON_FOUND - true if the program was found<br></pre>
<p><br><p>If bison is found, the module defines the macros:<br><pre> BISON_TARGET(&lt;Name&gt; &lt;YaccInput&gt; &lt;CodeOutput&gt; [VERBOSE &lt;file&gt;]<br> [COMPILE_FLAGS &lt;string&gt;])<br></pre>
<p>which will create a custom rule to generate a parser. &lt;YaccInput&gt; is the path to a yacc file. &lt;CodeOutput&gt; is the name of the source file generated by bison. A header file is also be generated, and contains the token list. If COMPILE_FLAGS option is specified, the next parameter is added in the bison command line. if VERBOSE option is specified, &lt;file&gt; is created and contains verbose descriptions of the grammar and parser. The macro defines a set of variables:<br><pre> BISON_${Name}_DEFINED - true is the macro ran successfully<br> BISON_${Name}_INPUT - The input source file, an alias for &lt;YaccInput&gt;<br> BISON_${Name}_OUTPUT_SOURCE - The source file generated by bison<br> BISON_${Name}_OUTPUT_HEADER - The header file generated by bison<br> BISON_${Name}_OUTPUTS - The sources files generated by bison<br> BISON_${Name}_COMPILE_FLAGS - Options used in the bison command line<br></pre>
<p><br><pre> ====================================================================<br> Example:<br></pre>
<p><br><pre> find_package(BISON)<br> BISON_TARGET(MyParser parser.y ${CMAKE_CURRENT_BINARY_DIR}/parser.cpp)<br> add_executable(Foo main.cpp ${BISON_MyParser_OUTPUTS})<br> ====================================================================<br></pre>
</li>
<li>
<a name="module:FindBLAS"><b><code>FindBLAS</code></b></a>: Find BLAS library<br>
<p>This module finds an installed fortran library that implements the BLAS linear-algebra interface (see <a href="http://www.netlib.org/blas/">http://www.netlib.org/blas/</a>). The list of libraries searched for is taken from the autoconf macro file, acx_blas.m4 (distributed at <a href="http://ac-archive.sourceforge.net/ac-archive/acx_blas.html">http://ac-archive.sourceforge.net/ac-archive/acx_blas.html</a>).<br><p>This module sets the following variables:<br><pre> BLAS_FOUND - set to true if a library implementing the BLAS interface<br> is found<br> BLAS_LINKER_FLAGS - uncached list of required linker flags (excluding -l<br> and -L).<br> BLAS_LIBRARIES - uncached list of libraries (using full path name) to<br> link against to use BLAS<br> BLAS95_LIBRARIES - uncached list of libraries (using full path name)<br> to link against to use BLAS95 interface<br> BLAS95_FOUND - set to true if a library implementing the BLAS f95 interface<br> is found<br> BLA_STATIC if set on this determines what kind of linkage we do (static)<br> BLA_VENDOR if set checks only the specified vendor, if not set checks<br> all the possibilities<br> BLA_F95 if set on tries to find the f95 interfaces for BLAS/LAPACK<br></pre>
<p>######### ## List of vendors (BLA_VENDOR) valid in this module # ATLAS, PhiPACK,CXML,DXML,SunPerf,SCSL,SGIMATH,IBMESSL,Intel10_32 (intel mkl v10 32 bit),Intel10_64lp (intel mkl v10 64 bit,lp thread model, lp64 model), # Intel( older versions of mkl 32 and 64 bit), ACML,Apple, NAS, Generic C/CXX should be enabled to use Intel mkl
</li>
<li>
<a name="module:FindBZip2"><b><code>FindBZip2</code></b></a>: Try to find BZip2<br>
<p>Once done this will define<br><pre> BZIP2_FOUND - system has BZip2<br> BZIP2_INCLUDE_DIR - the BZip2 include directory<br> BZIP2_LIBRARIES - Link these to use BZip2<br> BZIP2_DEFINITIONS - Compiler switches required for using BZip2<br> BZIP2_NEED_PREFIX - this is set if the functions are prefixed with BZ2_<br></pre>
</li>
<li>
<a name="module:FindBoost"><b><code>FindBoost</code></b></a>: Try to find Boost include dirs and libraries<br>
<p>Usage of this module as follows:<br><p>NOTE: Take note of the Boost_ADDITIONAL_VERSIONS variable below. Due to Boost naming conventions and limitations in CMake this find module is NOT future safe with respect to Boost version numbers, and may break.<br><p>== Using Header-Only libraries from within Boost: ==<br><pre> find_package( Boost 1.36.0 )<br> if(Boost_FOUND)<br> include_directories(${Boost_INCLUDE_DIRS})<br> add_executable(foo foo.cc)<br> endif()<br></pre>
<p><br><p><br><p>== Using actual libraries from within Boost: ==<br><pre> set(Boost_USE_STATIC_LIBS ON)<br> set(Boost_USE_MULTITHREADED ON)<br> find_package( Boost 1.36.0 COMPONENTS date_time filesystem system ... )<br></pre>
<p><br><pre> if(Boost_FOUND)<br> include_directories(${Boost_INCLUDE_DIRS})<br> add_executable(foo foo.cc)<br> target_link_libraries(foo ${Boost_LIBRARIES})<br> endif()<br></pre>
<p><br><p><br><p>The components list needs to contain actual names of boost libraries only, such as "date_time" for "libboost_date_time". If you're using parts of Boost that contain header files only (e.g. foreach) you do not need to specify COMPONENTS.<br><p>You should provide a minimum version number that should be used. If you provide this version number and specify the REQUIRED attribute, this module will fail if it can't find the specified or a later version. If you specify a version number this is automatically put into the considered list of version numbers and thus doesn't need to be specified in the Boost_ADDITIONAL_VERSIONS variable (see below).<br><p>NOTE for Visual Studio Users:<br><pre> Automatic linking is used on MSVC &amp; Borland compilers by default when<br> #including things in Boost. It's important to note that setting<br> Boost_USE_STATIC_LIBS to OFF is NOT enough to get you dynamic linking,<br> should you need this feature. Automatic linking typically uses static<br> libraries with a few exceptions (Boost.Python is one).<br></pre>
<p><br><pre> Please see the section below near Boost_LIB_DIAGNOSTIC_DEFINITIONS for<br> more details. Adding a TARGET_LINK_LIBRARIES() as shown in the example<br> above appears to cause VS to link dynamically if Boost_USE_STATIC_LIBS<br> gets set to OFF. It is suggested you avoid automatic linking since it<br> will make your application less portable.<br></pre>
<p><br><p>=========== The mess that is Boost_ADDITIONAL_VERSIONS (sorry?) ============<br><p>OK, so the Boost_ADDITIONAL_VERSIONS variable can be used to specify a list of boost version numbers that should be taken into account when searching for Boost. Unfortunately boost puts the version number into the actual filename for the libraries, so this variable will certainly be needed in the future when new Boost versions are released.<br><p>Currently this module searches for the following version numbers: 1.33, 1.33.0, 1.33.1, 1.34, 1.34.0, 1.34.1, 1.35, 1.35.0, 1.35.1, 1.36, 1.36.0, 1.36.1, 1.37, 1.37.0, 1.38, 1.38.0, 1.39, 1.39.0, 1.40, 1.40.0<br><p>NOTE: If you add a new major 1.x version in Boost_ADDITIONAL_VERSIONS you should add both 1.x and 1.x.0 as shown above. Official Boost include directories omit the 3rd version number from include paths if it is 0 although not all binary Boost releases do so.<br><p>SET(Boost_ADDITIONAL_VERSIONS "1.78" "1.78.0" "1.79" "1.79.0")<br><p>===================================== ============= ========================<br><p>Variables used by this module, they can change the default behaviour and need to be set before calling find_package:<br><pre> Boost_USE_MULTITHREADED Can be set to OFF to use the non-multithreaded<br> boost libraries. If not specified, defaults<br> to ON.<br></pre>
<p><br><pre> Boost_USE_STATIC_LIBS Can be set to ON to force the use of the static<br> boost libraries. Defaults to OFF.<br></pre>
<p><br><p>Other Variables used by this module which you may want to set.<br><pre> Boost_ADDITIONAL_VERSIONS A list of version numbers to use for searching<br> the boost include directory. Please see<br> the documentation above regarding this<br> annoying, but necessary variable :(<br></pre>
<p><br><pre> Boost_DEBUG Set this to TRUE to enable debugging output<br> of FindBoost.cmake if you are having problems.<br> Please enable this before filing any bug<br> reports.<br></pre>
<p><br><pre> Boost_DETAILED_FAILURE_MSG FindBoost doesn't output detailed information<br> about why it failed or how to fix the problem<br> unless this is set to TRUE or the REQUIRED<br> keyword is specified in find_package().<br> [Since CMake 2.8.0]<br></pre>
<p><br><pre> Boost_COMPILER Set this to the compiler suffix used by Boost<br> (e.g. "-gcc43") if FindBoost has problems finding<br> the proper Boost installation<br></pre>
<p><br><p>These last three variables are available also as environment variables:<br><pre> BOOST_ROOT or BOOSTROOT The preferred installation prefix for searching for<br> Boost. Set this if the module has problems finding<br> the proper Boost installation.<br></pre>
<p><br><pre> BOOST_INCLUDEDIR Set this to the include directory of Boost, if the<br> module has problems finding the proper Boost installation<br></pre>
<p><br><pre> BOOST_LIBRARYDIR Set this to the lib directory of Boost, if the<br> module has problems finding the proper Boost installation<br></pre>
<p><br><p>Variables defined by this module:<br><pre> Boost_FOUND System has Boost, this means the include dir was<br> found, as well as all the libraries specified in<br> the COMPONENTS list.<br></pre>
<p><br><pre> Boost_INCLUDE_DIRS Boost include directories: not cached<br></pre>
<p><br><pre> Boost_INCLUDE_DIR This is almost the same as above, but this one is<br> cached and may be modified by advanced users<br></pre>
<p><br><pre> Boost_LIBRARIES Link to these to use the Boost libraries that you<br> specified: not cached<br></pre>
<p><br><pre> Boost_LIBRARY_DIRS The path to where the Boost library files are.<br></pre>
<p><br><pre> Boost_VERSION The version number of the boost libraries that<br> have been found, same as in version.hpp from Boost<br></pre>
<p><br><pre> Boost_LIB_VERSION The version number in filename form as<br> it's appended to the library filenames<br></pre>
<p><br><pre> Boost_MAJOR_VERSION major version number of boost<br> Boost_MINOR_VERSION minor version number of boost<br> Boost_SUBMINOR_VERSION subminor version number of boost<br></pre>
<p><br><pre> Boost_LIB_DIAGNOSTIC_DEFINITIONS [WIN32 Only] You can call<br> add_definitions(${Boost_LIB_DIAGNOSTIC_DEFINITIONS})<br> to have diagnostic information about Boost's<br> automatic linking outputted during compilation time.<br></pre>
<p><br><p>For each component you specify in find_package(), the following (UPPER-CASE) variables are set. You can use these variables if you would like to pick and choose components for your targets instead of just using Boost_LIBRARIES.<br><pre> Boost_${COMPONENT}_FOUND True IF the Boost library "component" was found.<br></pre>
<p><br><pre> Boost_${COMPONENT}_LIBRARY Contains the libraries for the specified Boost<br> "component" (includes debug and optimized keywords<br> when needed).<br></pre>
</li>
<li>
<a name="module:FindBullet"><b><code>FindBullet</code></b></a>: Try to find the Bullet physics engine<br>
<p><br><pre> This module defines the following variables<br></pre>
<p><br><pre> BULLET_FOUND - Was bullet found<br> BULLET_INCLUDE_DIRS - the Bullet include directories<br> BULLET_LIBRARIES - Link to this, by default it includes<br> all bullet components (Dynamics,<br> Collision, LinearMath, &amp; SoftBody)<br></pre>
<p><br><pre> This module accepts the following variables<br></pre>
<p><br><pre> BULLET_ROOT - Can be set to bullet install path or Windows build path<br></pre>
<p><br>
</li>
<li>
<a name="module:FindCABLE"><b><code>FindCABLE</code></b></a>: Find CABLE<br>
<p>This module finds if CABLE is installed and determines where the include files and libraries are. This code sets the following variables:<br><pre> CABLE the path to the cable executable<br> CABLE_TCL_LIBRARY the path to the Tcl wrapper library<br> CABLE_INCLUDE_DIR the path to the include directory<br></pre>
<p><br><p>To build Tcl wrappers, you should add shared library and link it to ${CABLE_TCL_LIBRARY}. You should also add ${CABLE_INCLUDE_DIR} as an include directory.
</li>
<li>
<a name="module:FindCUDA"><b><code>FindCUDA</code></b></a>: Tools for building CUDA C files: libraries and build dependencies.<br>
<p>This script locates the NVIDIA CUDA C tools. It should work on linux, windows, and mac and should be reasonably up to date with CUDA C releases.<br><p>This script makes use of the standard find_package arguments of &lt;VERSION&gt;, REQUIRED and QUIET. CUDA_FOUND will report if an acceptable version of CUDA was found.<br><p>The script will prompt the user to specify CUDA_TOOLKIT_ROOT_DIR if the prefix cannot be determined by the location of nvcc in the system path and REQUIRED is specified to find_package(). To use a different installed version of the toolkit set the environment variable CUDA_BIN_PATH before running cmake (e.g. CUDA_BIN_PATH=/usr/local/cuda1.0 instead of the default /usr/local/cuda) or set CUDA_TOOLKIT_ROOT_DIR after configuring. If you change the value of CUDA_TOOLKIT_ROOT_DIR, various components that depend on the path will be relocated.<br><p>It might be necessary to set CUDA_TOOLKIT_ROOT_DIR manually on certain platforms, or to use a cuda runtime not installed in the default location. In newer versions of the toolkit the cuda library is included with the graphics driver- be sure that the driver version matches what is needed by the cuda runtime version.<br><p>The following variables affect the behavior of the macros in the script (in alphebetical order). Note that any of these flags can be changed multiple times in the same directory before calling CUDA_ADD_EXECUTABLE, CUDA_ADD_LIBRARY, CUDA_COMPILE, CUDA_COMPILE_PTX or CUDA_WRAP_SRCS.<br><pre> CUDA_64_BIT_DEVICE_CODE (Default matches host bit size)<br> -- Set to ON to compile for 64 bit device code, OFF for 32 bit device code.<br> Note that making this different from the host code when generating object<br> or C files from CUDA code just won't work, because size_t gets defined by<br> nvcc in the generated source. If you compile to PTX and then load the<br> file yourself, you can mix bit sizes between device and host.<br></pre>
<p><br><pre> CUDA_ATTACH_VS_BUILD_RULE_TO_CUDA_FILE (Default ON)<br> -- Set to ON if you want the custom build rule to be attached to the source<br> file in Visual Studio. Turn OFF if you add the same cuda file to multiple<br> targets.<br></pre>
<p><br><pre> This allows the user to build the target from the CUDA file; however, bad<br> things can happen if the CUDA source file is added to multiple targets.<br> When performing parallel builds it is possible for the custom build<br> command to be run more than once and in parallel causing cryptic build<br> errors. VS runs the rules for every source file in the target, and a<br> source can have only one rule no matter how many projects it is added to.<br> When the rule is run from multiple targets race conditions can occur on<br> the generated file. Eventually everything will get built, but if the user<br> is unaware of this behavior, there may be confusion. It would be nice if<br> this script could detect the reuse of source files across multiple targets<br> and turn the option off for the user, but no good solution could be found.<br></pre>
<p><br><pre> CUDA_BUILD_CUBIN (Default OFF)<br> -- Set to ON to enable and extra compilation pass with the -cubin option in<br> Device mode. The output is parsed and register, shared memory usage is<br> printed during build.<br></pre>
<p><br><pre> CUDA_BUILD_EMULATION (Default OFF for device mode)<br> -- Set to ON for Emulation mode. -D_DEVICEEMU is defined for CUDA C files<br> when CUDA_BUILD_EMULATION is TRUE.<br></pre>
<p><br><pre> CUDA_GENERATED_OUTPUT_DIR (Default CMAKE_CURRENT_BINARY_DIR)<br> -- Set to the path you wish to have the generated files placed. If it is<br> blank output files will be placed in CMAKE_CURRENT_BINARY_DIR.<br> Intermediate files will always be placed in<br> CMAKE_CURRENT_BINARY_DIR/CMakeFiles.<br></pre>
<p><br><pre> CUDA_HOST_COMPILATION_CPP (Default ON)<br> -- Set to OFF for C compilation of host code.<br></pre>
<p><br><pre> CUDA_NVCC_FLAGS<br> CUDA_NVCC_FLAGS_&lt;CONFIG&gt;<br> -- Additional NVCC command line arguments. NOTE: multiple arguments must be<br> semi-colon delimited (e.g. --compiler-options;-Wall)<br></pre>
<p><br><pre> CUDA_PROPAGATE_HOST_FLAGS (Default ON)<br> -- Set to ON to propagate CMAKE_{C,CXX}_FLAGS and their configuration<br> dependent counterparts (e.g. CMAKE_C_FLAGS_DEBUG) automatically to the<br> host compiler through nvcc's -Xcompiler flag. This helps make the<br> generated host code match the rest of the system better. Sometimes<br> certain flags give nvcc problems, and this will help you turn the flag<br> propagation off. This does not affect the flags supplied directly to nvcc<br> via CUDA_NVCC_FLAGS or through the OPTION flags specified through<br> CUDA_ADD_LIBRARY, CUDA_ADD_EXECUTABLE, or CUDA_WRAP_SRCS. Flags used for<br> shared library compilation are not affected by this flag.<br></pre>
<p><br><pre> CUDA_VERBOSE_BUILD (Default OFF)<br> -- Set to ON to see all the commands used when building the CUDA file. When<br> using a Makefile generator the value defaults to VERBOSE (run make<br> VERBOSE=1 to see output), although setting CUDA_VERBOSE_BUILD to ON will<br> always print the output.<br></pre>
<p><br><p>The script creates the following macros (in alphebetical order):<br><pre> CUDA_ADD_CUFFT_TO_TARGET( cuda_target )<br> -- Adds the cufft library to the target (can be any target). Handles whether<br> you are in emulation mode or not.<br></pre>
<p><br><pre> CUDA_ADD_CUBLAS_TO_TARGET( cuda_target )<br> -- Adds the cublas library to the target (can be any target). Handles<br> whether you are in emulation mode or not.<br></pre>
<p><br><pre> CUDA_ADD_EXECUTABLE( cuda_target file0 file1 ...<br> [WIN32] [MACOSX_BUNDLE] [EXCLUDE_FROM_ALL] [OPTIONS ...] )<br> -- Creates an executable "cuda_target" which is made up of the files<br> specified. All of the non CUDA C files are compiled using the standard<br> build rules specified by CMAKE and the cuda files are compiled to object<br> files using nvcc and the host compiler. In addition CUDA_INCLUDE_DIRS is<br> added automatically to include_directories(). Standard CMake target calls<br> can be used on the target after calling this macro<br> (e.g. set_target_properties and target_link_libraries).<br></pre>
<p><br><pre> CUDA_ADD_LIBRARY( cuda_target file0 file1 ...<br> [STATIC | SHARED | MODULE] [EXCLUDE_FROM_ALL] [OPTIONS ...] )<br> -- Same as CUDA_ADD_EXECUTABLE except that a library is created.<br></pre>
<p><br><pre> CUDA_BUILD_CLEAN_TARGET()<br> -- Creates a convience target that deletes all the dependency files<br> generated. You should make clean after running this target to ensure the<br> dependency files get regenerated.<br></pre>
<p><br><pre> CUDA_COMPILE( generated_files file0 file1 ... [STATIC | SHARED | MODULE]<br> [OPTIONS ...] )<br> -- Returns a list of generated files from the input source files to be used<br> with ADD_LIBRARY or ADD_EXECUTABLE.<br></pre>
<p><br><pre> CUDA_COMPILE_PTX( generated_files file0 file1 ... [OPTIONS ...] )<br> -- Returns a list of PTX files generated from the input source files.<br></pre>
<p><br><pre> CUDA_INCLUDE_DIRECTORIES( path0 path1 ... )<br> -- Sets the directories that should be passed to nvcc<br> (e.g. nvcc -Ipath0 -Ipath1 ... ). These paths usually contain other .cu<br> files.<br></pre>
<p><br><pre> CUDA_WRAP_SRCS ( cuda_target format generated_files file0 file1 ...<br> [STATIC | SHARED | MODULE] [OPTIONS ...] )<br> -- This is where all the magic happens. CUDA_ADD_EXECUTABLE,<br> CUDA_ADD_LIBRARY, CUDA_COMPILE, and CUDA_COMPILE_PTX all call this<br> function under the hood.<br></pre>
<p><br><pre> Given the list of files (file0 file1 ... fileN) this macro generates<br> custom commands that generate either PTX or linkable objects (use "PTX" or<br> "OBJ" for the format argument to switch). Files that don't end with .cu<br> or have the HEADER_FILE_ONLY property are ignored.<br></pre>
<p><br><pre> The arguments passed in after OPTIONS are extra command line options to<br> give to nvcc. You can also specify per configuration options by<br> specifying the name of the configuration followed by the options. General<br> options must preceed configuration specific options. Not all<br> configurations need to be specified, only the ones provided will be used.<br></pre>
<p><br><pre> OPTIONS -DFLAG=2 "-DFLAG_OTHER=space in flag"<br> DEBUG -g<br> RELEASE --use_fast_math<br> RELWITHDEBINFO --use_fast_math;-g<br> MINSIZEREL --use_fast_math<br></pre>
<p><br><pre> For certain configurations (namely VS generating object files with<br> CUDA_ATTACH_VS_BUILD_RULE_TO_CUDA_FILE set to ON), no generated file will<br> be produced for the given cuda file. This is because when you add the<br> cuda file to Visual Studio it knows that this file produces an object file<br> and will link in the resulting object file automatically.<br></pre>
<p><br><pre> This script will also generate a separate cmake script that is used at<br> build time to invoke nvcc. This is for serveral reasons.<br></pre>
<p><br><pre> 1. nvcc can return negative numbers as return values which confuses<br> Visual Studio into thinking that the command succeeded. The script now<br> checks the error codes and produces errors when there was a problem.<br></pre>
<p><br><pre> 2. nvcc has been known to not delete incomplete results when it<br> encounters problems. This confuses build systems into thinking the<br> target was generated when in fact an unusable file exists. The script<br> now deletes the output files if there was an error.<br></pre>
<p><br><pre> 3. By putting all the options that affect the build into a file and then<br> make the build rule dependent on the file, the output files will be<br> regenerated when the options change.<br></pre>
<p><br><pre> This script also looks at optional arguments STATIC, SHARED, or MODULE to<br> determine when to target the object compilation for a shared library.<br> BUILD_SHARED_LIBS is ignored in CUDA_WRAP_SRCS, but it is respected in<br> CUDA_ADD_LIBRARY. On some systems special flags are added for building<br> objects intended for shared libraries. A preprocessor macro,<br> &lt;target_name&gt;_EXPORTS is defined when a shared library compilation is<br> detected.<br></pre>
<p><br><pre> Flags passed into add_definitions with -D or /D are passed along to nvcc.<br></pre>
<p><br><p>The script defines the following variables:<br><pre> CUDA_VERSION_MAJOR -- The major version of cuda as reported by nvcc.<br> CUDA_VERSION_MINOR -- The minor version.<br> CUDA_VERSION<br> CUDA_VERSION_STRING -- CUDA_VERSION_MAJOR.CUDA_VERSION_MINOR<br></pre>
<p><br><pre> CUDA_TOOLKIT_ROOT_DIR -- Path to the CUDA Toolkit (defined if not set).<br> CUDA_SDK_ROOT_DIR -- Path to the CUDA SDK. Use this to find files in the<br> SDK. This script will not directly support finding<br> specific libraries or headers, as that isn't<br> supported by NVIDIA. If you want to change<br> libraries when the path changes see the<br> FindCUDA.cmake script for an example of how to clear<br> these variables. There are also examples of how to<br> use the CUDA_SDK_ROOT_DIR to locate headers or<br> libraries, if you so choose (at your own risk).<br> CUDA_INCLUDE_DIRS -- Include directory for cuda headers. Added automatically<br> for CUDA_ADD_EXECUTABLE and CUDA_ADD_LIBRARY.<br> CUDA_LIBRARIES -- Cuda RT library.<br> CUDA_CUFFT_LIBRARIES -- Device or emulation library for the Cuda FFT<br> implementation (alternative to:<br> CUDA_ADD_CUFFT_TO_TARGET macro)<br> CUDA_CUBLAS_LIBRARIES -- Device or emulation library for the Cuda BLAS<br> implementation (alterative to:<br> CUDA_ADD_CUBLAS_TO_TARGET macro).<br></pre>
<p><br><p><br><pre> James Bigler, NVIDIA Corp (nvidia.com - jbigler)<br> Abe Stephens, SCI Institute -- <a href="http://www.sci.utah.edu/~abe/FindCuda.html">http://www.sci.utah.edu/~abe/FindCuda.html</a><br></pre>
<p><br><pre> Copyright (c) 2008 - 2009 NVIDIA Corporation. All rights reserved.<br></pre>
<p><br><pre> Copyright (c) 2007-2009<br> Scientific Computing and Imaging Institute, University of Utah<br></pre>
<p><br><pre> This code is licensed under the MIT License. See the FindCUDA.cmake script<br> for the text of the license.<br></pre>
</li>
<li>
<a name="module:FindCURL"><b><code>FindCURL</code></b></a>: Find curl<br>
<p>Find the native CURL headers and libraries.<br><pre> CURL_INCLUDE_DIRS - where to find curl/curl.h, etc.<br> CURL_LIBRARIES - List of libraries when using curl.<br> CURL_FOUND - True if curl found.<br></pre>
</li>
<li>
<a name="module:FindCVS"><b><code>FindCVS</code></b></a>: <br>
<p>The module defines the following variables:<br><pre> CVS_EXECUTABLE - path to cvs command line client<br> CVS_FOUND - true if the command line client was found<br></pre>
<p>Example usage:<br><pre> find_package(CVS)<br> if(CVS_FOUND)<br> message("CVS found: ${CVS_EXECUTABLE}")<br> endif(CVS_FOUND)<br></pre>
</li>
<li>
<a name="module:FindCoin3D"><b><code>FindCoin3D</code></b></a>: Find Coin3D (Open Inventor)<br>
<p>Coin3D is an implementation of the Open Inventor API. It provides data structures and algorithms for 3D visualization <a href="http://www.coin3d.org/">http://www.coin3d.org/</a><br><p>This module defines the following variables<br><pre> COIN3D_FOUND - system has Coin3D - Open Inventor<br> COIN3D_INCLUDE_DIRS - where the Inventor include directory can be found<br> COIN3D_LIBRARIES - Link to this to use Coin3D<br></pre>
<p><br>
</li>
<li>
<a name="module:FindCups"><b><code>FindCups</code></b></a>: Try to find the Cups printing system<br>
<p>Once done this will define<br><pre> CUPS_FOUND - system has Cups<br> CUPS_INCLUDE_DIR - the Cups include directory<br> CUPS_LIBRARIES - Libraries needed to use Cups<br> Set CUPS_REQUIRE_IPP_DELETE_ATTRIBUTE to TRUE if you need a version which <br> features this function (i.e. at least 1.1.19)<br></pre>
</li>
<li>
<a name="module:FindCurses"><b><code>FindCurses</code></b></a>: Find the curses include file and library<br>
<p><br><pre> CURSES_FOUND - system has Curses<br> CURSES_INCLUDE_DIR - the Curses include directory<br> CURSES_LIBRARIES - The libraries needed to use Curses<br> CURSES_HAVE_CURSES_H - true if curses.h is available<br> CURSES_HAVE_NCURSES_H - true if ncurses.h is available<br> CURSES_HAVE_NCURSES_NCURSES_H - true if ncurses/ncurses.h is available<br> CURSES_HAVE_NCURSES_CURSES_H - true if ncurses/curses.h is available<br> CURSES_LIBRARY - set for backwards compatibility with 2.4 CMake<br></pre>
<p><br><p>Set CURSES_NEED_NCURSES to TRUE before the FIND_PACKAGE() command if NCurses functionality is required.
</li>
<li>
<a name="module:FindCxxTest"><b><code>FindCxxTest</code></b></a>: Find CxxTest<br>
<p>Find the CxxTest suite and declare a helper macro for creating unit tests and integrating them with CTest. For more details on CxxTest see <a href="http://cxxtest.tigris.org">http://cxxtest.tigris.org</a><br><p>INPUT Variables<br><pre> CXXTEST_USE_PYTHON<br> If true, the CXXTEST_ADD_TEST macro will use<br> the Python test generator instead of Perl.<br></pre>
<p><br><p>OUTPUT Variables<br><pre> CXXTEST_FOUND<br> True if the CxxTest framework was found<br> CXXTEST_INCLUDE_DIR<br> Where to find the CxxTest include directory<br> CXXTEST_PERL_TESTGEN_EXECUTABLE<br> The perl-based test generator.<br> CXXTEST_PYTHON_TESTGEN_EXECUTABLE<br> The python-based test generator.<br></pre>
<p><br><p>MACROS for optional use by CMake users:<br><pre> CXXTEST_ADD_TEST(&lt;test_name&gt; &lt;gen_source_file&gt; &lt;input_files_to_testgen...&gt;)<br> Creates a CxxTest runner and adds it to the CTest testing suite<br> Parameters:<br> test_name The name of the test<br> gen_source_file The generated source filename to be generated by CxxTest<br> input_files_to_testgen The list of header files containing the<br> CxxTest::TestSuite's to be included in this runner<br> <br> #==============<br> Example Usage:<br></pre>
<p><br><pre> find_package(CxxTest)<br> if(CXXTEST_FOUND)<br> include_directories(${CXXTEST_INCLUDE_DIR})<br> enable_testing()<br></pre>
<p><br><pre> CXXTEST_ADD_TEST(unittest_foo foo_test.cc<br> ${CMAKE_CURRENT_SOURCE_DIR}/foo_test.h)<br> target_link_libraries(unittest_foo foo) # as needed<br> endif()<br></pre>
<p><br><pre> This will (if CxxTest is found):<br> 1. Invoke the testgen executable to autogenerate foo_test.cc in the<br> binary tree from "foo_test.h" in the current source directory.<br> 2. Create an executable and test called unittest_foo.<br> <br> #=============<br> Example foo_test.h:<br></pre>
<p><br><pre> #include &lt;cxxtest/TestSuite.h&gt;<br> <br> class MyTestSuite : public CxxTest::TestSuite <br> {<br> public:<br> void testAddition( void )<br> {<br> TS_ASSERT( 1 + 1 &gt; 1 );<br> TS_ASSERT_EQUALS( 1 + 1, 2 );<br> }<br> };<br></pre>
<p><br>
</li>
<li>
<a name="module:FindCygwin"><b><code>FindCygwin</code></b></a>: this module looks for Cygwin<br>
<p><br>
</li>
<li>
<a name="module:FindDCMTK"><b><code>FindDCMTK</code></b></a>: find DCMTK libraries<br>
<p><br>
</li>
<li>
<a name="module:FindDart"><b><code>FindDart</code></b></a>: Find DART<br>
<p>This module looks for the dart testing software and sets DART_ROOT to point to where it found it.<br>
</li>
<li>
<a name="module:FindDevIL"><b><code>FindDevIL</code></b></a>: <br>
<p>This module locates the developer's image library. <a href="http://openil.sourceforge.net/">http://openil.sourceforge.net/</a><br><p>This module sets: IL_LIBRARIES the name of the IL library. These include the full path to the core DevIL library. This one has to be linked into the application. ILU_LIBRARIES the name of the ILU library. Again, the full path. This library is for filters and effects, not actual loading. It doesn't have to be linked if the functionality it provides is not used. ILUT_LIBRARIES the name of the ILUT library. Full path. This part of the library interfaces with OpenGL. It is not strictly needed in applications. IL_INCLUDE_DIR where to find the il.h, ilu.h and ilut.h files. IL_FOUND this is set to TRUE if all the above variables were set. This will be set to false if ILU or ILUT are not found, even if they are not needed. In most systems, if one library is found all the others are as well. That's the way the DevIL developers release it.
</li>
<li>
<a name="module:FindDoxygen"><b><code>FindDoxygen</code></b></a>: This module looks for Doxygen and the path to Graphviz's dot<br>
<p>Doxygen is a documentation generation tool. Please see <a href="http://www.doxygen.org">http://www.doxygen.org</a><br><p>This module accepts the following optional variables:<br><pre> DOXYGEN_SKIP_DOT = If true this module will skip trying to find Dot<br> (an optional component often used by Doxygen)<br></pre>
<p><br><p>This modules defines the following variables:<br><pre> DOXYGEN_EXECUTABLE = The path to the doxygen command.<br> DOXYGEN_FOUND = Was Doxygen found or not?<br></pre>
<p><br><pre> DOXYGEN_DOT_EXECUTABLE = The path to the dot program used by doxygen.<br> DOXYGEN_DOT_FOUND = Was Dot found or not?<br> DOXYGEN_DOT_PATH = The path to dot not including the executable<br></pre>
<p><br><p><br>
</li>
<li>
<a name="module:FindEXPAT"><b><code>FindEXPAT</code></b></a>: Find expat<br>
<p>Find the native EXPAT headers and libraries.<br><pre> EXPAT_INCLUDE_DIRS - where to find expat.h, etc.<br> EXPAT_LIBRARIES - List of libraries when using expat.<br> EXPAT_FOUND - True if expat found.<br></pre>
</li>
<li>
<a name="module:FindFLEX"><b><code>FindFLEX</code></b></a>: Find flex executable and provides a macro to generate custom build rules<br>
<p><br><p>The module defines the following variables:<br><pre> FLEX_FOUND - true is flex executable is found<br> FLEX_EXECUTABLE - the path to the flex executable<br> FLEX_VERSION - the version of flex<br> FLEX_LIBRARIES - The flex libraries<br></pre>
<p><br><p>If flex is found on the system, the module provides the macro:<br><pre> FLEX_TARGET(Name FlexInput FlexOutput [COMPILE_FLAGS &lt;string&gt;])<br></pre>
<p>which creates a custom command to generate the &lt;FlexOutput&gt; file from the &lt;FlexInput&gt; file. If COMPILE_FLAGS option is specified, the next parameter is added to the flex command line. Name is an alias used to get details of this custom command. Indeed the macro defines the following variables:<br><pre> FLEX_${Name}_DEFINED - true is the macro ran successfully<br> FLEX_${Name}_OUTPUTS - the source file generated by the custom rule, an<br> alias for FlexOutput<br> FLEX_${Name}_INPUT - the flex source file, an alias for ${FlexInput}<br></pre>
<p><br><p>Flex scanners oftenly use tokens defined by Bison: the code generated by Flex depends of the header generated by Bison. This module also defines a macro:<br><pre> ADD_FLEX_BISON_DEPENDENCY(FlexTarget BisonTarget)<br></pre>
<p>which adds the required dependency between a scanner and a parser where &lt;FlexTarget&gt; and &lt;BisonTarget&gt; are the first parameters of respectively FLEX_TARGET and BISON_TARGET macros.<br><pre> ====================================================================<br> Example:<br></pre>
<p><br><pre> find_package(BISON)<br> find_package(FLEX)<br></pre>
<p><br><pre> BISON_TARGET(MyParser parser.y ${CMAKE_CURRENT_BINARY_DIR}/parser.cpp<br> FLEX_TARGET(MyScanner lexer.l ${CMAKE_CURRENT_BIANRY_DIR}/lexer.cpp)<br> ADD_FLEX_BISON_DEPENDENCY(MyScanner MyParser)<br></pre>
<p><br><pre> include_directories(${CMAKE_CURRENT_BINARY_DIR})<br> add_executable(Foo<br> Foo.cc<br> ${BISON_MyParser_OUTPUTS}<br> ${FLEX_MyScanner_OUTPUTS}<br> )<br> ====================================================================<br></pre>
</li>
<li>
<a name="module:FindFLTK"><b><code>FindFLTK</code></b></a>: Find the native FLTK includes and library<br>
<p><br><p>By default FindFLTK.cmake will search for all of the FLTK components and add them to the FLTK_LIBRARIES variable.<br><pre> You can limit the components which get placed in FLTK_LIBRARIES by<br> defining one or more of the following three options:<br></pre>
<p><br><pre> FLTK_SKIP_OPENGL, set to true to disable searching for opengl and<br> the FLTK GL library<br> FLTK_SKIP_FORMS, set to true to disable searching for fltk_forms<br> FLTK_SKIP_IMAGES, set to true to disable searching for fltk_images<br></pre>
<p><br><pre> FLTK_SKIP_FLUID, set to true if the fluid binary need not be present<br> at build time<br></pre>
<p><br><p>The following variables will be defined:<br><pre> FLTK_FOUND, True if all components not skipped were found<br> FLTK_INCLUDE_DIR, where to find include files<br> FLTK_LIBRARIES, list of fltk libraries you should link against<br> FLTK_FLUID_EXECUTABLE, where to find the Fluid tool<br> FLTK_WRAP_UI, This enables the FLTK_WRAP_UI command<br></pre>
<p><br><p>The following cache variables are assigned but should not be used. See the FLTK_LIBRARIES variable instead.<br><pre> FLTK_BASE_LIBRARY = the full path to fltk.lib<br> FLTK_GL_LIBRARY = the full path to fltk_gl.lib<br> FLTK_FORMS_LIBRARY = the full path to fltk_forms.lib<br> FLTK_IMAGES_LIBRARY = the full path to fltk_images.lib<br></pre>
</li>
<li>
<a name="module:FindFLTK2"><b><code>FindFLTK2</code></b></a>: Find the native FLTK2 includes and library<br>
<p>The following settings are defined<br><pre> FLTK2_FLUID_EXECUTABLE, where to find the Fluid tool<br> FLTK2_WRAP_UI, This enables the FLTK2_WRAP_UI command<br> FLTK2_INCLUDE_DIR, where to find include files<br> FLTK2_LIBRARIES, list of fltk2 libraries<br> FLTK2_FOUND, Don't use FLTK2 if false.<br></pre>
<p>The following settings should not be used in general.<br><pre> FLTK2_BASE_LIBRARY = the full path to fltk2.lib<br> FLTK2_GL_LIBRARY = the full path to fltk2_gl.lib<br> FLTK2_IMAGES_LIBRARY = the full path to fltk2_images.lib<br></pre>
</li>
<li>
<a name="module:FindFreetype"><b><code>FindFreetype</code></b></a>: Locate FreeType library<br>
<p>This module defines<br><pre> FREETYPE_LIBRARIES, the library to link against<br> FREETYPE_FOUND, if false, do not try to link to FREETYPE<br> FREETYPE_INCLUDE_DIRS, where to find headers.<br> This is the concatenation of the paths:<br> FREETYPE_INCLUDE_DIR_ft2build<br> FREETYPE_INCLUDE_DIR_freetype2<br></pre>
<p><br><p>$FREETYPE_DIR is an environment variable that would correspond to the ./configure --prefix=$FREETYPE_DIR used in building FREETYPE.
</li>
<li>
<a name="module:FindGCCXML"><b><code>FindGCCXML</code></b></a>: Find the GCC-XML front-end executable.
</li>
<li>
<a name="module:FindGDAL"><b><code>FindGDAL</code></b></a>: <br>
<p>Locate gdal<br><p>This module accepts the following environment variables:<br><pre> GDAL_DIR or GDAL_ROOT - Specify the location of GDAL<br></pre>
<p><br><p>This module defines the following CMake variables:<br><pre> GDAL_FOUND - True if libgdal is found<br> GDAL_LIBRARY - A variable pointing to the GDAL library<br> GDAL_INCLUDE_DIR - Where to find the headers<br></pre>
</li>
<li>
<a name="module:FindGIF"><b><code>FindGIF</code></b></a>: <br>
<p>This module defines GIF_LIBRARIES - libraries to link to in order to use GIF GIF_FOUND, if false, do not try to link GIF_INCLUDE_DIR, where to find the headers<br><p>$GIF_DIR is an environment variable that would correspond to the ./configure --prefix=$GIF_DIR
</li>
<li>
<a name="module:FindGLUT"><b><code>FindGLUT</code></b></a>: try to find glut library and include files<br>
<pre> GLUT_INCLUDE_DIR, where to find GL/glut.h, etc.<br> GLUT_LIBRARIES, the libraries to link against<br> GLUT_FOUND, If false, do not try to use GLUT.<br></pre>
<p>Also defined, but not for general use are:<br><pre> GLUT_glut_LIBRARY = the full path to the glut library.<br> GLUT_Xmu_LIBRARY = the full path to the Xmu library.<br> GLUT_Xi_LIBRARY = the full path to the Xi Library.<br></pre>
</li>
<li>
<a name="module:FindGTK"><b><code>FindGTK</code></b></a>: try to find GTK (and glib) and GTKGLArea<br>
<pre> GTK_INCLUDE_DIR - Directories to include to use GTK<br> GTK_LIBRARIES - Files to link against to use GTK<br> GTK_FOUND - GTK was found<br> GTK_GL_FOUND - GTK's GL features were found<br></pre>
</li>
<li>
<a name="module:FindGTK2"><b><code>FindGTK2</code></b></a>: FindGTK2.cmake<br>
<p>This module can find the GTK2 widget libraries and several of its other optional components like gtkmm, glade, and glademm.<br><p>NOTE: If you intend to use version checking, CMake 2.6.2 or later is<br><pre> required.<br></pre>
<p><br><p>Specify one or more of the following components as you call this find module. See example below.<br><pre> gtk<br> gtkmm<br> glade<br> glademm<br></pre>
<p><br><p>The following variables will be defined for your use<br><pre> GTK2_FOUND - Were all of your specified components found?<br> GTK2_INCLUDE_DIRS - All include directories<br> GTK2_LIBRARIES - All libraries<br></pre>
<p><br><pre> GTK2_VERSION - The version of GTK2 found (x.y.z)<br> GTK2_MAJOR_VERSION - The major version of GTK2<br> GTK2_MINOR_VERSION - The minor version of GTK2<br> GTK2_PATCH_VERSION - The patch version of GTK2<br></pre>
<p><br><p>Optional variables you can define prior to calling this module:<br><pre> GTK2_DEBUG - Enables verbose debugging of the module<br> GTK2_SKIP_MARK_AS_ADVANCED - Disable marking cache variables as advanced<br></pre>
<p><br><p>================= Example Usage:<br><pre> Call find_package() once, here are some examples to pick from:<br></pre>
<p><br><pre> Require GTK 2.6 or later<br> find_package(GTK2 2.6 REQUIRED gtk)<br></pre>
<p><br><pre> Require GTK 2.10 or later and Glade<br> find_package(GTK2 2.10 REQUIRED gtk glade)<br></pre>
<p><br><pre> Search for GTK/GTKMM 2.8 or later<br> find_package(GTK2 2.8 COMPONENTS gtk gtkmm)<br></pre>
<p><br><pre> if(GTK2_FOUND)<br> include_directories(${GTK2_INCLUDE_DIRS})<br> add_executable(mygui mygui.cc)<br> target_link_libraries(mygui ${GTK2_LIBRARIES})<br> endif()<br></pre>
<p><br>
</li>
<li>
<a name="module:FindGTest"><b><code>FindGTest</code></b></a>: --------------------<br>
<p>Locate the Google C++ Testing Framework.<br><p>Defines the following variables:<br><pre> GTEST_FOUND - Found the Google Testing framework<br> GTEST_INCLUDE_DIRS - Include directories<br></pre>
<p><br><p>Also defines the library variables below as normal variables. These contain debug/optimized keywords when a debugging library is found.<br><pre> GTEST_BOTH_LIBRARIES - Both libgtest &amp; libgtest-main<br> GTEST_LIBRARIES - libgtest<br> GTEST_MAIN_LIBRARIES - libgtest-main<br></pre>
<p><br><p>Accepts the following variables as input:<br><pre> GTEST_ROOT - (as CMake or env. variable)<br> The root directory of the gtest install prefix<br></pre>
<p><br><pre> GTEST_MSVC_SEARCH - If on MSVC, enables searching the build tree of<br> GTest if set to MD or MT (defaults: MD)<br></pre>
<p><br><p>Example Usage:<br><pre> enable_testing(true)<br> find_package(GTest REQUIRED)<br> include_directories(${GTEST_INCLUDE_DIRS})<br></pre>
<p><br><pre> add_executable(foo foo.cc)<br> target_link_libraries(foo ${GTEST_BOTH_LIBRARIES})<br></pre>
<p><br><pre> add_test(AllTestsInFoo foo)<br></pre>
<p><br><p><br><p>If you would like each Google test to show up in CTest as a test you may use the following macro. NOTE: It WILL slow down your tests, so be warned.<br><p>GTEST_ADD_TESTS(executable extra_args ARGN)<br><pre> executable = The path to the test executable<br> extra_args = Pass a list of extra arguments to be passed to<br> executable enclosed in quotes (or "" for none)<br> ARGN = A list of source files to search for tests &amp; test<br> fixtures.<br></pre>
<p><br><pre> Example:<br> set(FooTestArgs --foo 1 --bar 2)<br> add_executable(FooTest FooUnitTest.cc)<br> GTEST_ADD_TESTS(FooTest "${FooTestArgs}" FooUnitTest.cc)<br></pre>
</li>
<li>
<a name="module:FindGettext"><b><code>FindGettext</code></b></a>: Find GNU gettext tools<br>
<p>This module looks for the GNU gettext tools. This module defines the following values:<br><pre> GETTEXT_MSGMERGE_EXECUTABLE: the full path to the msgmerge tool.<br> GETTEXT_MSGFMT_EXECUTABLE: the full path to the msgfmt tool.<br> GETTEXT_FOUND: True if gettext has been found.<br></pre>
<p><br><p>Additionally it provides the following macros: GETTEXT_CREATE_TRANSLATIONS ( outputFile [ALL] file1 ... fileN )<br><pre> This will create a target "translations" which will convert the <br> given input po files into the binary output mo file. If the <br> ALL option is used, the translations will also be created when<br> building the default target.<br></pre>
</li>
<li>
<a name="module:FindGnuTLS"><b><code>FindGnuTLS</code></b></a>: Try to find the GNU Transport Layer Security library (gnutls)<br>
<p><br><p>Once done this will define<br><pre> GNUTLS_FOUND - System has gnutls<br> GNUTLS_INCLUDE_DIR - The gnutls include directory<br> GNUTLS_LIBRARIES - The libraries needed to use gnutls<br> GNUTLS_DEFINITIONS - Compiler switches required for using gnutls<br></pre>
</li>
<li>
<a name="module:FindGnuplot"><b><code>FindGnuplot</code></b></a>: this module looks for gnuplot<br>
<p><br><p>Once done this will define<br><pre> GNUPLOT_FOUND - system has Gnuplot<br> GNUPLOT_EXECUTABLE - the Gnuplot executable<br></pre>
</li>
<li>
<a name="module:FindHDF5"><b><code>FindHDF5</code></b></a>: Find HDF5, a library for reading and writing self describing array data.<br>
<p><br><p>This module invokes the HDF5 wrapper compiler that should be installed alongside HDF5. Depending upon the HDF5 Configuration, the wrapper compiler is called either h5cc or h5pcc. If this succeeds, the module will then call the compiler with the -show argument to see what flags are used when compiling an HDF5 client application.<br><p>The module will optionally accept the COMPONENTS argument. If no COMPONENTS are specified, then the find module will default to finding only the HDF5 C library. If one or more COMPONENTS are specified, the module will attempt to find the language bindings for the specified components. Currently, the only valid components are C and CXX. The module does not yet support finding the Fortran bindings. If the COMPONENTS argument is not given, the module will attempt to find only the C bindings.<br><p>On UNIX systems, this module will read the variable HDF5_USE_STATIC_LIBRARIES to determine whether or not to prefer a static link to a dynamic link for HDF5 and all of it's dependencies. To use this feature, make sure that the HDF5_USE_STATIC_LIBRARIES variable is set before the call to find_package.<br><p>To provide the module with a hint about where to find your HDF5 installation, you can set the environment variable HDF5_ROOT. The Find module will then look in this path when searching for HDF5 executables, paths, and libraries.<br><p>In addition to finding the includes and libraries required to compile an HDF5 client application, this module also makes an effort to find tools that come with the HDF5 distribution that may be useful for regression testing.<br><p>This module will define the following variables:<br><pre> HDF5_INCLUDE_DIR - Location of the hdf5 includes<br> HDF5_DEFINITIONS - Required compiler definitions for HDF5<br> HDF5_C_LIBRARIES - Required libraries for the HDF5 C bindings.<br> HDF5_CXX_LIBRARIES - Required libraries for the HDF5 C++ bindings<br> HDF5_LIBRARIES - Required libraries for all requested bindings<br> HDF5_FOUND - true if HDF5 was found on the system<br> HDF5_LIBRARY_DIRS - the full set of library directories<br> HDF5_IS_PARALLEL - Whether or not HDF5 was found with parallel IO support<br> HDF5_C_COMPILER_EXECUTABLE - the path to the HDF5 C wrapper compiler<br> HDF5_CXX_COMPILER_EXECUTABLE - the path to the HDF5 C++ wrapper compiler<br> HDF5_DIFF_EXECUTABLE - the path to the HDF5 dataset comparison tool<br></pre>
</li>
<li>
<a name="module:FindHSPELL"><b><code>FindHSPELL</code></b></a>: Try to find HSPELL<br>
<p>Once done this will define<br><pre> HSPELL_FOUND - system has HSPELL<br> HSPELL_INCLUDE_DIR - the HSPELL include directory<br> HSPELL_LIBRARIES - The libraries needed to use HSPELL<br> HSPELL_DEFINITIONS - Compiler switches required for using HSPELL<br></pre>
</li>
<li>
<a name="module:FindHTMLHelp"><b><code>FindHTMLHelp</code></b></a>: This module looks for Microsoft HTML Help Compiler<br>
<p>It defines:<br><pre> HTML_HELP_COMPILER : full path to the Compiler (hhc.exe)<br> HTML_HELP_INCLUDE_PATH : include path to the API (htmlhelp.h)<br> HTML_HELP_LIBRARY : full path to the library (htmlhelp.lib)<br></pre>
<p><br>
</li>
<li>
<a name="module:FindITK"><b><code>FindITK</code></b></a>: Find an ITK installation or build tree.
</li>
<li>
<a name="module:FindImageMagick"><b><code>FindImageMagick</code></b></a>: Find the ImageMagick binary suite.<br>
<p>This module will search for a set of ImageMagick tools specified as components in the FIND_PACKAGE call. Typical components include, but are not limited to (future versions of ImageMagick might have additional components not listed here):<br><pre> animate<br> compare<br> composite<br> conjure<br> convert<br> display<br> identify<br> import<br> mogrify<br> montage<br> stream<br></pre>
<p><br><p>If no component is specified in the FIND_PACKAGE call, then it only searches for the ImageMagick executable directory. This code defines the following variables:<br><pre> ImageMagick_FOUND - TRUE if all components are found.<br> ImageMagick_EXECUTABLE_DIR - Full path to executables directory.<br> ImageMagick_&lt;component&gt;_FOUND - TRUE if &lt;component&gt; is found.<br> ImageMagick_&lt;component&gt;_EXECUTABLE - Full path to &lt;component&gt; executable.<br></pre>
<p><br><p>There are also components for the following ImageMagick APIs:<br><pre> Magick++<br> MagickWand<br> MagickCore<br></pre>
<p><br><p>For these components the following variables are set:<br><pre> ImageMagick_FOUND - TRUE if all components are found.<br> ImageMagick_INCLUDE_DIRS - Full paths to all include dirs.<br> ImageMagick_LIBRARIES - Full paths to all libraries.<br> ImageMagick_&lt;component&gt;_FOUND - TRUE if &lt;component&gt; is found.<br> ImageMagick_&lt;component&gt;_INCLUDE_DIRS - Full path to &lt;component&gt; include dirs.<br> ImageMagick_&lt;component&gt;_LIBRARIES - Full path to &lt;component&gt; libraries.<br></pre>
<p><br><p>Example Usages:<br><pre> FIND_PACKAGE(ImageMagick)<br> FIND_PACKAGE(ImageMagick COMPONENTS convert)<br> FIND_PACKAGE(ImageMagick COMPONENTS convert mogrify display)<br> FIND_PACKAGE(ImageMagick COMPONENTS Magick++)<br> FIND_PACKAGE(ImageMagick COMPONENTS Magick++ convert)<br></pre>
<p><br><p>Note that the standard FIND_PACKAGE features are supported (i.e., QUIET, REQUIRED, etc.).
</li>
<li>
<a name="module:FindJNI"><b><code>FindJNI</code></b></a>: Find JNI java libraries.<br>
<p>This module finds if Java is installed and determines where the include files and libraries are. It also determines what the name of the library is. This code sets the following variables:<br><pre> <br> JNI_INCLUDE_DIRS = the include dirs to use<br> JNI_LIBRARIES = the libraries to use<br> JAVA_AWT_LIBRARY = the path to the jawt library<br> JAVA_JVM_LIBRARY = the path to the jvm library<br> JAVA_INCLUDE_PATH = the include path to jni.h<br> JAVA_INCLUDE_PATH2 = the include path to jni_md.h<br> JAVA_AWT_INCLUDE_PATH = the include path to jawt.h<br></pre>
<p><br>
</li>
<li>
<a name="module:FindJPEG"><b><code>FindJPEG</code></b></a>: Find JPEG<br>
<p>Find the native JPEG includes and library This module defines<br><pre> JPEG_INCLUDE_DIR, where to find jpeglib.h, etc.<br> JPEG_LIBRARIES, the libraries needed to use JPEG.<br> JPEG_FOUND, If false, do not try to use JPEG.<br></pre>
<p>also defined, but not for general use are<br><pre> JPEG_LIBRARY, where to find the JPEG library.<br></pre>
</li>
<li>
<a name="module:FindJasper"><b><code>FindJasper</code></b></a>: Try to find the Jasper JPEG2000 library<br>
<p>Once done this will define<br><pre> JASPER_FOUND - system has Jasper<br> JASPER_INCLUDE_DIR - the Jasper include directory<br> JASPER_LIBRARIES - The libraries needed to use Jasper<br></pre>
</li>
<li>
<a name="module:FindJava"><b><code>FindJava</code></b></a>: Find Java<br>
<p>This module finds if Java is installed and determines where the include files and libraries are. This code sets the following variables:<br><pre> JAVA_RUNTIME = the full path to the Java runtime<br> JAVA_COMPILE = the full path to the Java compiler<br> JAVA_ARCHIVE = the full path to the Java archiver<br></pre>
<p><br>
</li>
<li>
<a name="module:FindKDE3"><b><code>FindKDE3</code></b></a>: Find the KDE3 include and library dirs, KDE preprocessors and define a some macros<br>
<p><br><p>This module defines the following variables:<br><pre> KDE3_DEFINITIONS - compiler definitions required for compiling KDE software<br> KDE3_INCLUDE_DIR - the KDE include directory<br> KDE3_INCLUDE_DIRS - the KDE and the Qt include directory, for use with INCLUDE_DIRECTORIES()<br> KDE3_LIB_DIR - the directory where the KDE libraries are installed, for use with LINK_DIRECTORIES()<br> QT_AND_KDECORE_LIBS - this contains both the Qt and the kdecore library<br> KDE3_DCOPIDL_EXECUTABLE - the dcopidl executable<br> KDE3_DCOPIDL2CPP_EXECUTABLE - the dcopidl2cpp executable<br> KDE3_KCFGC_EXECUTABLE - the kconfig_compiler executable<br> KDE3_FOUND - set to TRUE if all of the above has been found<br></pre>
<p><br><p>The following user adjustable options are provided:<br><pre> KDE3_BUILD_TESTS - enable this to build KDE testcases<br></pre>
<p><br><p><br><p>It also adds the following macros (from KDE3Macros.cmake) SRCS_VAR is always the variable which contains the list of source files for your application or library.<br><p>KDE3_AUTOMOC(file1 ... fileN)<br><pre> Call this if you want to have automatic moc file handling.<br> This means if you include "foo.moc" in the source file foo.cpp<br> a moc file for the header foo.h will be created automatically.<br> You can set the property SKIP_AUTOMAKE using SET_SOURCE_FILES_PROPERTIES()<br> to exclude some files in the list from being processed.<br></pre>
<p><br><p>KDE3_ADD_MOC_FILES(SRCS_VAR file1 ... fileN )<br><pre> If you don't use the KDE3_AUTOMOC() macro, for the files<br> listed here moc files will be created (named "foo.moc.cpp")<br></pre>
<p><br><p>KDE3_ADD_DCOP_SKELS(SRCS_VAR header1.h ... headerN.h )<br><pre> Use this to generate DCOP skeletions from the listed headers.<br></pre>
<p><br><p>KDE3_ADD_DCOP_STUBS(SRCS_VAR header1.h ... headerN.h )<br><pre> Use this to generate DCOP stubs from the listed headers.<br></pre>
<p><br><p>KDE3_ADD_UI_FILES(SRCS_VAR file1.ui ... fileN.ui )<br><pre> Use this to add the Qt designer ui files to your application/library.<br></pre>
<p><br><p>KDE3_ADD_KCFG_FILES(SRCS_VAR file1.kcfgc ... fileN.kcfgc )<br><pre> Use this to add KDE kconfig compiler files to your application/library.<br></pre>
<p><br><p>KDE3_INSTALL_LIBTOOL_FILE(target)<br><pre> This will create and install a simple libtool file for the given target.<br></pre>
<p><br><p>KDE3_ADD_EXECUTABLE(name file1 ... fileN )<br><pre> Currently identical to ADD_EXECUTABLE(), may provide some advanced features in the future.<br></pre>
<p><br><p>KDE3_ADD_KPART(name [WITH_PREFIX] file1 ... fileN )<br><pre> Create a KDE plugin (KPart, kioslave, etc.) from the given source files.<br> If WITH_PREFIX is given, the resulting plugin will have the prefix "lib", otherwise it won't.<br> It creates and installs an appropriate libtool la-file.<br></pre>
<p><br><p>KDE3_ADD_KDEINIT_EXECUTABLE(name file1 ... fileN )<br><pre> Create a KDE application in the form of a module loadable via kdeinit.<br> A library named kdeinit_&lt;name&gt; will be created and a small executable which links to it.<br></pre>
<p><br><p>The option KDE3_ENABLE_FINAL to enable all-in-one compilation is no longer supported.<br><p><br><p>Author: Alexander Neundorf &lt;neundorf@kde.org&gt;
</li>
<li>
<a name="module:FindKDE4"><b><code>FindKDE4</code></b></a>: <br>
<p>Find KDE4 and provide all necessary variables and macros to compile software for it. It looks for KDE 4 in the following directories in the given order:<br><pre> CMAKE_INSTALL_PREFIX<br> KDEDIRS<br> /opt/kde4<br></pre>
<p><br><p>Please look in FindKDE4Internal.cmake and KDE4Macros.cmake for more information. They are installed with the KDE 4 libraries in $KDEDIRS/share/apps/cmake/modules/.<br><p>Author: Alexander Neundorf &lt;neundorf@kde.org&gt;
</li>
<li>
<a name="module:FindLAPACK"><b><code>FindLAPACK</code></b></a>: Find LAPACK library<br>
<p>This module finds an installed fortran library that implements the LAPACK linear-algebra interface (see <a href="http://www.netlib.org/lapack/">http://www.netlib.org/lapack/</a>).<br><p>The approach follows that taken for the autoconf macro file, acx_lapack.m4 (distributed at <a href="http://ac-archive.sourceforge.net/ac-archive/acx_lapack.html">http://ac-archive.sourceforge.net/ac-archive/acx_lapack.html</a>).<br><p>This module sets the following variables:<br><pre> LAPACK_FOUND - set to true if a library implementing the LAPACK interface<br> is found<br> LAPACK_LINKER_FLAGS - uncached list of required linker flags (excluding -l<br> and -L).<br> LAPACK_LIBRARIES - uncached list of libraries (using full path name) to<br> link against to use LAPACK<br> LAPACK95_LIBRARIES - uncached list of libraries (using full path name) to<br> link against to use LAPACK95<br> LAPACK95_FOUND - set to true if a library implementing the LAPACK f95<br> interface is found<br> BLA_STATIC if set on this determines what kind of linkage we do (static)<br> BLA_VENDOR if set checks only the specified vendor, if not set checks<br> all the possibilities<br> BLA_F95 if set on tries to find the f95 interfaces for BLAS/LAPACK<br></pre>
<p>## List of vendors (BLA_VENDOR) valid in this module # Intel(mkl), ACML,Apple, NAS, Generic
</li>
<li>
<a name="module:FindLATEX"><b><code>FindLATEX</code></b></a>: Find Latex<br>
<p>This module finds if Latex is installed and determines where the executables are. This code sets the following variables:<br><pre> <br> LATEX_COMPILER: path to the LaTeX compiler<br> PDFLATEX_COMPILER: path to the PdfLaTeX compiler<br> BIBTEX_COMPILER: path to the BibTeX compiler<br> MAKEINDEX_COMPILER: path to the MakeIndex compiler<br> DVIPS_CONVERTER: path to the DVIPS converter<br> PS2PDF_CONVERTER: path to the PS2PDF converter<br> LATEX2HTML_CONVERTER: path to the LaTeX2Html converter <br></pre>
<p><br>
</li>
<li>
<a name="module:FindLibXml2"><b><code>FindLibXml2</code></b></a>: Try to find LibXml2<br>
<p>Once done this will define<br><pre> LIBXML2_FOUND - System has LibXml2<br> LIBXML2_INCLUDE_DIR - The LibXml2 include directory<br> LIBXML2_LIBRARIES - The libraries needed to use LibXml2<br> LIBXML2_DEFINITIONS - Compiler switches required for using LibXml2<br> LIBXML2_XMLLINT_EXECUTABLE - The XML checking tool xmllint coming with LibXml2<br></pre>
</li>
<li>
<a name="module:FindLibXslt"><b><code>FindLibXslt</code></b></a>: Try to find LibXslt<br>
<p>Once done this will define<br><pre> LIBXSLT_FOUND - system has LibXslt<br> LIBXSLT_INCLUDE_DIR - the LibXslt include directory<br> LIBXSLT_LIBRARIES - Link these to LibXslt<br> LIBXSLT_DEFINITIONS - Compiler switches required for using LibXslt<br></pre>
</li>
<li>
<a name="module:FindLua50"><b><code>FindLua50</code></b></a>: <br>
<p>Locate Lua library This module defines<br><pre> LUA50_FOUND, if false, do not try to link to Lua <br> LUA_LIBRARIES, both lua and lualib<br> LUA_INCLUDE_DIR, where to find lua.h and lualib.h (and probably lauxlib.h)<br></pre>
<p><br><p>Note that the expected include convention is<br><pre> #include "lua.h"<br></pre>
<p>and not<br><pre> #include &lt;lua/lua.h&gt;<br></pre>
<p>This is because, the lua location is not standardized and may exist in locations other than lua/
</li>
<li>
<a name="module:FindLua51"><b><code>FindLua51</code></b></a>: <br>
<p>Locate Lua library This module defines<br><pre> LUA51_FOUND, if false, do not try to link to Lua <br> LUA_LIBRARIES<br> LUA_INCLUDE_DIR, where to find lua.h <br></pre>
<p><br><p>Note that the expected include convention is<br><pre> #include "lua.h"<br></pre>
<p>and not<br><pre> #include &lt;lua/lua.h&gt;<br></pre>
<p>This is because, the lua location is not standardized and may exist in locations other than lua/
</li>
<li>
<a name="module:FindMFC"><b><code>FindMFC</code></b></a>: Find MFC on Windows<br>
<p>Find the native MFC - i.e. decide if an application can link to the MFC libraries.<br><pre> MFC_FOUND - Was MFC support found<br></pre>
<p>You don't need to include anything or link anything to use it.
</li>
<li>
<a name="module:FindMPEG"><b><code>FindMPEG</code></b></a>: Find the native MPEG includes and library<br>
<p>This module defines<br><pre> MPEG_INCLUDE_DIR, where to find MPEG.h, etc.<br> MPEG_LIBRARIES, the libraries required to use MPEG.<br> MPEG_FOUND, If false, do not try to use MPEG.<br></pre>
<p>also defined, but not for general use are<br><pre> MPEG_mpeg2_LIBRARY, where to find the MPEG library.<br> MPEG_vo_LIBRARY, where to find the vo library.<br></pre>
</li>
<li>
<a name="module:FindMPEG2"><b><code>FindMPEG2</code></b></a>: Find the native MPEG2 includes and library<br>
<p>This module defines<br><pre> MPEG2_INCLUDE_DIR, path to mpeg2dec/mpeg2.h, etc.<br> MPEG2_LIBRARIES, the libraries required to use MPEG2.<br> MPEG2_FOUND, If false, do not try to use MPEG2.<br></pre>
<p>also defined, but not for general use are<br><pre> MPEG2_mpeg2_LIBRARY, where to find the MPEG2 library.<br> MPEG2_vo_LIBRARY, where to find the vo library.<br></pre>
</li>
<li>
<a name="module:FindMPI"><b><code>FindMPI</code></b></a>: Message Passing Interface (MPI) module.<br>
<p><br><p>The Message Passing Interface (MPI) is a library used to write high-performance parallel applications that use message passing, and is typically deployed on a cluster. MPI is a standard interface (defined by the MPI forum) for which many implementations are available. All of these implementations have somewhat different compilation approaches (different include paths, libraries to link against, etc.), and this module tries to smooth out those differences.<br><p>This module will set the following variables:<br><pre> MPI_FOUND TRUE if we have found MPI<br> MPI_COMPILE_FLAGS Compilation flags for MPI programs<br> MPI_INCLUDE_PATH Include path(s) for MPI header<br> MPI_LINK_FLAGS Linking flags for MPI programs<br> MPI_LIBRARY First MPI library to link against (cached)<br> MPI_EXTRA_LIBRARY Extra MPI libraries to link against (cached)<br> MPI_LIBRARIES All libraries to link MPI programs against<br> MPIEXEC Executable for running MPI programs<br> MPIEXEC_NUMPROC_FLAG Flag to pass to MPIEXEC before giving it the<br> number of processors to run on<br> MPIEXEC_PREFLAGS Flags to pass to MPIEXEC directly before the<br> executable to run.<br> MPIEXEC_POSTFLAGS Flags to pass to MPIEXEC after all other flags.<br></pre>
<p><br><p>This module will attempt to auto-detect these settings, first by looking for a MPI compiler, which many MPI implementations provide as a pass-through to the native compiler to simplify the compilation of MPI programs. The MPI compiler is stored in the cache variable MPI_COMPILER, and will attempt to look for commonly-named drivers mpic++, mpicxx, mpiCC, or mpicc. If the compiler driver is found and recognized, it will be used to set all of the module variables. To skip this auto-detection, set MPI_LIBRARY and MPI_INCLUDE_PATH in the CMake cache.<br><p>If no compiler driver is found or the compiler driver is not recognized, this module will then search for common include paths and library names to try to detect MPI.<br><p>If CMake initially finds a different MPI than was intended, and you want to use the MPI compiler auto-detection for a different MPI implementation, set MPI_COMPILER to the MPI compiler driver you want to use (e.g., mpicxx) and then set MPI_LIBRARY to the string MPI_LIBRARY-NOTFOUND. When you re-configure, auto-detection of MPI will run again with the newly-specified MPI_COMPILER.<br><p>When using MPIEXEC to execute MPI applications, you should typically use all of the MPIEXEC flags as follows:<br><pre> ${MPIEXEC} ${MPIEXEC_NUMPROC_FLAG} PROCS ${MPIEXEC_PREFLAGS} EXECUTABLE<br> ${MPIEXEC_POSTFLAGS} ARGS<br></pre>
<p>where PROCS is the number of processors on which to execute the program, EXECUTABLE is the MPI program, and ARGS are the arguments to pass to the MPI program.
</li>
<li>
<a name="module:FindMatlab"><b><code>FindMatlab</code></b></a>: this module looks for Matlab<br>
<p>Defines:<br><pre> MATLAB_INCLUDE_DIR: include path for mex.h, engine.h<br> MATLAB_LIBRARIES: required libraries: libmex, etc<br> MATLAB_MEX_LIBRARY: path to libmex.lib<br> MATLAB_MX_LIBRARY: path to libmx.lib<br> MATLAB_ENG_LIBRARY: path to libeng.lib<br></pre>
</li>
<li>
<a name="module:FindMotif"><b><code>FindMotif</code></b></a>: Try to find Motif (or lesstif)<br>
<p>Once done this will define:<br><pre> MOTIF_FOUND - system has MOTIF<br> MOTIF_INCLUDE_DIR - include paths to use Motif<br> MOTIF_LIBRARIES - Link these to use Motif<br></pre>
</li>
<li>
<a name="module:FindOpenAL"><b><code>FindOpenAL</code></b></a>: <br>
<p>Locate OpenAL This module defines OPENAL_LIBRARY OPENAL_FOUND, if false, do not try to link to OpenAL OPENAL_INCLUDE_DIR, where to find the headers<br><p>$OPENALDIR is an environment variable that would correspond to the ./configure --prefix=$OPENALDIR used in building OpenAL.<br><p>Created by Eric Wing. This was influenced by the FindSDL.cmake module.
</li>
<li>
<a name="module:FindOpenGL"><b><code>FindOpenGL</code></b></a>: Try to find OpenGL<br>
<p>Once done this will define<br><pre> <br> OPENGL_FOUND - system has OpenGL<br> OPENGL_XMESA_FOUND - system has XMESA<br> OPENGL_GLU_FOUND - system has GLU<br> OPENGL_INCLUDE_DIR - the GL include directory<br> OPENGL_LIBRARIES - Link these to use OpenGL and GLU<br> <br></pre>
<p>If you want to use just GL you can use these values<br><pre> OPENGL_gl_LIBRARY - Path to OpenGL Library<br> OPENGL_glu_LIBRARY - Path to GLU Library<br> <br></pre>
<p>On OSX default to using the framework version of opengl People will have to change the cache values of OPENGL_glu_LIBRARY and OPENGL_gl_LIBRARY to use OpenGL with X11 on OSX
</li>
<li>
<a name="module:FindOpenMP"><b><code>FindOpenMP</code></b></a>: Finds OpenMP support<br>
<p>This module can be used to detect OpenMP support in a compiler. If the compiler supports OpenMP, the flags required to compile with openmp support are set. <br><p>The following variables are set:<br><pre> OpenMP_C_FLAGS - flags to add to the C compiler for OpenMP support<br> OpenMP_CXX_FLAGS - flags to add to the CXX compiler for OpenMP support<br> OPENMP_FOUND - true if openmp is detected<br></pre>
<p><br><p>Supported compilers can be found at <a href="http://openmp.org/wp/openmp-compilers/">http://openmp.org/wp/openmp-compilers/</a>
</li>
<li>
<a name="module:FindOpenSSL"><b><code>FindOpenSSL</code></b></a>: Try to find the OpenSSL encryption library<br>
<p>Once done this will define<br><pre> OPENSSL_FOUND - system has the OpenSSL library<br> OPENSSL_INCLUDE_DIR - the OpenSSL include directory<br> OPENSSL_LIBRARIES - The libraries needed to use OpenSSL<br></pre>
</li>
<li>
<a name="module:FindOpenSceneGraph"><b><code>FindOpenSceneGraph</code></b></a>: Find OpenSceneGraph<br>
<p>This module searches for the OpenSceneGraph core "osg" library as well as OpenThreads, and whatever additional COMPONENTS (nodekits) that you specify.<br><pre> See <a href="http://www.openscenegraph.org">http://www.openscenegraph.org</a><br></pre>
<p><br><p>NOTE: To use this module effectively you must either require CMake &gt;= 2.6.3 with cmake_minimum_required(VERSION 2.6.3) or download and place FindOpenThreads.cmake, Findosg_functions.cmake, Findosg.cmake, and Find&lt;etc&gt;.cmake files into your CMAKE_MODULE_PATH.<br><p>==================================<br><p>This module accepts the following variables (note mixed case)<br><pre> OpenSceneGraph_DEBUG - Enable debugging output<br></pre>
<p><br><pre> OpenSceneGraph_MARK_AS_ADVANCED - Mark cache variables as advanced <br> automatically<br></pre>
<p><br><p>The following environment variables are also respected for finding the OSG and it's various components. CMAKE_PREFIX_PATH can also be used for this (see find_library() CMake documentation).<br><pre> &lt;MODULE&gt;_DIR (where MODULE is of the form "OSGVOLUME" and there is a FindosgVolume.cmake file)<br> OSG_DIR<br> OSGDIR<br> OSG_ROOT<br></pre>
<p><br><p>This module defines the following output variables:<br><pre> OPENSCENEGRAPH_FOUND - Was the OSG and all of the specified components found?<br></pre>
<p><br><pre> OPENSCENEGRAPH_VERSION - The version of the OSG which was found<br></pre>
<p><br><pre> OPENSCENEGRAPH_INCLUDE_DIRS - Where to find the headers<br></pre>
<p><br><pre> OPENSCENEGRAPH_LIBRARIES - The OSG libraries<br></pre>
<p><br><p>================================== Example Usage:<br><pre> find_package(OpenSceneGraph 2.0.0 REQUIRED osgDB osgUtil)<br> # libOpenThreads &amp; libosg automatically searched<br> include_directories(${OPENSCENEGRAPH_INCLUDE_DIRS})<br></pre>
<p><br><pre> add_executable(foo foo.cc)<br> target_link_libraries(foo ${OPENSCENEGRAPH_LIBRARIES})<br></pre>
<p><br>
</li>
<li>
<a name="module:FindOpenThreads"><b><code>FindOpenThreads</code></b></a>: <br>
<p>OpenThreads is a C++ based threading library. Its largest userbase seems to OpenSceneGraph so you might notice I accept OSGDIR as an environment path. I consider this part of the Findosg* suite used to find OpenSceneGraph components. Each component is separate and you must opt in to each module.<br><p>Locate OpenThreads This module defines OPENTHREADS_LIBRARY OPENTHREADS_FOUND, if false, do not try to link to OpenThreads OPENTHREADS_INCLUDE_DIR, where to find the headers<br><p>$OPENTHREADS_DIR is an environment variable that would correspond to the ./configure --prefix=$OPENTHREADS_DIR used in building osg.<br><p>Created by Eric Wing.
</li>
<li>
<a name="module:FindPHP4"><b><code>FindPHP4</code></b></a>: Find PHP4<br>
<p>This module finds if PHP4 is installed and determines where the include files and libraries are. It also determines what the name of the library is. This code sets the following variables:<br><pre> PHP4_INCLUDE_PATH = path to where php.h can be found<br> PHP4_EXECUTABLE = full path to the php4 binary<br></pre>
<p><br>
</li>
<li>
<a name="module:FindPNG"><b><code>FindPNG</code></b></a>: Find the native PNG includes and library<br>
<p><br><p>This module defines<br><pre> PNG_INCLUDE_DIR, where to find png.h, etc.<br> PNG_LIBRARIES, the libraries to link against to use PNG.<br> PNG_DEFINITIONS - You should add_definitons(${PNG_DEFINITIONS}) before compiling code that includes png library files.<br> PNG_FOUND, If false, do not try to use PNG.<br></pre>
<p>also defined, but not for general use are<br><pre> PNG_LIBRARY, where to find the PNG library.<br></pre>
<p>None of the above will be defined unles zlib can be found. PNG depends on Zlib
</li>
<li>
<a name="module:FindPackageHandleStandardArgs"><b><code>FindPackageHandleStandardArgs</code></b></a>: <br>
<p>FIND_PACKAGE_HANDLE_STANDARD_ARGS(NAME (DEFAULT_MSG|"Custom failure message") VAR1 ... )<br><pre> This macro is intended to be used in FindXXX.cmake modules files.<br> It handles the REQUIRED and QUIET argument to FIND_PACKAGE() and<br> it also sets the &lt;UPPERCASED_NAME&gt;_FOUND variable.<br> The package is found if all variables listed are TRUE.<br> Example:<br></pre>
<p><br><pre> FIND_PACKAGE_HANDLE_STANDARD_ARGS(LibXml2 DEFAULT_MSG LIBXML2_LIBRARIES LIBXML2_INCLUDE_DIR)<br></pre>
<p><br><pre> LibXml2 is considered to be found, if both LIBXML2_LIBRARIES and <br> LIBXML2_INCLUDE_DIR are valid. Then also LIBXML2_FOUND is set to TRUE.<br> If it is not found and REQUIRED was used, it fails with FATAL_ERROR, <br> independent whether QUIET was used or not.<br> If it is found, the location is reported using the VAR1 argument, so <br> here a message "Found LibXml2: /usr/lib/libxml2.so" will be printed out.<br> If the second argument is DEFAULT_MSG, the message in the failure case will <br> be "Could NOT find LibXml2", if you don't like this message you can specify<br> your own custom failure message there.<br></pre>
</li>
<li>
<a name="module:FindPackageMessage"><b><code>FindPackageMessage</code></b></a>: <br>
<p>FIND_PACKAGE_MESSAGE(&lt;name&gt; "message for user" "find result details")<br><p>This macro is intended to be used in FindXXX.cmake modules files. It will print a message once for each unique find result. This is useful for telling the user where a package was found. The first argument specifies the name (XXX) of the package. The second argument specifies the message to display. The third argument lists details about the find result so that if they change the message will be displayed again. The macro also obeys the QUIET argument to the find_package command.<br><p>Example:<br><pre> IF(X11_FOUND)<br> FIND_PACKAGE_MESSAGE(X11 "Found X11: ${X11_X11_LIB}"<br> "[${X11_X11_LIB}][${X11_INCLUDE_DIR}]")<br> ELSE(X11_FOUND)<br> ...<br> ENDIF(X11_FOUND)<br></pre>
</li>
<li>
<a name="module:FindPerl"><b><code>FindPerl</code></b></a>: Find perl<br>
<p>this module looks for Perl<br><pre> PERL_EXECUTABLE - the full path to perl<br> PERL_FOUND - If false, don't attempt to use perl.<br></pre>
</li>
<li>
<a name="module:FindPerlLibs"><b><code>FindPerlLibs</code></b></a>: Find Perl libraries<br>
<p>This module finds if PERL is installed and determines where the include files and libraries are. It also determines what the name of the library is. This code sets the following variables:<br><pre> PERLLIBS_FOUND = True if perl.h &amp; libperl were found<br> PERL_INCLUDE_PATH = path to where perl.h is found<br> PERL_LIBRARY = path to libperl<br> PERL_EXECUTABLE = full path to the perl binary<br></pre>
<p><br><pre> The following variables are also available if needed<br> (introduced after CMake 2.6.4)<br></pre>
<p><br><pre> PERL_SITESEARCH = path to the sitesearch install dir<br> PERL_SITELIB = path to the sitelib install directory<br> PERL_VENDORARCH = path to the vendor arch install directory<br> PERL_VENDORLIB = path to the vendor lib install directory<br> PERL_ARCHLIB = path to the arch lib install directory<br> PERL_PRIVLIB = path to the priv lib install directory<br> PERL_EXTRA_C_FLAGS = Compilation flags used to build perl<br></pre>
<p><br>
</li>
<li>
<a name="module:FindPhysFS"><b><code>FindPhysFS</code></b></a>: <br>
<p>Locate PhysFS library This module defines PHYSFS_LIBRARY, the name of the library to link against PHYSFS_FOUND, if false, do not try to link to PHYSFS PHYSFS_INCLUDE_DIR, where to find physfs.h<br><p>$PHYSFSDIR is an environment variable that would correspond to the ./configure --prefix=$PHYSFSDIR used in building PHYSFS.<br><p>Created by Eric Wing.
</li>
<li>
<a name="module:FindPike"><b><code>FindPike</code></b></a>: Find Pike<br>
<p>This module finds if PIKE is installed and determines where the include files and libraries are. It also determines what the name of the library is. This code sets the following variables:<br><pre> PIKE_INCLUDE_PATH = path to where program.h is found<br> PIKE_EXECUTABLE = full path to the pike binary<br></pre>
<p><br>
</li>
<li>
<a name="module:FindPkgConfig"><b><code>FindPkgConfig</code></b></a>: a pkg-config module for CMake<br>
<p><br><p>Usage:<br><pre> pkg_check_modules(&lt;PREFIX&gt; [REQUIRED] &lt;MODULE&gt; [&lt;MODULE&gt;]*)<br> checks for all the given modules<br></pre>
<p><br><pre> pkg_search_module(&lt;PREFIX&gt; [REQUIRED] &lt;MODULE&gt; [&lt;MODULE&gt;]*)<br> checks for given modules and uses the first working one<br></pre>
<p><br><p>When the 'REQUIRED' argument was set, macros will fail with an error when module(s) could not be found<br><p>It sets the following variables:<br><pre> PKG_CONFIG_FOUND ... true if pkg-config works on the system<br> PKG_CONFIG_EXECUTABLE ... pathname of the pkg-config program<br> &lt;PREFIX&gt;_FOUND ... set to 1 if module(s) exist<br></pre>
<p><br><p>For the following variables two sets of values exist; first one is the common one and has the given PREFIX. The second set contains flags which are given out when pkgconfig was called with the '--static' option.<br><pre> &lt;XPREFIX&gt;_LIBRARIES ... only the libraries (w/o the '-l')<br> &lt;XPREFIX&gt;_LIBRARY_DIRS ... the paths of the libraries (w/o the '-L')<br> &lt;XPREFIX&gt;_LDFLAGS ... all required linker flags<br> &lt;XPREFIX&gt;_LDFLAGS_OTHER ... all other linker flags<br> &lt;XPREFIX&gt;_INCLUDE_DIRS ... the '-I' preprocessor flags (w/o the '-I')<br> &lt;XPREFIX&gt;_CFLAGS ... all required cflags<br> &lt;XPREFIX&gt;_CFLAGS_OTHER ... the other compiler flags<br></pre>
<p><br><pre> &lt;XPREFIX&gt; = &lt;PREFIX&gt; for common case<br> &lt;XPREFIX&gt; = &lt;PREFIX&gt;_STATIC for static linking<br></pre>
<p><br><p>There are some special variables whose prefix depends on the count of given modules. When there is only one module, &lt;PREFIX&gt; stays unchanged. When there are multiple modules, the prefix will be changed to &lt;PREFIX&gt;_&lt;MODNAME&gt;:<br><pre> &lt;XPREFIX&gt;_VERSION ... version of the module<br> &lt;XPREFIX&gt;_PREFIX ... prefix-directory of the module<br> &lt;XPREFIX&gt;_INCLUDEDIR ... include-dir of the module<br> &lt;XPREFIX&gt;_LIBDIR ... lib-dir of the module<br></pre>
<p><br><pre> &lt;XPREFIX&gt; = &lt;PREFIX&gt; when |MODULES| == 1, else<br> &lt;XPREFIX&gt; = &lt;PREFIX&gt;_&lt;MODNAME&gt;<br></pre>
<p><br><p>A &lt;MODULE&gt; parameter can have the following formats:<br><pre> {MODNAME} ... matches any version<br> {MODNAME}&gt;={VERSION} ... at least version &lt;VERSION&gt; is required<br> {MODNAME}={VERSION} ... exactly version &lt;VERSION&gt; is required<br> {MODNAME}&lt;={VERSION} ... modules must not be newer than &lt;VERSION&gt;<br></pre>
<p><br><p>Examples<br><pre> pkg_check_modules (GLIB2 glib-2.0)<br></pre>
<p><br><pre> pkg_check_modules (GLIB2 glib-2.0&gt;=2.10)<br> requires at least version 2.10 of glib2 and defines e.g.<br> GLIB2_VERSION=2.10.3<br></pre>
<p><br><pre> pkg_check_modules (FOO glib-2.0&gt;=2.10 gtk+-2.0)<br> requires both glib2 and gtk2, and defines e.g.<br> FOO_glib-2.0_VERSION=2.10.3<br> FOO_gtk+-2.0_VERSION=2.8.20<br></pre>
<p><br><pre> pkg_check_modules (XRENDER REQUIRED xrender)<br> defines e.g.:<br> XRENDER_LIBRARIES=Xrender;X11<br> XRENDER_STATIC_LIBRARIES=Xrender;X11;pthread;Xau;Xdmcp<br></pre>
<p><br><pre> pkg_search_module (BAR libxml-2.0 libxml2 libxml&gt;=2)<br></pre>
</li>
<li>
<a name="module:FindProducer"><b><code>FindProducer</code></b></a>: <br>
<p>Though Producer isn't directly part of OpenSceneGraph, its primary user is OSG so I consider this part of the Findosg* suite used to find OpenSceneGraph components. You'll notice that I accept OSGDIR as an environment path.<br><p>Each component is separate and you must opt in to each module. You must also opt into OpenGL (and OpenThreads?) as these modules won't do it for you. This is to allow you control over your own system piece by piece in case you need to opt out of certain components or change the Find behavior for a particular module (perhaps because the default FindOpenGL.cmake module doesn't work with your system as an example). If you want to use a more convenient module that includes everything, use the FindOpenSceneGraph.cmake instead of the Findosg*.cmake modules.<br><p>Locate Producer This module defines PRODUCER_LIBRARY PRODUCER_FOUND, if false, do not try to link to Producer PRODUCER_INCLUDE_DIR, where to find the headers<br><p>$PRODUCER_DIR is an environment variable that would correspond to the ./configure --prefix=$PRODUCER_DIR used in building osg.<br><p>Created by Eric Wing.
</li>
<li>
<a name="module:FindProtobuf"><b><code>FindProtobuf</code></b></a>: <br>
<p>Locate and configure the Google Protocol Buffers library. Defines the following variables:<br><pre> PROTOBUF_FOUND - Found the Google Protocol Buffers library<br> PROTOBUF_INCLUDE_DIRS - Include directories for Google Protocol Buffers<br> PROTOBUF_LIBRARIES - The protobuf library<br></pre>
<p><br><p>The following cache variables are also defined:<br><pre> PROTOBUF_LIBRARY - The protobuf library<br> PROTOBUF_PROTOC_LIBRARY - The protoc library<br> PROTOBUF_INCLUDE_DIR - The include directory for protocol buffers<br> PROTOBUF_PROTOC_EXECUTABLE - The protoc compiler<br></pre>
<p><br><pre> ====================================================================<br> Example:<br></pre>
<p><br><pre> find_package(Protobuf REQUIRED)<br> include_directories(${PROTOBUF_INCLUDE_DIRS})<br></pre>
<p><br><pre> include_directories(${CMAKE_CURRENT_BINARY_DIR})<br> PROTOBUF_GENERATE_CPP(PROTO_SRCS PROTO_HDRS foo.proto)<br> add_executable(bar bar.cc ${PROTO_SRCS} ${PROTO_HDRS})<br> target_link_libraries(bar ${PROTOBUF_LIBRARY})<br></pre>
<p><br><p>NOTE: You may need to link against pthreads, depending on the platform.<br><pre> ====================================================================<br></pre>
<p><br><p>PROTOBUF_GENERATE_CPP (public function)<br><pre> SRCS = Variable to define with autogenerated<br> source files<br> HDRS = Variable to define with autogenerated<br> header files<br> ARGN = proto files<br></pre>
<p><br><pre> ====================================================================<br></pre>
</li>
<li>
<a name="module:FindPythonInterp"><b><code>FindPythonInterp</code></b></a>: Find python interpreter<br>
<p>This module finds if Python interpreter is installed and determines where the executables are. This code sets the following variables:<br><pre> PYTHONINTERP_FOUND - Was the Python executable found<br> PYTHON_EXECUTABLE - path to the Python interpreter<br></pre>
<p><br>
</li>
<li>
<a name="module:FindPythonLibs"><b><code>FindPythonLibs</code></b></a>: Find python libraries<br>
<p>This module finds if Python is installed and determines where the include files and libraries are. It also determines what the name of the library is. This code sets the following variables:<br><pre> PYTHONLIBS_FOUND - have the Python libs been found<br> PYTHON_LIBRARIES - path to the python library<br> PYTHON_INCLUDE_PATH - path to where Python.h is found (deprecated)<br> PYTHON_INCLUDE_DIRS - path to where Python.h is found<br> PYTHON_DEBUG_LIBRARIES - path to the debug library<br></pre>
<p><br>
</li>
<li>
<a name="module:FindQt"><b><code>FindQt</code></b></a>: Searches for all installed versions of QT.<br>
<p>This should only be used if your project can work with multiple versions of QT. If not, you should just directly use FindQt4 or FindQt3. If multiple versions of QT are found on the machine, then The user must set the option DESIRED_QT_VERSION to the version they want to use. If only one version of qt is found on the machine, then the DESIRED_QT_VERSION is set to that version and the matching FindQt3 or FindQt4 module is included. Once the user sets DESIRED_QT_VERSION, then the FindQt3 or FindQt4 module is included.<br><pre> QT_REQUIRED if this is set to TRUE then if CMake can <br> not find QT4 or QT3 an error is raised <br> and a message is sent to the user.<br></pre>
<p><br><pre> DESIRED_QT_VERSION OPTION is created<br> QT4_INSTALLED is set to TRUE if qt4 is found.<br> QT3_INSTALLED is set to TRUE if qt3 is found.<br></pre>
</li>
<li>
<a name="module:FindQt3"><b><code>FindQt3</code></b></a>: Locate Qt include paths and libraries<br>
<p>This module defines:<br><pre> QT_INCLUDE_DIR - where to find qt.h, etc.<br> QT_LIBRARIES - the libraries to link against to use Qt.<br> QT_DEFINITIONS - definitions to use when<br> compiling code that uses Qt.<br> QT_FOUND - If false, don't try to use Qt.<br></pre>
<p><br><p>If you need the multithreaded version of Qt, set QT_MT_REQUIRED to TRUE<br><p>Also defined, but not for general use are:<br><pre> QT_MOC_EXECUTABLE, where to find the moc tool.<br> QT_UIC_EXECUTABLE, where to find the uic tool.<br> QT_QT_LIBRARY, where to find the Qt library.<br> QT_QTMAIN_LIBRARY, where to find the qtmain<br> library. This is only required by Qt3 on Windows.<br></pre>
</li>
<li>
<a name="module:FindQt4"><b><code>FindQt4</code></b></a>: Find QT 4<br>
<p>This module can be used to find Qt4. The most important issue is that the Qt4 qmake is available via the system path. This qmake is then used to detect basically everything else. This module defines a number of key variables and macros. The variable QT_USE_FILE is set which is the path to a CMake file that can be included to compile Qt 4 applications and libraries. It sets up the compilation environment for include directories, preprocessor defines and populates a QT_LIBRARIES variable.<br><p>Typical usage could be something like:<br><pre> find_package(Qt4 4.4.3 COMPONENTS QtCore QtGui QtXml REQUIRED )<br> include(${QT_USE_FILE})<br> add_executable(myexe main.cpp)<br> target_link_libraries(myexe ${QT_LIBRARIES})<br></pre>
<p><br><p>The minimum required version can be specified using the standard find_package()-syntax (see example above). For compatibility with older versions of FindQt4.cmake it is also possible to set the variable QT_MIN_VERSION to the minimum required version of Qt4 before the find_package(Qt4) command. If both are used, the version used in the find_package() command overrides the one from QT_MIN_VERSION.<br><p>When using the components argument, QT_USE_QT* variables are automatically set for the QT_USE_FILE to pick up. If one wishes to manually set them, the available ones to set include:<br><pre> QT_DONT_USE_QTCORE<br> QT_DONT_USE_QTGUI<br> QT_USE_QT3SUPPORT<br> QT_USE_QTASSISTANT<br> QT_USE_QAXCONTAINER<br> QT_USE_QAXSERVER<br> QT_USE_QTDESIGNER<br> QT_USE_QTMOTIF<br> QT_USE_QTMAIN<br> QT_USE_QTNETWORK<br> QT_USE_QTNSPLUGIN<br> QT_USE_QTOPENGL<br> QT_USE_QTSQL<br> QT_USE_QTXML<br> QT_USE_QTSVG<br> QT_USE_QTTEST<br> QT_USE_QTUITOOLS<br> QT_USE_QTDBUS<br> QT_USE_QTSCRIPT<br> QT_USE_QTASSISTANTCLIENT<br> QT_USE_QTHELP<br> QT_USE_QTWEBKIT<br> QT_USE_QTXMLPATTERNS<br> QT_USE_PHONON<br> QT_USE_QTSCRIPTTOOLS<br></pre>
<p><br><p>There are also some files that need processing by some Qt tools such as moc and uic. Listed below are macros that may be used to process those files.<br><pre> <br> macro QT4_WRAP_CPP(outfiles inputfile ... OPTIONS ...)<br> create moc code from a list of files containing Qt class with<br> the Q_OBJECT declaration. Per-direcotry preprocessor definitions <br> are also added. Options may be given to moc, such as those found<br> when executing "moc -help". <br></pre>
<p><br><pre> macro QT4_WRAP_UI(outfiles inputfile ... OPTIONS ...)<br> create code from a list of Qt designer ui files.<br> Options may be given to uic, such as those found<br> when executing "uic -help"<br></pre>
<p><br><pre> macro QT4_ADD_RESOURCES(outfiles inputfile ... OPTIONS ...)<br> create code from a list of Qt resource files.<br> Options may be given to rcc, such as those found<br> when executing "rcc -help"<br></pre>
<p><br><pre> macro QT4_GENERATE_MOC(inputfile outputfile )<br> creates a rule to run moc on infile and create outfile.<br> Use this if for some reason QT4_WRAP_CPP() isn't appropriate, e.g.<br> because you need a custom filename for the moc file or something similar.<br></pre>
<p><br><pre> macro QT4_AUTOMOC(sourcefile1 sourcefile2 ... )<br> This macro is still experimental.<br> It can be used to have moc automatically handled.<br> So if you have the files foo.h and foo.cpp, and in foo.h a <br> a class uses the Q_OBJECT macro, moc has to run on it. If you don't<br> want to use QT4_WRAP_CPP() (which is reliable and mature), you can insert<br> #include "foo.moc"<br> in foo.cpp and then give foo.cpp as argument to QT4_AUTOMOC(). This will the<br> scan all listed files at cmake-time for such included moc files and if it finds<br> them cause a rule to be generated to run moc at build time on the <br> accompanying header file foo.h.<br> If a source file has the SKIP_AUTOMOC property set it will be ignored by this macro.<br></pre>
<p><br><pre> macro QT4_ADD_DBUS_INTERFACE(outfiles interface basename)<br> create a the interface header and implementation files with the <br> given basename from the given interface xml file and add it to <br> the list of sources<br></pre>
<p><br><pre> macro QT4_ADD_DBUS_INTERFACES(outfiles inputfile ... )<br> create the interface header and implementation files <br> for all listed interface xml files<br> the name will be automatically determined from the name of the xml file<br></pre>
<p><br><pre> macro QT4_ADD_DBUS_ADAPTOR(outfiles xmlfile parentheader parentclassname [basename] [classname])<br> create a dbus adaptor (header and implementation file) from the xml file<br> describing the interface, and add it to the list of sources. The adaptor<br> forwards the calls to a parent class, defined in parentheader and named<br> parentclassname. The name of the generated files will be<br> &lt;basename&gt;adaptor.{cpp,h} where basename defaults to the basename of the xml file.<br> If &lt;classname&gt; is provided, then it will be used as the classname of the<br> adaptor itself.<br></pre>
<p><br><pre> macro QT4_GENERATE_DBUS_INTERFACE( header [interfacename] OPTIONS ...)<br> generate the xml interface file from the given header.<br> If the optional argument interfacename is omitted, the name of the <br> interface file is constructed from the basename of the header with<br> the suffix .xml appended.<br> Options may be given to qdbuscpp2xml, such as those found when executing "qdbuscpp2xml --help"<br></pre>
<p><br><pre> macro QT4_CREATE_TRANSLATION( qm_files directories ... sources ... <br> ts_files ... OPTIONS ...)<br> out: qm_files<br> in: directories sources ts_files<br> options: flags to pass to lupdate, such as -extensions to specify<br> extensions for a directory scan.<br> generates commands to create .ts (vie lupdate) and .qm<br> (via lrelease) - files from directories and/or sources. The ts files are <br> created and/or updated in the source tree (unless given with full paths).<br> The qm files are generated in the build tree.<br> Updating the translations can be done by adding the qm_files<br> to the source list of your library/executable, so they are<br> always updated, or by adding a custom target to control when<br> they get updated/generated.<br></pre>
<p><br><pre> macro QT4_ADD_TRANSLATION( qm_files ts_files ... )<br> out: qm_files<br> in: ts_files<br> generates commands to create .qm from .ts - files. The generated<br> filenames can be found in qm_files. The ts_files<br> must exists and are not updated in any way.<br></pre>
<p><br><p><br><pre> Below is a detailed list of variables that FindQt4.cmake sets.<br> QT_FOUND If false, don't try to use Qt.<br> QT4_FOUND If false, don't try to use Qt 4.<br></pre>
<p><br><pre> QT_VERSION_MAJOR The major version of Qt found.<br> QT_VERSION_MINOR The minor version of Qt found.<br> QT_VERSION_PATCH The patch version of Qt found.<br></pre>
<p><br><pre> QT_EDITION Set to the edition of Qt (i.e. DesktopLight)<br> QT_EDITION_DESKTOPLIGHT True if QT_EDITION == DesktopLight<br> QT_QTCORE_FOUND True if QtCore was found.<br> QT_QTGUI_FOUND True if QtGui was found.<br> QT_QT3SUPPORT_FOUND True if Qt3Support was found.<br> QT_QTASSISTANT_FOUND True if QtAssistant was found.<br> QT_QAXCONTAINER_FOUND True if QAxContainer was found (Windows only).<br> QT_QAXSERVER_FOUND True if QAxServer was found (Windows only).<br> QT_QTDBUS_FOUND True if QtDBus was found.<br> QT_QTDESIGNER_FOUND True if QtDesigner was found.<br> QT_QTDESIGNERCOMPONENTS True if QtDesignerComponents was found.<br> QT_QTMOTIF_FOUND True if QtMotif was found.<br> QT_QTNETWORK_FOUND True if QtNetwork was found.<br> QT_QTNSPLUGIN_FOUND True if QtNsPlugin was found.<br> QT_QTOPENGL_FOUND True if QtOpenGL was found.<br> QT_QTSQL_FOUND True if QtSql was found.<br> QT_QTXML_FOUND True if QtXml was found.<br> QT_QTSVG_FOUND True if QtSvg was found.<br> QT_QTSCRIPT_FOUND True if QtScript was found.<br> QT_QTTEST_FOUND True if QtTest was found.<br> QT_QTUITOOLS_FOUND True if QtUiTools was found.<br> QT_QTASSISTANTCLIENT_FOUND True if QtAssistantClient was found.<br> QT_QTHELP_FOUND True if QtHelp was found.<br> QT_QTWEBKIT_FOUND True if QtWebKit was found.<br> QT_QTXMLPATTERNS_FOUND True if QtXmlPatterns was found.<br> QT_PHONON_FOUND True if phonon was found.<br> QT_QTSCRIPTTOOLS_FOUND True if QtScriptTools was found.<br></pre>
<p><br><pre> QT_MAC_USE_COCOA For Mac OS X, its whether Cocoa or Carbon is used.<br> In general, this should not be used, but its useful<br> when having platform specific code.<br></pre>
<p><br><pre> QT_DEFINITIONS Definitions to use when compiling code that uses Qt.<br> You do not need to use this if you include QT_USE_FILE.<br> The QT_USE_FILE will also define QT_DEBUG and QT_NO_DEBUG<br> to fit your current build type. Those are not contained<br> in QT_DEFINITIONS.<br> <br> QT_INCLUDES List of paths to all include directories of <br> Qt4 QT_INCLUDE_DIR and QT_QTCORE_INCLUDE_DIR are<br> always in this variable even if NOTFOUND,<br> all other INCLUDE_DIRS are<br> only added if they are found.<br> You do not need to use this if you include QT_USE_FILE.<br> <br></pre>
<p><br><pre> Include directories for the Qt modules are listed here.<br> You do not need to use these variables if you include QT_USE_FILE.<br></pre>
<p><br><pre> QT_INCLUDE_DIR Path to "include" of Qt4<br> QT_QT3SUPPORT_INCLUDE_DIR Path to "include/Qt3Support" <br> QT_QTASSISTANT_INCLUDE_DIR Path to "include/QtAssistant" <br> QT_QTASSISTANTCLIENT_INCLUDE_DIR Path to "include/QtAssistant"<br> QT_QAXCONTAINER_INCLUDE_DIR Path to "include/ActiveQt" (Windows only)<br> QT_QAXSERVER_INCLUDE_DIR Path to "include/ActiveQt" (Windows only)<br> QT_QTCORE_INCLUDE_DIR Path to "include/QtCore" <br> QT_QTDESIGNER_INCLUDE_DIR Path to "include/QtDesigner" <br> QT_QTDESIGNERCOMPONENTS_INCLUDE_DIR Path to "include/QtDesigner"<br> QT_QTDBUS_INCLUDE_DIR Path to "include/QtDBus" <br> QT_QTGUI_INCLUDE_DIR Path to "include/QtGui" <br> QT_QTHELP_INCLUDE_DIR Path to "include/QtHelp"<br> QT_QTMOTIF_INCLUDE_DIR Path to "include/QtMotif" <br> QT_QTNETWORK_INCLUDE_DIR Path to "include/QtNetwork" <br> QT_QTNSPLUGIN_INCLUDE_DIR Path to "include/QtNsPlugin" <br> QT_QTOPENGL_INCLUDE_DIR Path to "include/QtOpenGL" <br> QT_QTSCRIPT_INCLUDE_DIR Path to "include/QtScript"<br> QT_QTSQL_INCLUDE_DIR Path to "include/QtSql" <br> QT_QTSVG_INCLUDE_DIR Path to "include/QtSvg"<br> QT_QTTEST_INCLUDE_DIR Path to "include/QtTest"<br> QT_QTWEBKIT_INCLUDE_DIR Path to "include/QtWebKit"<br> QT_QTXML_INCLUDE_DIR Path to "include/QtXml" <br> QT_QTXMLPATTERNS_INCLUDE_DIR Path to "include/QtXmlPatterns"<br> QT_PHONON_INCLUDE_DIR Path to "include/phonon"<br> QT_QTSCRIPTTOOLS_INCLUDE_DIR Path to "include/QtScriptTools"<br> <br> QT_BINARY_DIR Path to "bin" of Qt4<br> QT_LIBRARY_DIR Path to "lib" of Qt4<br> QT_PLUGINS_DIR Path to "plugins" for Qt4<br> QT_TRANSLATIONS_DIR Path to "translations" of Qt4<br> QT_DOC_DIR Path to "doc" of Qt4<br> QT_MKSPECS_DIR Path to "mkspecs" of Qt4<br> <br></pre>
<p><br><p>The Qt toolkit may contain both debug and release libraries. In that case, the following library variables will contain both. You do not need to use these variables if you include QT_USE_FILE, and use QT_LIBRARIES.<br><pre> QT_QT3SUPPORT_LIBRARY The Qt3Support library<br> QT_QTASSISTANT_LIBRARY The QtAssistant library<br> QT_QTASSISTANTCLIENT_LIBRARY The QtAssistantClient library<br> QT_QAXCONTAINER_LIBRARY The QAxContainer library (Windows only)<br> QT_QAXSERVER_LIBRARY The QAxServer library (Windows only)<br> QT_QTCORE_LIBRARY The QtCore library<br> QT_QTDBUS_LIBRARY The QtDBus library<br> QT_QTDESIGNER_LIBRARY The QtDesigner library<br> QT_QTDESIGNERCOMPONENTS_LIBRARY The QtDesignerComponents library<br> QT_QTGUI_LIBRARY The QtGui library<br> QT_QTHELP_LIBRARY The QtHelp library<br> QT_QTMOTIF_LIBRARY The QtMotif library<br> QT_QTNETWORK_LIBRARY The QtNetwork library<br> QT_QTNSPLUGIN_LIBRARY The QtNsPLugin library<br> QT_QTOPENGL_LIBRARY The QtOpenGL library<br> QT_QTSCRIPT_LIBRARY The QtScript library<br> QT_QTSQL_LIBRARY The QtSql library<br> QT_QTSVG_LIBRARY The QtSvg library<br> QT_QTTEST_LIBRARY The QtTest library<br> QT_QTUITOOLS_LIBRARY The QtUiTools library<br> QT_QTWEBKIT_LIBRARY The QtWebKit library<br> QT_QTXML_LIBRARY The QtXml library<br> QT_QTXMLPATTERNS_LIBRARY The QtXmlPatterns library<br> QT_QTMAIN_LIBRARY The qtmain library for Windows<br> QT_PHONON_LIBRARY The phonon library<br> QT_QTSCRIPTTOOLS_LIBRARY The QtScriptTools library<br> <br></pre>
<p>also defined, but NOT for general use are<br><pre> QT_MOC_EXECUTABLE Where to find the moc tool.<br> QT_UIC_EXECUTABLE Where to find the uic tool.<br> QT_UIC3_EXECUTABLE Where to find the uic3 tool.<br> QT_RCC_EXECUTABLE Where to find the rcc tool<br> QT_DBUSCPP2XML_EXECUTABLE Where to find the qdbuscpp2xml tool.<br> QT_DBUSXML2CPP_EXECUTABLE Where to find the qdbusxml2cpp tool.<br> QT_LUPDATE_EXECUTABLE Where to find the lupdate tool.<br> QT_LRELEASE_EXECUTABLE Where to find the lrelease tool.<br> QT_QCOLLECTIONGENERATOR_EXECUTABLE Where to find the qcollectiongenerator tool.<br> <br></pre>
<p><br><p>These are around for backwards compatibility they will be set<br><pre> QT_WRAP_CPP Set true if QT_MOC_EXECUTABLE is found<br> QT_WRAP_UI Set true if QT_UIC_EXECUTABLE is found<br> <br></pre>
<p>These variables do _NOT_ have any effect anymore (compared to FindQt.cmake)<br><pre> QT_MT_REQUIRED Qt4 is now always multithreaded<br> <br></pre>
<p>These variables are set to "" Because Qt structure changed (They make no sense in Qt4)<br><pre> QT_QT_LIBRARY Qt-Library is now split<br></pre>
</li>
<li>
<a name="module:FindQuickTime"><b><code>FindQuickTime</code></b></a>: <br>
<p>Locate QuickTime This module defines QUICKTIME_LIBRARY QUICKTIME_FOUND, if false, do not try to link to gdal QUICKTIME_INCLUDE_DIR, where to find the headers<br><p>$QUICKTIME_DIR is an environment variable that would correspond to the ./configure --prefix=$QUICKTIME_DIR<br><p>Created by Eric Wing.
</li>
<li>
<a name="module:FindRTI"><b><code>FindRTI</code></b></a>: Try to find M&amp;S HLA RTI libraries<br>
<p>This module finds if any HLA RTI is installed and locates the standard RTI include files and libraries.<br><p>RTI is a simulation infrastructure standardized by IEEE and SISO. It has a well defined C++ API that assures that simulation applications are independent on a particular RTI implementation.<br><pre> <a href="http://en.wikipedia.org/wiki/Run-Time_Infrastructure_">http://en.wikipedia.org/wiki/Run-Time_Infrastructure_</a>(simulation)<br></pre>
<p><br><p>This code sets the following variables:<br><pre> RTI_INCLUDE_DIR = the directory where RTI includes file are found<br> RTI_LIBRARIES = The libraries to link against to use RTI<br> RTI_DEFINITIONS = -DRTI_USES_STD_FSTREAM<br> RTI_FOUND = Set to FALSE if any HLA RTI was not found<br></pre>
<p><br><p>Report problems to &lt;certi-devel@nongnu.org&gt;
</li>
<li>
<a name="module:FindRuby"><b><code>FindRuby</code></b></a>: Find Ruby<br>
<p>This module finds if Ruby is installed and determines where the include files and libraries are. Ruby 1.8 and 1.9 are supported. The minimum required version specified in the find_package() command is honored. It also determines what the name of the library is. This code sets the following variables:<br><pre> RUBY_EXECUTABLE = full path to the ruby binary<br> RUBY_INCLUDE_DIRS = include dirs to be used when using the ruby library<br> RUBY_LIBRARY = full path to the ruby library<br> RUBY_VERSION = the version of ruby which was found, e.g. "1.8.7"<br> RUBY_FOUND = set to true if ruby ws found successfully<br></pre>
<p><br><pre> RUBY_INCLUDE_PATH = same as RUBY_INCLUDE_DIRS, only provided for compatibility reasons, don't use it<br></pre>
</li>
<li>
<a name="module:FindSDL"><b><code>FindSDL</code></b></a>: <br>
<p>Locate SDL library This module defines SDL_LIBRARY, the name of the library to link against SDL_FOUND, if false, do not try to link to SDL SDL_INCLUDE_DIR, where to find SDL.h<br><p>This module responds to the the flag: SDL_BUILDING_LIBRARY If this is defined, then no SDL_main will be linked in because only applications need main(). Otherwise, it is assumed you are building an application and this module will attempt to locate and set the the proper link flags as part of the returned SDL_LIBRARY variable.<br><p>Don't forget to include SDLmain.h and SDLmain.m your project for the OS X framework based version. (Other versions link to -lSDLmain which this module will try to find on your behalf.) Also for OS X, this module will automatically add the -framework Cocoa on your behalf.<br><p><br><p>Additional Note: If you see an empty SDL_LIBRARY_TEMP in your configuration and no SDL_LIBRARY, it means CMake did not find your SDL library (SDL.dll, libsdl.so, SDL.framework, etc). Set SDL_LIBRARY_TEMP to point to your SDL library, and configure again. Similarly, if you see an empty SDLMAIN_LIBRARY, you should set this value as appropriate. These values are used to generate the final SDL_LIBRARY variable, but when these values are unset, SDL_LIBRARY does not get created.<br><p><br><p>$SDLDIR is an environment variable that would correspond to the ./configure --prefix=$SDLDIR used in building SDL. l.e.galup 9-20-02<br><p>Modified by Eric Wing. Added code to assist with automated building by using environmental variables and providing a more controlled/consistent search behavior. Added new modifications to recognize OS X frameworks and additional Unix paths (FreeBSD, etc). Also corrected the header search path to follow "proper" SDL guidelines. Added a search for SDLmain which is needed by some platforms. Added a search for threads which is needed by some platforms. Added needed compile switches for MinGW.<br><p>On OSX, this will prefer the Framework version (if found) over others. People will have to manually change the cache values of SDL_LIBRARY to override this selection or set the CMake environment CMAKE_INCLUDE_PATH to modify the search paths.<br><p>Note that the header path has changed from SDL/SDL.h to just SDL.h This needed to change because "proper" SDL convention is #include "SDL.h", not &lt;SDL/SDL.h&gt;. This is done for portability reasons because not all systems place things in SDL/ (see FreeBSD).
</li>
<li>
<a name="module:FindSDL_image"><b><code>FindSDL_image</code></b></a>: <br>
<p>Locate SDL_image library This module defines SDLIMAGE_LIBRARY, the name of the library to link against SDLIMAGE_FOUND, if false, do not try to link to SDL SDLIMAGE_INCLUDE_DIR, where to find SDL/SDL.h<br><p>$SDLDIR is an environment variable that would correspond to the ./configure --prefix=$SDLDIR used in building SDL.<br><p>Created by Eric Wing. This was influenced by the FindSDL.cmake module, but with modifications to recognize OS X frameworks and additional Unix paths (FreeBSD, etc).
</li>
<li>
<a name="module:FindSDL_mixer"><b><code>FindSDL_mixer</code></b></a>: <br>
<p>Locate SDL_mixer library This module defines SDLMIXER_LIBRARY, the name of the library to link against SDLMIXER_FOUND, if false, do not try to link to SDL SDLMIXER_INCLUDE_DIR, where to find SDL/SDL.h<br><p>$SDLDIR is an environment variable that would correspond to the ./configure --prefix=$SDLDIR used in building SDL.<br><p>Created by Eric Wing. This was influenced by the FindSDL.cmake module, but with modifications to recognize OS X frameworks and additional Unix paths (FreeBSD, etc).
</li>
<li>
<a name="module:FindSDL_net"><b><code>FindSDL_net</code></b></a>: <br>
<p>Locate SDL_net library This module defines SDLNET_LIBRARY, the name of the library to link against SDLNET_FOUND, if false, do not try to link against SDLNET_INCLUDE_DIR, where to find the headers<br><p>$SDLDIR is an environment variable that would correspond to the ./configure --prefix=$SDLDIR used in building SDL.<br><p>Created by Eric Wing. This was influenced by the FindSDL.cmake module, but with modifications to recognize OS X frameworks and additional Unix paths (FreeBSD, etc).
</li>
<li>
<a name="module:FindSDL_sound"><b><code>FindSDL_sound</code></b></a>: <br>
<p>Locates the SDL_sound library
</li>
<li>
<a name="module:FindSDL_ttf"><b><code>FindSDL_ttf</code></b></a>: <br>
<p>Locate SDL_ttf library This module defines SDLTTF_LIBRARY, the name of the library to link against SDLTTF_FOUND, if false, do not try to link to SDL SDLTTF_INCLUDE_DIR, where to find SDL/SDL.h<br><p>$SDLDIR is an environment variable that would correspond to the ./configure --prefix=$SDLDIR used in building SDL.<br><p>Created by Eric Wing. This was influenced by the FindSDL.cmake module, but with modifications to recognize OS X frameworks and additional Unix paths (FreeBSD, etc).
</li>
<li>
<a name="module:FindSWIG"><b><code>FindSWIG</code></b></a>: Find SWIG<br>
<p>This module finds an installed SWIG. It sets the following variables:<br><pre> SWIG_FOUND - set to true if SWIG is found<br> SWIG_DIR - the directory where swig is installed<br> SWIG_EXECUTABLE - the path to the swig executable<br> SWIG_VERSION - the version number of the swig executable<br></pre>
<p><br><p>All informations are collected from the SWIG_EXECUTABLE so the version to be found can be changed from the command line by means of setting SWIG_EXECUTABLE<br>
</li>
<li>
<a name="module:FindSelfPackers"><b><code>FindSelfPackers</code></b></a>: Find upx<br>
<p>This module looks for some executable packers (i.e. softwares that compress executables or shared libs into on-the-fly self-extracting executables or shared libs. Examples:<br><pre> UPX: <a href="http://wildsau.idv.uni-linz.ac.at/mfx/upx.html">http://wildsau.idv.uni-linz.ac.at/mfx/upx.html</a><br></pre>
</li>
<li>
<a name="module:FindSquish"><b><code>FindSquish</code></b></a>: -- Typical Use<br>
<p><br><p>This module can be used to find Squish (currently support is aimed at version 3).<br><pre> SQUISH_FOUND If false, don't try to use Squish<br> SQUISH_VERSION_MAJOR The major version of Squish found<br> SQUISH_VERSION_MINOR The minor version of Squish found<br> SQUISH_VERSION_PATCH The patch version of Squish found<br></pre>
<p><br><pre> SQUISH_INSTALL_DIR The Squish installation directory (containing bin, lib, etc)<br> SQUISH_SERVER_EXECUTABLE The squishserver executable<br> SQUISH_CLIENT_EXECUTABLE The squishrunner executable<br></pre>
<p><br><pre> SQUISH_INSTALL_DIR_FOUND Was the install directory found?<br> SQUISH_SERVER_EXECUTABLE_FOUND Was the server executable found?<br> SQUISH_CLIENT_EXECUTABLE_FOUND Was the client executable found?<br></pre>
<p><br><p>macro SQUISH_ADD_TEST(testName applicationUnderTest testSuite testCase)<br><pre> ENABLE_TESTING()<br> FIND_PACKAGE(Squish)<br> IF (SQUISH_FOUND)<br> SQUISH_ADD_TEST(myTestName myApplication testSuiteName testCaseName)<br> ENDIF (SQUISH_FOUND)<br></pre>
<p><br>
</li>
<li>
<a name="module:FindSubversion"><b><code>FindSubversion</code></b></a>: Extract information from a subversion working copy<br>
<p>The module defines the following variables:<br><pre> Subversion_SVN_EXECUTABLE - path to svn command line client<br> Subversion_VERSION_SVN - version of svn command line client<br> Subversion_FOUND - true if the command line client was found<br></pre>
<p>If the command line client executable is found the macro<br><pre> Subversion_WC_INFO(&lt;dir&gt; &lt;var-prefix&gt;)<br></pre>
<p>is defined to extract information of a subversion working copy at a given location. The macro defines the following variables:<br><pre> &lt;var-prefix&gt;_WC_URL - url of the repository (at &lt;dir&gt;)<br> &lt;var-prefix&gt;_WC_ROOT - root url of the repository<br> &lt;var-prefix&gt;_WC_REVISION - current revision<br> &lt;var-prefix&gt;_WC_LAST_CHANGED_AUTHOR - author of last commit<br> &lt;var-prefix&gt;_WC_LAST_CHANGED_DATE - date of last commit<br> &lt;var-prefix&gt;_WC_LAST_CHANGED_REV - revision of last commit<br> &lt;var-prefix&gt;_WC_LAST_CHANGED_LOG - last log of base revision<br> &lt;var-prefix&gt;_WC_INFO - output of command `svn info &lt;dir&gt;'<br></pre>
<p>Example usage:<br><pre> FIND_PACKAGE(Subversion)<br> IF(Subversion_FOUND)<br> Subversion_WC_INFO(${PROJECT_SOURCE_DIR} Project)<br> MESSAGE("Current revision is ${Project_WC_REVISION}")<br> Subversion_WC_LOG(${PROJECT_SOURCE_DIR} Project)<br> MESSAGE("Last changed log is ${Project_LAST_CHANGED_LOG}")<br> ENDIF(Subversion_FOUND)<br></pre>
</li>
<li>
<a name="module:FindTCL"><b><code>FindTCL</code></b></a>: TK_INTERNAL_PATH was removed.<br>
<p>This module finds if Tcl is installed and determines where the include files and libraries are. It also determines what the name of the library is. This code sets the following variables:<br><pre> TCL_FOUND = Tcl was found<br> TK_FOUND = Tk was found<br> TCLTK_FOUND = Tcl and Tk were found<br> TCL_LIBRARY = path to Tcl library (tcl tcl80)<br> TCL_INCLUDE_PATH = path to where tcl.h can be found<br> TCL_TCLSH = path to tclsh binary (tcl tcl80)<br> TK_LIBRARY = path to Tk library (tk tk80 etc)<br> TK_INCLUDE_PATH = path to where tk.h can be found<br> TK_WISH = full path to the wish executable<br></pre>
<p><br><p>In an effort to remove some clutter and clear up some issues for people who are not necessarily Tcl/Tk gurus/developpers, some variables were moved or removed. Changes compared to CMake 2.4 are:<br><pre> =&gt; they were only useful for people writing Tcl/Tk extensions.<br> =&gt; these libs are not packaged by default with Tcl/Tk distributions. <br> Even when Tcl/Tk is built from source, several flavors of debug libs<br> are created and there is no real reason to pick a single one<br> specifically (say, amongst tcl84g, tcl84gs, or tcl84sgx). <br> Let's leave that choice to the user by allowing him to assign <br> TCL_LIBRARY to any Tcl library, debug or not.<br> =&gt; this ended up being only a Win32 variable, and there is a lot of<br> confusion regarding the location of this file in an installed Tcl/Tk<br> tree anyway (see 8.5 for example). If you need the internal path at<br> this point it is safer you ask directly where the *source* tree is<br> and dig from there.<br></pre>
</li>
<li>
<a name="module:FindTIFF"><b><code>FindTIFF</code></b></a>: Find TIFF library<br>
<p>Find the native TIFF includes and library This module defines<br><pre> TIFF_INCLUDE_DIR, where to find tiff.h, etc.<br> TIFF_LIBRARIES, libraries to link against to use TIFF.<br> TIFF_FOUND, If false, do not try to use TIFF.<br></pre>
<p>also defined, but not for general use are<br><pre> TIFF_LIBRARY, where to find the TIFF library.<br></pre>
</li>
<li>
<a name="module:FindTclStub"><b><code>FindTclStub</code></b></a>: TCL_STUB_LIBRARY_DEBUG and TK_STUB_LIBRARY_DEBUG were removed.<br>
<p>This module finds Tcl stub libraries. It first finds Tcl include files and libraries by calling FindTCL.cmake. How to Use the Tcl Stubs Library:<br><pre> <a href="http://tcl.activestate.com/doc/howto/stubs.html">http://tcl.activestate.com/doc/howto/stubs.html</a><br></pre>
<p>Using Stub Libraries:<br><pre> <a href="http://safari.oreilly.com/0130385603/ch48lev1sec3">http://safari.oreilly.com/0130385603/ch48lev1sec3</a><br></pre>
<p>This code sets the following variables:<br><pre> TCL_STUB_LIBRARY = path to Tcl stub library<br> TK_STUB_LIBRARY = path to Tk stub library<br> TTK_STUB_LIBRARY = path to ttk stub library<br></pre>
<p><br><p>In an effort to remove some clutter and clear up some issues for people who are not necessarily Tcl/Tk gurus/developpers, some variables were moved or removed. Changes compared to CMake 2.4 are:<br><pre> =&gt; these libs are not packaged by default with Tcl/Tk distributions. <br> Even when Tcl/Tk is built from source, several flavors of debug libs<br> are created and there is no real reason to pick a single one<br> specifically (say, amongst tclstub84g, tclstub84gs, or tclstub84sgx). <br> Let's leave that choice to the user by allowing him to assign <br> TCL_STUB_LIBRARY to any Tcl library, debug or not.<br></pre>
</li>
<li>
<a name="module:FindTclsh"><b><code>FindTclsh</code></b></a>: Find tclsh<br>
<p>This module finds if TCL is installed and determines where the include files and libraries are. It also determines what the name of the library is. This code sets the following variables:<br><pre> TCLSH_FOUND = TRUE if tclsh has been found<br> TCL_TCLSH = the path to the tclsh executable<br></pre>
<p>In cygwin, look for the cygwin version first. Don't look for it later to avoid finding the cygwin version on a Win32 build.
</li>
<li>
<a name="module:FindThreads"><b><code>FindThreads</code></b></a>: This module determines the thread library of the system.<br>
<p>The following variables are set<br><pre> CMAKE_THREAD_LIBS_INIT - the thread library<br> CMAKE_USE_SPROC_INIT - are we using sproc?<br> CMAKE_USE_WIN32_THREADS_INIT - using WIN32 threads?<br> CMAKE_USE_PTHREADS_INIT - are we using pthreads<br> CMAKE_HP_PTHREADS_INIT - are we using hp pthreads<br></pre>
</li>
<li>
<a name="module:FindUnixCommands"><b><code>FindUnixCommands</code></b></a>: Find unix commands from cygwin<br>
<p>This module looks for some usual Unix commands.<br>
</li>
<li>
<a name="module:FindVTK"><b><code>FindVTK</code></b></a>: Find a VTK installation or build tree.<br>
<p>The following variables are set if VTK is found. If VTK is not found, VTK_FOUND is set to false.<br><pre> VTK_FOUND - Set to true when VTK is found.<br> VTK_USE_FILE - CMake file to use VTK.<br> VTK_MAJOR_VERSION - The VTK major version number.<br> VTK_MINOR_VERSION - The VTK minor version number <br> (odd non-release).<br> VTK_BUILD_VERSION - The VTK patch level <br> (meaningless for odd minor).<br> VTK_INCLUDE_DIRS - Include directories for VTK<br> VTK_LIBRARY_DIRS - Link directories for VTK libraries<br> VTK_KITS - List of VTK kits, in CAPS <br> (COMMON,IO,) etc.<br> VTK_LANGUAGES - List of wrapped languages, in CAPS<br> (TCL, PYHTON,) etc.<br></pre>
<p>The following cache entries must be set by the user to locate VTK:<br><pre> VTK_DIR - The directory containing VTKConfig.cmake. <br> This is either the root of the build tree,<br> or the lib/vtk directory. This is the <br> only cache entry.<br></pre>
<p>The following variables are set for backward compatibility and should not be used in new code:<br><pre> USE_VTK_FILE - The full path to the UseVTK.cmake file.<br> This is provided for backward <br> compatibility. Use VTK_USE_FILE <br> instead.<br></pre>
<p><br>
</li>
<li>
<a name="module:FindWget"><b><code>FindWget</code></b></a>: Find wget<br>
<p>This module looks for wget. This module defines the following values:<br><pre> WGET_EXECUTABLE: the full path to the wget tool.<br> WGET_FOUND: True if wget has been found.<br></pre>
</li>
<li>
<a name="module:FindWish"><b><code>FindWish</code></b></a>: Find wish installation<br>
<p>This module finds if TCL is installed and determines where the include files and libraries are. It also determines what the name of the library is. This code sets the following variables:<br><pre> TK_WISH = the path to the wish executable<br></pre>
<p><br><p>if UNIX is defined, then it will look for the cygwin version first
</li>
<li>
<a name="module:FindX11"><b><code>FindX11</code></b></a>: Find X11 installation<br>
<p>Try to find X11 on UNIX systems. The following values are defined<br><pre> X11_FOUND - True if X11 is available<br> X11_INCLUDE_DIR - include directories to use X11<br> X11_LIBRARIES - link against these to use X11<br></pre>
<p><br><p>and also the following more fine grained variables: Include paths: X11_ICE_INCLUDE_PATH, X11_ICE_LIB, X11_ICE_FOUND<br><pre> X11_Xaccessrules_INCLUDE_PATH, X11_Xaccess_FOUND<br> X11_Xaccessstr_INCLUDE_PATH, X11_Xaccess_FOUND<br> X11_Xau_INCLUDE_PATH, X11_Xau_LIB, X11_Xau_FOUND<br> X11_Xcomposite_INCLUDE_PATH, X11_Xcomposite_LIB, X11_Xcomposite_FOUND<br> X11_Xcursor_INCLUDE_PATH, X11_Xcursor_LIB, X11_Xcursor_FOUND<br> X11_Xdamage_INCLUDE_PATH, X11_Xdamage_LIB, X11_Xdamage_FOUND<br> X11_Xdmcp_INCLUDE_PATH, X11_Xdmcp_LIB, X11_Xdmcp_FOUND<br> X11_Xext_LIB, X11_Xext_FOUND<br> X11_dpms_INCLUDE_PATH, (in X11_Xext_LIB), X11_dpms_FOUND<br> X11_XShm_INCLUDE_PATH, (in X11_Xext_LIB), X11_XShm_FOUND<br> X11_Xshape_INCLUDE_PATH, (in X11_Xext_LIB), X11_Xshape_FOUND<br> X11_xf86misc_INCLUDE_PATH, X11_Xxf86misc_LIB, X11_xf86misc_FOUND<br> X11_xf86vmode_INCLUDE_PATH, X11_xf86vmode_FOUND<br> X11_Xfixes_INCLUDE_PATH, X11_Xfixes_LIB, X11_Xfixes_FOUND<br> X11_Xft_INCLUDE_PATH, X11_Xft_LIB, X11_Xft_FOUND<br> X11_Xinerama_INCLUDE_PATH, X11_Xinerama_LIB, X11_Xinerama_FOUND<br> X11_Xinput_INCLUDE_PATH, X11_Xinput_LIB, X11_Xinput_FOUND<br> X11_Xkb_INCLUDE_PATH, X11_Xkb_FOUND<br> X11_Xkblib_INCLUDE_PATH, X11_Xkb_FOUND<br> X11_Xpm_INCLUDE_PATH, X11_Xpm_LIB, X11_Xpm_FOUND<br> X11_XTest_INCLUDE_PATH, X11_XTest_LIB, X11_XTest_FOUND<br> X11_Xrandr_INCLUDE_PATH, X11_Xrandr_LIB, X11_Xrandr_FOUND<br> X11_Xrender_INCLUDE_PATH, X11_Xrender_LIB, X11_Xrender_FOUND<br> X11_Xscreensaver_INCLUDE_PATH, X11_Xscreensaver_LIB, X11_Xscreensaver_FOUND<br> X11_Xt_INCLUDE_PATH, X11_Xt_LIB, X11_Xt_FOUND<br> X11_Xutil_INCLUDE_PATH, X11_Xutil_FOUND<br> X11_Xv_INCLUDE_PATH, X11_Xv_LIB, X11_Xv_FOUND<br></pre>
</li>
<li>
<a name="module:FindXMLRPC"><b><code>FindXMLRPC</code></b></a>: Find xmlrpc<br>
<p>Find the native XMLRPC headers and libraries.<br><pre> XMLRPC_INCLUDE_DIRS - where to find xmlrpc.h, etc.<br> XMLRPC_LIBRARIES - List of libraries when using xmlrpc.<br> XMLRPC_FOUND - True if xmlrpc found.<br></pre>
<p>XMLRPC modules may be specified as components for this find module. Modules may be listed by running "xmlrpc-c-config". Modules include:<br><pre> c++ C++ wrapper code<br> libwww-client libwww-based client<br> cgi-server CGI-based server<br> abyss-server ABYSS-based server<br></pre>
<p>Typical usage:<br><pre> FIND_PACKAGE(XMLRPC REQUIRED libwww-client)<br></pre>
</li>
<li>
<a name="module:FindZLIB"><b><code>FindZLIB</code></b></a>: Find zlib<br>
<p>Find the native ZLIB includes and library<br><pre> ZLIB_INCLUDE_DIRS - where to find zlib.h, etc.<br> ZLIB_LIBRARIES - List of libraries when using zlib.<br> ZLIB_FOUND - True if zlib found.<br></pre>
</li>
<li>
<a name="module:Findosg"><b><code>Findosg</code></b></a>: <br>
<p><br><p>NOTE: It is highly recommended that you use the new FindOpenSceneGraph.cmake introduced in CMake 2.6.3 and not use this Find module directly.<br><p>This is part of the Findosg* suite used to find OpenSceneGraph components. Each component is separate and you must opt in to each module. You must also opt into OpenGL and OpenThreads (and Producer if needed) as these modules won't do it for you. This is to allow you control over your own system piece by piece in case you need to opt out of certain components or change the Find behavior for a particular module (perhaps because the default FindOpenGL.cmake module doesn't work with your system as an example). If you want to use a more convenient module that includes everything, use the FindOpenSceneGraph.cmake instead of the Findosg*.cmake modules.<br><p>Locate osg This module defines<br><p>OSG_FOUND - Was the Osg found? OSG_INCLUDE_DIR - Where to find the headers OSG_LIBRARIES - The libraries to link against for the OSG (use this)<br><p>OSG_LIBRARY - The OSG library OSG_LIBRARY_DEBUG - The OSG debug library<br><p>$OSGDIR is an environment variable that would correspond to the ./configure --prefix=$OSGDIR used in building osg.<br><p>Created by Eric Wing.
</li>
<li>
<a name="module:FindosgAnimation"><b><code>FindosgAnimation</code></b></a>: <br>
<p>This is part of the Findosg* suite used to find OpenSceneGraph components. Each component is separate and you must opt in to each module. You must also opt into OpenGL and OpenThreads (and Producer if needed) as these modules won't do it for you. This is to allow you control over your own system piece by piece in case you need to opt out of certain components or change the Find behavior for a particular module (perhaps because the default FindOpenGL.cmake module doesn't work with your system as an example). If you want to use a more convenient module that includes everything, use the FindOpenSceneGraph.cmake instead of the Findosg*.cmake modules.<br><p>Locate osgAnimation This module defines<br><p>OSGANIMATION_FOUND - Was osgAnimation found? OSGANIMATION_INCLUDE_DIR - Where to find the headers OSGANIMATION_LIBRARIES - The libraries to link against for the OSG (use this)<br><p>OSGANIMATION_LIBRARY - The OSG library OSGANIMATION_LIBRARY_DEBUG - The OSG debug library<br><p>$OSGDIR is an environment variable that would correspond to the ./configure --prefix=$OSGDIR used in building osg.<br><p>Created by Eric Wing.
</li>
<li>
<a name="module:FindosgDB"><b><code>FindosgDB</code></b></a>: <br>
<p>This is part of the Findosg* suite used to find OpenSceneGraph components. Each component is separate and you must opt in to each module. You must also opt into OpenGL and OpenThreads (and Producer if needed) as these modules won't do it for you. This is to allow you control over your own system piece by piece in case you need to opt out of certain components or change the Find behavior for a particular module (perhaps because the default FindOpenGL.cmake module doesn't work with your system as an example). If you want to use a more convenient module that includes everything, use the FindOpenSceneGraph.cmake instead of the Findosg*.cmake modules.<br><p>Locate osgDB This module defines<br><p>OSGDB_FOUND - Was osgDB found? OSGDB_INCLUDE_DIR - Where to find the headers OSGDB_LIBRARIES - The libraries to link against for the osgDB (use this)<br><p>OSGDB_LIBRARY - The osgDB library OSGDB_LIBRARY_DEBUG - The osgDB debug library<br><p>$OSGDIR is an environment variable that would correspond to the ./configure --prefix=$OSGDIR used in building osg.<br><p>Created by Eric Wing.
</li>
<li>
<a name="module:FindosgFX"><b><code>FindosgFX</code></b></a>: <br>
<p>This is part of the Findosg* suite used to find OpenSceneGraph components. Each component is separate and you must opt in to each module. You must also opt into OpenGL and OpenThreads (and Producer if needed) as these modules won't do it for you. This is to allow you control over your own system piece by piece in case you need to opt out of certain components or change the Find behavior for a particular module (perhaps because the default FindOpenGL.cmake module doesn't work with your system as an example). If you want to use a more convenient module that includes everything, use the FindOpenSceneGraph.cmake instead of the Findosg*.cmake modules.<br><p>Locate osgFX This module defines<br><p>OSGFX_FOUND - Was osgFX found? OSGFX_INCLUDE_DIR - Where to find the headers OSGFX_LIBRARIES - The libraries to link against for the osgFX (use this)<br><p>OSGFX_LIBRARY - The osgFX library OSGFX_LIBRARY_DEBUG - The osgFX debug library<br><p>$OSGDIR is an environment variable that would correspond to the ./configure --prefix=$OSGDIR used in building osg.<br><p>Created by Eric Wing.
</li>
<li>
<a name="module:FindosgGA"><b><code>FindosgGA</code></b></a>: <br>
<p>This is part of the Findosg* suite used to find OpenSceneGraph components. Each component is separate and you must opt in to each module. You must also opt into OpenGL and OpenThreads (and Producer if needed) as these modules won't do it for you. This is to allow you control over your own system piece by piece in case you need to opt out of certain components or change the Find behavior for a particular module (perhaps because the default FindOpenGL.cmake module doesn't work with your system as an example). If you want to use a more convenient module that includes everything, use the FindOpenSceneGraph.cmake instead of the Findosg*.cmake modules.<br><p>Locate osgGA This module defines<br><p>OSGGA_FOUND - Was osgGA found? OSGGA_INCLUDE_DIR - Where to find the headers OSGGA_LIBRARIES - The libraries to link against for the osgGA (use this)<br><p>OSGGA_LIBRARY - The osgGA library OSGGA_LIBRARY_DEBUG - The osgGA debug library<br><p>$OSGDIR is an environment variable that would correspond to the ./configure --prefix=$OSGDIR used in building osg.<br><p>Created by Eric Wing.
</li>
<li>
<a name="module:FindosgIntrospection"><b><code>FindosgIntrospection</code></b></a>: <br>
<p>This is part of the Findosg* suite used to find OpenSceneGraph components. Each component is separate and you must opt in to each module. You must also opt into OpenGL and OpenThreads (and Producer if needed) as these modules won't do it for you. This is to allow you control over your own system piece by piece in case you need to opt out of certain components or change the Find behavior for a particular module (perhaps because the default FindOpenGL.cmake module doesn't work with your system as an example). If you want to use a more convenient module that includes everything, use the FindOpenSceneGraph.cmake instead of the Findosg*.cmake modules.<br><p>Locate osgINTROSPECTION This module defines<br><p>OSGINTROSPECTION_FOUND - Was osgIntrospection found? OSGINTROSPECTION_INCLUDE_DIR - Where to find the headers OSGINTROSPECTION_LIBRARIES - The libraries to link for osgIntrospection (use this)<br><p>OSGINTROSPECTION_LIBRARY - The osgIntrospection library OSGINTROSPECTION_LIBRARY_DEBUG - The osgIntrospection debug library<br><p>$OSGDIR is an environment variable that would correspond to the ./configure --prefix=$OSGDIR used in building osg.<br><p>Created by Eric Wing.
</li>
<li>
<a name="module:FindosgManipulator"><b><code>FindosgManipulator</code></b></a>: <br>
<p>This is part of the Findosg* suite used to find OpenSceneGraph components. Each component is separate and you must opt in to each module. You must also opt into OpenGL and OpenThreads (and Producer if needed) as these modules won't do it for you. This is to allow you control over your own system piece by piece in case you need to opt out of certain components or change the Find behavior for a particular module (perhaps because the default FindOpenGL.cmake module doesn't work with your system as an example). If you want to use a more convenient module that includes everything, use the FindOpenSceneGraph.cmake instead of the Findosg*.cmake modules.<br><p>Locate osgManipulator This module defines<br><p>OSGMANIPULATOR_FOUND - Was osgManipulator found? OSGMANIPULATOR_INCLUDE_DIR - Where to find the headers OSGMANIPULATOR_LIBRARIES - The libraries to link for osgManipulator (use this)<br><p>OSGMANIPULATOR_LIBRARY - The osgManipulator library OSGMANIPULATOR_LIBRARY_DEBUG - The osgManipulator debug library<br><p>$OSGDIR is an environment variable that would correspond to the ./configure --prefix=$OSGDIR used in building osg.<br><p>Created by Eric Wing.
</li>
<li>
<a name="module:FindosgParticle"><b><code>FindosgParticle</code></b></a>: <br>
<p>This is part of the Findosg* suite used to find OpenSceneGraph components. Each component is separate and you must opt in to each module. You must also opt into OpenGL and OpenThreads (and Producer if needed) as these modules won't do it for you. This is to allow you control over your own system piece by piece in case you need to opt out of certain components or change the Find behavior for a particular module (perhaps because the default FindOpenGL.cmake module doesn't work with your system as an example). If you want to use a more convenient module that includes everything, use the FindOpenSceneGraph.cmake instead of the Findosg*.cmake modules.<br><p>Locate osgParticle This module defines<br><p>OSGPARTICLE_FOUND - Was osgParticle found? OSGPARTICLE_INCLUDE_DIR - Where to find the headers OSGPARTICLE_LIBRARIES - The libraries to link for osgParticle (use this)<br><p>OSGPARTICLE_LIBRARY - The osgParticle library OSGPARTICLE_LIBRARY_DEBUG - The osgParticle debug library<br><p>$OSGDIR is an environment variable that would correspond to the ./configure --prefix=$OSGDIR used in building osg.<br><p>Created by Eric Wing.
</li>
<li>
<a name="module:FindosgProducer"><b><code>FindosgProducer</code></b></a>: <br>
<p>This is part of the Findosg* suite used to find OpenSceneGraph components. Each component is separate and you must opt in to each module. You must also opt into OpenGL and OpenThreads (and Producer if needed) as these modules won't do it for you. This is to allow you control over your own system piece by piece in case you need to opt out of certain components or change the Find behavior for a particular module (perhaps because the default FindOpenGL.cmake module doesn't work with your system as an example). If you want to use a more convenient module that includes everything, use the FindOpenSceneGraph.cmake instead of the Findosg*.cmake modules.<br><p>Locate osgProducer This module defines<br><p>OSGPRODUCER_FOUND - Was osgProducer found? OSGPRODUCER_INCLUDE_DIR - Where to find the headers OSGPRODUCER_LIBRARIES - The libraries to link for osgProducer (use this)<br><p>OSGPRODUCER_LIBRARY - The osgProducer library OSGPRODUCER_LIBRARY_DEBUG - The osgProducer debug library<br><p>$OSGDIR is an environment variable that would correspond to the ./configure --prefix=$OSGDIR used in building osg.<br><p>Created by Eric Wing.
</li>
<li>
<a name="module:FindosgShadow"><b><code>FindosgShadow</code></b></a>: <br>
<p>This is part of the Findosg* suite used to find OpenSceneGraph components. Each component is separate and you must opt in to each module. You must also opt into OpenGL and OpenThreads (and Producer if needed) as these modules won't do it for you. This is to allow you control over your own system piece by piece in case you need to opt out of certain components or change the Find behavior for a particular module (perhaps because the default FindOpenGL.cmake module doesn't work with your system as an example). If you want to use a more convenient module that includes everything, use the FindOpenSceneGraph.cmake instead of the Findosg*.cmake modules.<br><p>Locate osgShadow This module defines<br><p>OSGSHADOW_FOUND - Was osgShadow found? OSGSHADOW_INCLUDE_DIR - Where to find the headers OSGSHADOW_LIBRARIES - The libraries to link for osgShadow (use this)<br><p>OSGSHADOW_LIBRARY - The osgShadow library OSGSHADOW_LIBRARY_DEBUG - The osgShadow debug library<br><p>$OSGDIR is an environment variable that would correspond to the ./configure --prefix=$OSGDIR used in building osg.<br><p>Created by Eric Wing.
</li>
<li>
<a name="module:FindosgSim"><b><code>FindosgSim</code></b></a>: <br>
<p>This is part of the Findosg* suite used to find OpenSceneGraph components. Each component is separate and you must opt in to each module. You must also opt into OpenGL and OpenThreads (and Producer if needed) as these modules won't do it for you. This is to allow you control over your own system piece by piece in case you need to opt out of certain components or change the Find behavior for a particular module (perhaps because the default FindOpenGL.cmake module doesn't work with your system as an example). If you want to use a more convenient module that includes everything, use the FindOpenSceneGraph.cmake instead of the Findosg*.cmake modules.<br><p>Locate osgSim This module defines<br><p>OSGSIM_FOUND - Was osgSim found? OSGSIM_INCLUDE_DIR - Where to find the headers OSGSIM_LIBRARIES - The libraries to link for osgSim (use this)<br><p>OSGSIM_LIBRARY - The osgSim library OSGSIM_LIBRARY_DEBUG - The osgSim debug library<br><p>$OSGDIR is an environment variable that would correspond to the ./configure --prefix=$OSGDIR used in building osg.<br><p>Created by Eric Wing.
</li>
<li>
<a name="module:FindosgTerrain"><b><code>FindosgTerrain</code></b></a>: <br>
<p>This is part of the Findosg* suite used to find OpenSceneGraph components. Each component is separate and you must opt in to each module. You must also opt into OpenGL and OpenThreads (and Producer if needed) as these modules won't do it for you. This is to allow you control over your own system piece by piece in case you need to opt out of certain components or change the Find behavior for a particular module (perhaps because the default FindOpenGL.cmake module doesn't work with your system as an example). If you want to use a more convenient module that includes everything, use the FindOpenSceneGraph.cmake instead of the Findosg*.cmake modules.<br><p>Locate osgTerrain This module defines<br><p>OSGTERRAIN_FOUND - Was osgTerrain found? OSGTERRAIN_INCLUDE_DIR - Where to find the headers OSGTERRAIN_LIBRARIES - The libraries to link for osgTerrain (use this)<br><p>OSGTERRAIN_LIBRARY - The osgTerrain library OSGTERRAIN_LIBRARY_DEBUG - The osgTerrain debug library<br><p>$OSGDIR is an environment variable that would correspond to the ./configure --prefix=$OSGDIR used in building osg.<br><p>Created by Eric Wing.
</li>
<li>
<a name="module:FindosgText"><b><code>FindosgText</code></b></a>: <br>
<p>This is part of the Findosg* suite used to find OpenSceneGraph components. Each component is separate and you must opt in to each module. You must also opt into OpenGL and OpenThreads (and Producer if needed) as these modules won't do it for you. This is to allow you control over your own system piece by piece in case you need to opt out of certain components or change the Find behavior for a particular module (perhaps because the default FindOpenGL.cmake module doesn't work with your system as an example). If you want to use a more convenient module that includes everything, use the FindOpenSceneGraph.cmake instead of the Findosg*.cmake modules.<br><p>Locate osgText This module defines<br><p>OSGTEXT_FOUND - Was osgText found? OSGTEXT_INCLUDE_DIR - Where to find the headers OSGTEXT_LIBRARIES - The libraries to link for osgText (use this)<br><p>OSGTEXT_LIBRARY - The osgText library OSGTEXT_LIBRARY_DEBUG - The osgText debug library<br><p>$OSGDIR is an environment variable that would correspond to the ./configure --prefix=$OSGDIR used in building osg.<br><p>Created by Eric Wing.
</li>
<li>
<a name="module:FindosgUtil"><b><code>FindosgUtil</code></b></a>: <br>
<p>This is part of the Findosg* suite used to find OpenSceneGraph components. Each component is separate and you must opt in to each module. You must also opt into OpenGL and OpenThreads (and Producer if needed) as these modules won't do it for you. This is to allow you control over your own system piece by piece in case you need to opt out of certain components or change the Find behavior for a particular module (perhaps because the default FindOpenGL.cmake module doesn't work with your system as an example). If you want to use a more convenient module that includes everything, use the FindOpenSceneGraph.cmake instead of the Findosg*.cmake modules.<br><p>Locate osgUtil This module defines<br><p>OSGUTIL_FOUND - Was osgUtil found? OSGUTIL_INCLUDE_DIR - Where to find the headers OSGUTIL_LIBRARIES - The libraries to link for osgUtil (use this)<br><p>OSGUTIL_LIBRARY - The osgUtil library OSGUTIL_LIBRARY_DEBUG - The osgUtil debug library<br><p>$OSGDIR is an environment variable that would correspond to the ./configure --prefix=$OSGDIR used in building osg.<br><p>Created by Eric Wing.
</li>
<li>
<a name="module:FindosgViewer"><b><code>FindosgViewer</code></b></a>: <br>
<p>This is part of the Findosg* suite used to find OpenSceneGraph components. Each component is separate and you must opt in to each module. You must also opt into OpenGL and OpenThreads (and Producer if needed) as these modules won't do it for you. This is to allow you control over your own system piece by piece in case you need to opt out of certain components or change the Find behavior for a particular module (perhaps because the default FindOpenGL.cmake module doesn't work with your system as an example). If you want to use a more convenient module that includes everything, use the FindOpenSceneGraph.cmake instead of the Findosg*.cmake modules.<br><p>Locate osgViewer This module defines<br><p>OSGVIEWER_FOUND - Was osgViewer found? OSGVIEWER_INCLUDE_DIR - Where to find the headers OSGVIEWER_LIBRARIES - The libraries to link for osgViewer (use this)<br><p>OSGVIEWER_LIBRARY - The osgViewer library OSGVIEWER_LIBRARY_DEBUG - The osgViewer debug library<br><p>$OSGDIR is an environment variable that would correspond to the ./configure --prefix=$OSGDIR used in building osg.<br><p>Created by Eric Wing.
</li>
<li>
<a name="module:FindosgVolume"><b><code>FindosgVolume</code></b></a>: <br>
<p>This is part of the Findosg* suite used to find OpenSceneGraph components. Each component is separate and you must opt in to each module. You must also opt into OpenGL and OpenThreads (and Producer if needed) as these modules won't do it for you. This is to allow you control over your own system piece by piece in case you need to opt out of certain components or change the Find behavior for a particular module (perhaps because the default FindOpenGL.cmake module doesn't work with your system as an example). If you want to use a more convenient module that includes everything, use the FindOpenSceneGraph.cmake instead of the Findosg*.cmake modules.<br><p>Locate osgVolume This module defines<br><p>OSGVOLUME_FOUND - Was osgVolume found? OSGVOLUME_INCLUDE_DIR - Where to find the headers OSGVOLUME_LIBRARIES - The libraries to link for osgVolume (use this)<br><p>OSGVOLUME_LIBRARY - The osgVolume library OSGVOLUME_LIBRARY_DEBUG - The osgVolume debug library<br><p>$OSGDIR is an environment variable that would correspond to the ./configure --prefix=$OSGDIR used in building osg.<br><p>Created by Eric Wing.
</li>
<li>
<a name="module:FindosgWidget"><b><code>FindosgWidget</code></b></a>: <br>
<p>This is part of the Findosg* suite used to find OpenSceneGraph components. Each component is separate and you must opt in to each module. You must also opt into OpenGL and OpenThreads (and Producer if needed) as these modules won't do it for you. This is to allow you control over your own system piece by piece in case you need to opt out of certain components or change the Find behavior for a particular module (perhaps because the default FindOpenGL.cmake module doesn't work with your system as an example). If you want to use a more convenient module that includes everything, use the FindOpenSceneGraph.cmake instead of the Findosg*.cmake modules.<br><p>Locate osgWidget This module defines<br><p>OSGWIDGET_FOUND - Was osgWidget found? OSGWIDGET_INCLUDE_DIR - Where to find the headers OSGWIDGET_LIBRARIES - The libraries to link for osgWidget (use this)<br><p>OSGWIDGET_LIBRARY - The osgWidget library OSGWIDGET_LIBRARY_DEBUG - The osgWidget debug library<br><p>$OSGDIR is an environment variable that would correspond to the ./configure --prefix=$OSGDIR used in building osg.<br><p>FindosgWidget.cmake tweaked from Findosg* suite as created by Eric Wing.
</li>
<li>
<a name="module:Findosg_functions"><b><code>Findosg_functions</code></b></a>: <br>
<p><br><p>This CMake file contains two macros to assist with searching for OSG libraries and nodekits.<br>
</li>
<li>
<a name="module:FindwxWidgets"><b><code>FindwxWidgets</code></b></a>: Find a wxWidgets (a.k.a., wxWindows) installation.<br>
<p>This module finds if wxWidgets is installed and selects a default configuration to use. wxWidgets is a modular library. To specify the modules that you will use, you need to name them as components to the package:<br><p>FIND_PACKAGE(wxWidgets COMPONENTS base core ...)<br><p>There are two search branches: a windows style and a unix style. For windows, the following variables are searched for and set to defaults in case of multiple choices. Change them if the defaults are not desired (i.e., these are the only variables you should change to select a configuration):<br><pre> wxWidgets_ROOT_DIR - Base wxWidgets directory<br> (e.g., C:/wxWidgets-2.6.3).<br> wxWidgets_LIB_DIR - Path to wxWidgets libraries<br> (e.g., C:/wxWidgets-2.6.3/lib/vc_lib).<br> wxWidgets_CONFIGURATION - Configuration to use<br> (e.g., msw, mswd, mswu, mswunivud, etc.)<br></pre>
<p><br><p>For unix style it uses the wx-config utility. You can select between debug/release, unicode/ansi, universal/non-universal, and static/shared in the QtDialog or ccmake interfaces by turning ON/OFF the following variables:<br><pre> wxWidgets_USE_DEBUG<br> wxWidgets_USE_UNICODE<br> wxWidgets_USE_UNIVERSAL<br> wxWidgets_USE_STATIC<br> <br></pre>
<p>The following are set after the configuration is done for both windows and unix style:<br><pre> wxWidgets_FOUND - Set to TRUE if wxWidgets was found.<br> wxWidgets_INCLUDE_DIRS - Include directories for WIN32<br> i.e., where to find "wx/wx.h" and<br> "wx/setup.h"; possibly empty for unices.<br> wxWidgets_LIBRARIES - Path to the wxWidgets libraries.<br> wxWidgets_LIBRARY_DIRS - compile time link dirs, useful for<br> rpath on UNIX. Typically an empty string<br> in WIN32 environment.<br> wxWidgets_DEFINITIONS - Contains defines required to compile/link<br> against WX, e.g. WXUSINGDLL<br> wxWidgets_DEFINITIONS_DEBUG- Contains defines required to compile/link<br> against WX debug builds, e.g. __WXDEBUG__<br> wxWidgets_CXX_FLAGS - Include dirs and compiler flags for<br> unices, empty on WIN32. Essentially<br> "`wx-config --cxxflags`".<br> wxWidgets_USE_FILE - Convenience include file.<br></pre>
<p><br><p>Sample usage:<br><pre> FIND_PACKAGE(wxWidgets COMPONENTS base core gl net)<br> IF(wxWidgets_FOUND)<br> INCLUDE(${wxWidgets_USE_FILE})<br> # and for each of your dependant executable/library targets:<br> TARGET_LINK_LIBRARIES(&lt;YourTarget&gt; ${wxWidgets_LIBRARIES})<br> ENDIF(wxWidgets_FOUND)<br></pre>
<p><br><p>If wxWidgets is required (i.e., not an optional part):<br><pre> FIND_PACKAGE(wxWidgets REQUIRED base core gl net)<br> INCLUDE(${wxWidgets_USE_FILE})<br> # and for each of your dependant executable/library targets:<br> TARGET_LINK_LIBRARIES(&lt;YourTarget&gt; ${wxWidgets_LIBRARIES})<br></pre>
</li>
<li>
<a name="module:FindwxWindows"><b><code>FindwxWindows</code></b></a>: Find wxWindows (wxWidgets) installation<br>
<p>This module finds if wxWindows/wxWidgets is installed and determines where the include files and libraries are. It also determines what the name of the library is. Please note this file is DEPRECATED and replaced by FindwxWidgets.cmake. This code sets the following variables:<br><pre> WXWINDOWS_FOUND = system has WxWindows<br> WXWINDOWS_LIBRARIES = path to the wxWindows libraries<br> on Unix/Linux with additional<br> linker flags from<br> "wx-config --libs"<br> CMAKE_WXWINDOWS_CXX_FLAGS = Compiler flags for wxWindows,<br> essentially "`wx-config --cxxflags`"<br> on Linux<br> WXWINDOWS_INCLUDE_DIR = where to find "wx/wx.h" and "wx/setup.h"<br> WXWINDOWS_LINK_DIRECTORIES = link directories, useful for rpath on<br> Unix<br> WXWINDOWS_DEFINITIONS = extra defines<br></pre>
<p><br><p>OPTIONS If you need OpenGL support please<br><pre> SET(WXWINDOWS_USE_GL 1)<br></pre>
<p>in your CMakeLists.txt *before* you include this file.<br><pre> HAVE_ISYSTEM - true required to replace -I by -isystem on g++<br></pre>
<p><br><p>For convenience include Use_wxWindows.cmake in your project's CMakeLists.txt using INCLUDE(Use_wxWindows).<br><p>USAGE<br><pre> SET(WXWINDOWS_USE_GL 1)<br> FIND_PACKAGE(wxWindows)<br></pre>
<p><br><p>NOTES wxWidgets 2.6.x is supported for monolithic builds e.g. compiled in wx/build/msw dir as:<br><pre> nmake -f makefile.vc BUILD=debug SHARED=0 USE_OPENGL=1 MONOLITHIC=1<br></pre>
<p><br><p>DEPRECATED<br><pre> CMAKE_WX_CAN_COMPILE<br> WXWINDOWS_LIBRARY<br> CMAKE_WX_CXX_FLAGS<br> WXWINDOWS_INCLUDE_PATH<br></pre>
<p><br><p>AUTHOR Jan Woetzel &lt;<a href="http://www.mip.informatik.uni-kiel.de/~jw">http://www.mip.informatik.uni-kiel.de/~jw</a>&gt; (07/2003-01/2006)
</li>
<li>
<a name="module:FortranCInterface"><b><code>FortranCInterface</code></b></a>: Fortran/C Interface Detection<br>
<p>This module automatically detects the API by which C and Fortran languages interact. Variables indicate if the mangling is found:<br><pre> FortranCInterface_GLOBAL_FOUND = Global subroutines and functions<br> FortranCInterface_MODULE_FOUND = Module subroutines and functions<br> (declared by "MODULE PROCEDURE")<br></pre>
<p>A function is provided to generate a C header file containing macros to mangle symbol names:<br><pre> FortranCInterface_HEADER(&lt;file&gt;<br> [MACRO_NAMESPACE &lt;macro-ns&gt;]<br> [SYMBOL_NAMESPACE &lt;ns&gt;]<br> [SYMBOLS [&lt;module&gt;:]&lt;function&gt; ...])<br></pre>
<p>It generates in &lt;file&gt; definitions of the following macros:<br><pre> #define FortranCInterface_GLOBAL (name,NAME) ...<br> #define FortranCInterface_GLOBAL_(name,NAME) ...<br> #define FortranCInterface_MODULE (mod,name, MOD,NAME) ...<br> #define FortranCInterface_MODULE_(mod,name, MOD,NAME) ...<br></pre>
<p>These macros mangle four categories of Fortran symbols, respectively:<br><pre> - Global symbols without '_': call mysub()<br> - Global symbols with '_' : call my_sub()<br> - Module symbols without '_': use mymod; call mysub()<br> - Module symbols with '_' : use mymod; call my_sub()<br></pre>
<p>If mangling for a category is not known, its macro is left undefined. All macros require raw names in both lower case and upper case. The MACRO_NAMESPACE option replaces the default "FortranCInterface_" prefix with a given namespace "&lt;macro-ns&gt;".<br><p>The SYMBOLS option lists symbols to mangle automatically with C preprocessor definitions:<br><pre> &lt;function&gt; ==&gt; #define &lt;ns&gt;&lt;function&gt; ...<br> &lt;module&gt;:&lt;function&gt; ==&gt; #define &lt;ns&gt;&lt;module&gt;_&lt;function&gt; ...<br></pre>
<p>If the mangling for some symbol is not known then no preprocessor definition is created, and a warning is displayed. The SYMBOL_NAMESPACE option prefixes all preprocessor definitions generated by the SYMBOLS option with a given namespace "&lt;ns&gt;".<br><p>Example usage:<br><pre> include(FortranCInterface)<br> FortranCInterface_HEADER(FC.h MACRO_NAMESPACE "FC_")<br></pre>
<p>This creates a "FC.h" header that defines mangling macros FC_GLOBAL(), FC_GLOBAL_(), FC_MODULE(), and FC_MODULE_().<br><p>Example usage:<br><pre> include(FortranCInterface)<br> FortranCInterface_HEADER(FCMangle.h<br> MACRO_NAMESPACE "FC_"<br> SYMBOL_NAMESPACE "FC_"<br> SYMBOLS mysub mymod:my_sub)<br></pre>
<p>This creates a "FC.h" header that defines the same FC_*() mangling macros as the previous example plus preprocessor symbols FC_mysub and FC_mymod_my_sub.<br><p>Another function is provided to verify that the Fortran and C/C++ compilers work together:<br><pre> FortranCInterface_VERIFY([CXX] [QUIET])<br></pre>
<p>It tests whether a simple test executable using Fortran and C (and C++ when the CXX option is given) compiles and links successfully. The result is stored in the cache entry FortranCInterface_VERIFIED_C (or FortranCInterface_VERIFIED_CXX if CXX is given) as a boolean. If the check fails and QUIET is not given the function terminates with a FATAL_ERROR message describing the problem. The purpose of this check is to stop a build early for incompatible compiler combinations.<br><p>FortranCInterface is aware of possible GLOBAL and MODULE manglings for many Fortran compilers, but it also provides an interface to specify new possible manglings. Set the variables<br><pre> FortranCInterface_GLOBAL_SYMBOLS<br> FortranCInterface_MODULE_SYMBOLS<br></pre>
<p>before including FortranCInterface to specify manglings of the symbols "MySub", "My_Sub", "MyModule:MySub", and "My_Module:My_Sub". For example, the code:<br><pre> set(FortranCInterface_GLOBAL_SYMBOLS mysub_ my_sub__ MYSUB_)<br> # ^^^^^ ^^^^^^ ^^^^^<br> set(FortranCInterface_MODULE_SYMBOLS<br> __mymodule_MOD_mysub __my_module_MOD_my_sub)<br> # ^^^^^^^^ ^^^^^ ^^^^^^^^^ ^^^^^^<br> include(FortranCInterface)<br></pre>
<p>tells FortranCInterface to try given GLOBAL and MODULE manglings. (The carets point at raw symbol names for clarity in this example but are not needed.)
</li>
<li>
<a name="module:GetPrerequisites"><b><code>GetPrerequisites</code></b></a>: <br>
<p>GetPrerequisites.cmake<br><p>This script provides functions to list the .dll, .dylib or .so files that an executable or shared library file depends on. (Its prerequisites.)<br><p>It uses various tools to obtain the list of required shared library files:<br><pre> dumpbin (Windows)<br> ldd (Linux/Unix)<br> otool (Mac OSX)<br></pre>
<p><br><p>The following functions are provided by this script:<br><pre> gp_append_unique<br> is_file_executable<br> gp_item_default_embedded_path<br> (projects can override with gp_item_default_embedded_path_override)<br> gp_resolve_item<br> (projects can override with gp_resolve_item_override)<br> gp_resolved_file_type<br> gp_file_type<br> get_prerequisites<br> list_prerequisites<br> list_prerequisites_by_glob<br></pre>
<p><br><p>Requires CMake 2.6 or greater because it uses function, break, return and PARENT_SCOPE.
</li>
<li>
<a name="module:InstallRequiredSystemLibraries"><b><code>InstallRequiredSystemLibraries</code></b></a>: <br>
<p>By including this file, all files in the CMAKE_INSTALL_DEBUG_LIBRARIES, will be installed with INSTALL_PROGRAMS into /bin for WIN32 and /lib for non-win32. If CMAKE_SKIP_INSTALL_RULES is set to TRUE before including this file, then the INSTALL command is not called. The use can use the variable CMAKE_INSTALL_SYSTEM_RUNTIME_LIBS to use a custom install command and install them into any directory they want. If it is the MSVC compiler, then the microsoft run time libraries will be found add automatically added to the CMAKE_INSTALL_DEBUG_LIBRARIES, and installed. If CMAKE_INSTALL_DEBUG_LIBRARIES is set and it is the MSVC compiler, then the debug libraries are installed when available. If CMAKE_INSTALL_MFC_LIBRARIES is set then the MFC run time libraries are installed as well as the CRT run time libraries.
</li>
<li>
<a name="module:MacroAddFileDependencies"><b><code>MacroAddFileDependencies</code></b></a>: MACRO_ADD_FILE_DEPENDENCIES(&lt;_file&gt; depend_files...)<br>
<p>Using the macro MACRO_ADD_FILE_DEPENDENCIES() is discouraged. There are usually better ways to specifiy the correct dependencies.<br><p>MACRO_ADD_FILE_DEPENDENCIES(&lt;_file&gt; depend_files...) is just a convenience wrapper around the OBJECT_DEPENDS source file property. You can just use SET_PROPERTY(SOURCE &lt;file&gt; APPEND PROPERTY OBJECT_DEPENDS depend_files) instead.
</li>
<li>
<a name="module:SelectLibraryConfigurations"><b><code>SelectLibraryConfigurations</code></b></a>: <br>
<p>select_library_configurations( basename )<br><p>This macro takes a library base name as an argument, and will choose good values for basename_LIBRARY, basename_LIBRARIES, basename_LIBRARY_DEBUG, and basename_LIBRARY_RELEASE depending on what has been found and set. If only basename_LIBRARY_RELEASE is defined, basename_LIBRARY, basename_LIBRARY_DEBUG, and basename_LIBRARY_RELEASE will be set to the release value. If only basename_LIBRARY_DEBUG is defined, then basename_LIBRARY, basename_LIBRARY_DEBUG and basename_LIBRARY_RELEASE will take the debug value. <br><p>If the generator supports configuration types, then basename_LIBRARY and basename_LIBRARIES will be set with debug and optimized flags specifying the library to be used for the given configuration. If no build type has been set or the generator in use does not support configuration types, then basename_LIBRARY and basename_LIBRARIES will take only the release values.
</li>
<li>
<a name="module:SquishTestScript"><b><code>SquishTestScript</code></b></a>: <br>
<p><br><p>This script launches a GUI test using Squish. You should not call the script directly; instead, you should access it via the SQUISH_ADD_TEST macro that is defined in FindSquish.cmake.<br><p>This script starts the Squish server, launches the test on the client, and finally stops the squish server. If any of these steps fail (including if the tests do not pass) then a fatal error is raised.<br>
</li>
<li>
<a name="module:TestBigEndian"><b><code>TestBigEndian</code></b></a>: Define macro to determine endian type<br>
<p>Check if the system is big endian or little endian<br><pre> TEST_BIG_ENDIAN(VARIABLE)<br> VARIABLE - variable to store the result to<br></pre>
<p><br>
</li>
<li>
<a name="module:TestCXXAcceptsFlag"><b><code>TestCXXAcceptsFlag</code></b></a>: Test CXX compiler for a flag<br>
<p>Check if the CXX compiler accepts a flag<br><pre> Macro CHECK_CXX_ACCEPTS_FLAG(FLAGS VARIABLE) -<br> checks if the function exists<br> FLAGS - the flags to try<br> VARIABLE - variable to store the result<br></pre>
<p><br>
</li>
<li>
<a name="module:TestForANSIForScope"><b><code>TestForANSIForScope</code></b></a>: Check for ANSI for scope support<br>
<p>Check if the compiler restricts the scope of variables declared in a for-init-statement to the loop body.<br><pre> CMAKE_NO_ANSI_FOR_SCOPE - holds result<br></pre>
<p><br>
</li>
<li>
<a name="module:TestForANSIStreamHeaders"><b><code>TestForANSIStreamHeaders</code></b></a>: Test for compiler support of ANSI stream headers iostream, etc.<br>
<p>check if the compiler supports the standard ANSI iostream header (without the .h)<br><pre> CMAKE_NO_ANSI_STREAM_HEADERS - defined by the results<br></pre>
<p><br>
</li>
<li>
<a name="module:TestForSSTREAM"><b><code>TestForSSTREAM</code></b></a>: Test for compiler support of ANSI sstream header<br>
<p>check if the compiler supports the standard ANSI sstream header<br><pre> CMAKE_NO_ANSI_STRING_STREAM - defined by the results<br></pre>
<p><br>
</li>
<li>
<a name="module:TestForSTDNamespace"><b><code>TestForSTDNamespace</code></b></a>: Test for std:: namespace support<br>
<p>check if the compiler supports std:: on stl classes<br><pre> CMAKE_NO_STD_NAMESPACE - defined by the results<br></pre>
<p><br>
</li>
<li>
<a name="module:UseEcos"><b><code>UseEcos</code></b></a>: This module defines variables and macros required to build eCos application.<br>
<p>This file contains the following macros: ECOS_ADD_INCLUDE_DIRECTORIES() - add the eCos include dirs ECOS_ADD_EXECUTABLE(name source1 ... sourceN ) - create an eCos executable ECOS_ADJUST_DIRECTORY(VAR source1 ... sourceN ) - adjusts the path of the source files and puts the result into VAR<br><p>Macros for selecting the toolchain: ECOS_USE_ARM_ELF_TOOLS() - enable the ARM ELF toolchain for the directory where it is called ECOS_USE_I386_ELF_TOOLS() - enable the i386 ELF toolchain for the directory where it is called ECOS_USE_PPC_EABI_TOOLS() - enable the PowerPC toolchain for the directory where it is called<br><p>It contains the following variables: ECOS_DEFINITIONS ECOSCONFIG_EXECUTABLE ECOS_CONFIG_FILE - defaults to ecos.ecc, if your eCos configuration file has a different name, adjust this variable for internal use only:<br><pre> ECOS_ADD_TARGET_LIB<br></pre>
</li>
<li>
<a name="module:UsePkgConfig"><b><code>UsePkgConfig</code></b></a>: obsolete pkg-config module for CMake<br>
<p><br><p>Defines the following macros:<br><p>PKGCONFIG(package includedir libdir linkflags cflags)<br><p>Calling PKGCONFIG will fill the desired information into the 4 given arguments, e.g. PKGCONFIG(libart-2.0 LIBART_INCLUDE_DIR LIBART_LINK_DIR LIBART_LINK_FLAGS LIBART_CFLAGS) if pkg-config was NOT found or the specified software package doesn't exist, the variable will be empty when the function returns, otherwise they will contain the respective information<br>
</li>
<li>
<a name="module:UseQt4"><b><code>UseQt4</code></b></a>: Use Module for QT4<br>
<p>Sets up C and C++ to use Qt 4. It is assumed that FindQt.cmake has already been loaded. See FindQt.cmake for information on how to load Qt 4 into your CMake project.
</li>
<li>
<a name="module:UseSWIG"><b><code>UseSWIG</code></b></a>: SWIG module for CMake<br>
<p>Defines the following macros:<br><pre> SWIG_ADD_MODULE(name language [ files ])<br> - Define swig module with given name and specified language<br> SWIG_LINK_LIBRARIES(name [ libraries ])<br> - Link libraries to swig module<br></pre>
<p>All other macros are for internal use only. To get the actual name of the swig module, use: ${SWIG_MODULE_${name}_REAL_NAME}. Set Source files properties such as CPLUSPLUS and SWIG_FLAGS to specify special behavior of SWIG. Also global CMAKE_SWIG_FLAGS can be used to add special flags to all swig calls. Another special variable is CMAKE_SWIG_OUTDIR, it allows one to specify where to write all the swig generated module (swig -outdir option) The name-specific variable SWIG_MODULE_&lt;name&gt;_EXTRA_DEPS may be used to specify extra dependencies for the generated modules. If the source file generated by swig need some special flag you can use SET_SOURCE_FILES_PROPERTIES( ${swig_generated_file_fullname}<br><pre> PROPERTIES COMPILE_FLAGS "-bla")<br></pre>
</li>
<li>
<a name="module:Use_wxWindows"><b><code>Use_wxWindows</code></b></a>: ---------------------------------------------------<br>
<p><br><p>This convenience include finds if wxWindows is installed and set the appropriate libs, incdirs, flags etc. author Jan Woetzel &lt;jw -at- mip.informatik.uni-kiel.de&gt; (07/2003)<br><p>USAGE:<br><pre> just include Use_wxWindows.cmake<br> in your projects CMakeLists.txt<br></pre>
<p>INCLUDE( ${CMAKE_MODULE_PATH}/Use_wxWindows.cmake)<br><pre> if you are sure you need GL then<br></pre>
<p>SET(WXWINDOWS_USE_GL 1)<br><pre> *before* you include this file.<br></pre>
</li>
<li>
<a name="module:UsewxWidgets"><b><code>UsewxWidgets</code></b></a>: Convenience include for using wxWidgets library<br>
<p>Finds if wxWidgets is installed and set the appropriate libs, incdirs, flags etc. INCLUDE_DIRECTORIES, LINK_DIRECTORIES and ADD_DEFINITIONS are called.<br><p>USAGE<br><pre> SET( wxWidgets_USE_LIBS gl xml xrc ) # optionally: more than wx std libs<br> FIND_PACKAGE(wxWidgets REQUIRED)<br> INCLUDE( ${xWidgets_USE_FILE} )<br> ... add your targets here, e.g. ADD_EXECUTABLE/ ADD_LIBRARY ...<br> TARGET_LINK_LIBRARIERS( &lt;yourWxDependantTarget&gt; ${wxWidgets_LIBRARIES})<br></pre>
<p><br><p>DEPRECATED<br><pre> LINK_LIBRARIES is not called in favor of adding dependencies per target.<br></pre>
<p><br><p>AUTHOR<br><pre> Jan Woetzel &lt;jw -at- mip.informatik.uni-kiel.de&gt;<br></pre>
</li>
</ul>
<h2><a name="section_Copyright"/>Copyright</h2>
<ul>
</ul>
<p>Copyright 2000-2009 Kitware, Inc., Insight Software Consortium. All rights reserved.
<p>Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
<p>Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
<p>Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
<p>Neither the names of Kitware, Inc., the Insight Software Consortium, nor the names of their contributors may be used to endorse or promote products derived from this software without specific prior written permission.
<p>THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
<h2><a name="section_See Also"/>See Also</h2>
<ul>
<li><a href="#see:HomePage"><b><code>Home Page</code></b></a></li> <li><a href="#see:FrequentlyAskedQuestions"><b><code>Frequently Asked Questions</code></b></a></li> <li><a href="#see:OnlineDocumentation"><b><code>Online Documentation</code></b></a></li> <li><a href="#see:MailingList"><b><code>Mailing List</code></b></a></li></ul>
<p>.B ccmake(1), cpack(1), ctest(1), cmakecommands(1), cmakecompat(1), cmakemodules(1), cmakeprops(1), cmakevars(1)
<p>The following resources are available to get help using CMake:
<ul>
<li>
<a name="see:HomePage"><b><code>Home Page</code></b></a>: <a href="http://www.cmake.org">http://www.cmake.org</a><br>
<p>The primary starting point for learning about CMake.
</li>
<li>
<a name="see:FrequentlyAskedQuestions"><b><code>Frequently Asked Questions</code></b></a>: <a href="http://www.cmake.org/Wiki/CMake_FAQ">http://www.cmake.org/Wiki/CMake_FAQ</a><br>
<p>A Wiki is provided containing answers to frequently asked questions.
</li>
<li>
<a name="see:OnlineDocumentation"><b><code>Online Documentation</code></b></a>: <a href="http://www.cmake.org/HTML/Documentation.html">http://www.cmake.org/HTML/Documentation.html</a><br>
<p>Links to available documentation may be found on this web page.
</li>
<li>
<a name="see:MailingList"><b><code>Mailing List</code></b></a>: <a href="http://www.cmake.org/HTML/MailingLists.html">http://www.cmake.org/HTML/MailingLists.html</a><br>
<p>For help and discussion about using cmake, a mailing list is provided at cmake@cmake.org. The list is member-post-only but one may sign up on the CMake web page. Please first read the full documentation at <a href="http://www.cmake.org">http://www.cmake.org</a> before posting questions to the list.
</li>
</ul>
<p>Summary of helpful links:<br><pre> Home: <a href="http://www.cmake.org">http://www.cmake.org</a><br> Docs: <a href="http://www.cmake.org/HTML/Documentation.html">http://www.cmake.org/HTML/Documentation.html</a><br> Mail: <a href="http://www.cmake.org/HTML/MailingLists.html">http://www.cmake.org/HTML/MailingLists.html</a><br> FAQ: <a href="http://www.cmake.org/Wiki/CMake_FAQ">http://www.cmake.org/Wiki/CMake_FAQ</a><br></pre>
</body></html>
Reference in New Issue View Git Blame Copy Permalink