For more information about how to contribute modules to CMake, see this page:
http://www.itk.org/Wiki/CMake:Module_Maintainers
Note to authors of FindXXX.cmake files
We would like all FindXXX.cmake files to produce consistent variable names.
Please use the following consistent variable names for general use.
XXX_INCLUDE_DIRS The final set of include directories listed in one variable for use by client code. This should not be a cache entry.
XXX_LIBRARIES The libraries to link against to use XXX. These should include full paths. This should not be a cache entry.
XXX_DEFINITIONS Definitions to use when compiling code that uses XXX. This really shouldn't include options such as (-DHAS_JPEG)that a client source-code file uses to decide whether to #include <jpeg.h>
XXX_EXECUTABLE Where to find the XXX tool.
XXX_YYY_EXECUTABLE Where to find the YYY tool that comes with XXX.
XXX_LIBRARY_DIRS Optionally, the final set of library directories listed in one variable for use by client code. This should not be a cache entry.
XXX_ROOT_DIR Where to find the base directory of XXX.
XXX_VERSION_YY Expect Version YY if true. Make sure at most one of these is ever true.
XXX_WRAP_YY If False, do not try to use the relevent CMake wrapping command.
XXX_YY_FOUND If False, optional YY part of XXX sytem is not available.
XXX_FOUND Set to false, or undefined, if we haven't found, or don't want to use XXX.
XXX_RUNTIME_LIBRARY_DIRS Optionally, the runtime library search path for use when running an executable linked to shared libraries.
The list should be used by user code to create the PATH on windows or LD_LIBRARY_PATH on unix.
This should not be a cache entry.
XXX_VERSION_STRING A human-readable string containing the version of the package found, if any.
XXX_VERSION_MAJOR The major version of the package found, if any.
XXX_VERSION_MINOR The minor version of the package found, if any.
XXX_VERSION_PATCH The patch version of the package found, if any.
You do not have to provide all of the above variables. You should provide XXX_FOUND under most circumstances. If XXX is a library, then XXX_LIBRARIES, should also be defined, and XXX_INCLUDE_DIRS should usually be defined (I guess libm.a might be an exception)
The following names should not usually be used in CMakeLists.txt files, but they may be usefully modified in users' CMake Caches to control stuff.
XXX_LIBRARY Name of XXX Library. A User may set this and XXX_INCLUDE_DIR to ignore to force non-use of XXX.
XXX_YY_LIBRARY Name of YY library that is part of the XXX system. It may or may not be required to use XXX.
XXX_INCLUDE_DIR Where to find xxx.h, etc. (XXX_INCLUDE_PATH was considered bad because a path includes an actual filename.)
XXX_YY_INCLUDE_DIR Where to find xxx_yy.h, etc.
For tidiness's sake, try to keep as many options as possible out of the cache, leaving at least one option which can be used to disable use of the module, or locate a not-found library (e.g. XXX_ROOT_DIR). For the same reason, mark most cache options as advanced.
If you need other commands to do special things then it should still begin with XXX_. This gives a sort of namespace effect and keeps things tidy for the user. You should put comments describing all the exported settings, plus descriptions of any the users can use to control stuff.
You really should also provide backwards compatibility any old settings that were actually in use. Make sure you comment them as deprecated, so that no-one starts using them.
To correctly document a module, create a comment block at the top with # comments. There are three types of comments that can be in the block:
1. The brief description of the module, this is done by:
# - a small description
2. A paragraph of text. This is done with all text that has a single
space between the # and the text. To create a new paragraph, just
put a # with no text on the line.
3. A verbatim line. This is done with two spaces between the # and the text.
For example:
# - This is a cool module
# This module does really cool stuff.
# It can do even more than you think.
#
# It even needs to paragraphs to tell you about it.
# And it defines the following variables:
# VAR_COOL - this is great isn't it?
# VAR_REALLY_COOL - cool right?
#
To have a .cmake file in this directory NOT show up in the
modules documentation, you should start the file with a blank
line.
A FindXXX.cmake module will typically be loaded by the command
FIND_PACKAGE(XXX [major[.minor[.patch[.tweak]]]] [EXACT]
[QUIET] [[REQUIRED|COMPONENTS] [components...]])
If any version numbers are given to the command it will set the
following variables before loading the module:
XXX_FIND_VERSION = full requested version string
XXX_FIND_VERSION_MAJOR = major version if requested, else 0
XXX_FIND_VERSION_MINOR = minor version if requested, else 0
XXX_FIND_VERSION_PATCH = patch version if requested, else 0
XXX_FIND_VERSION_TWEAK = tweak version if requested, else 0
XXX_FIND_VERSION_COUNT = number of version components, 0 to 4
XXX_FIND_VERSION_EXACT = true if EXACT option was given
If the find module supports versioning it should locate a version of
the package that is compatible with the version requested. If a
compatible version of the package cannot be found the module should
not report success. The version of the package found should be stored
in "XXX_VERSION..." version variables documented by the module.
If the QUIET option is given to the command it will set the variable
XXX_FIND_QUIETLY to true before loading the FindXXX.cmake module. If
this variable is set the module should not complain about not being
able to find the package. If the
REQUIRED option is given to the command it will set the variable
XXX_FIND_REQUIRED to true before loading the FindXXX.cmake module. If
this variable is set the module should issue a FATAL_ERROR if the
package cannot be found. For each package-specific component, say
YYY, listed after the REQUIRED option a variable XXX_FIND_REQUIRED_YYY
to true. The set of components listed after either the REQUIRED
option or the COMPONENTS option will be specified in a
XXX_FIND_COMPONENTS variable. This can be used by the FindXXX.cmake
module to determine which sub-components of the package must be found.
If neither the QUIET nor REQUIRED options are given then the
FindXXX.cmake module should look for the package and complain without
error if the module is not found.
To get this behaviour you can use the FIND_PACKAGE_HANDLE_STANDARD_ARGS()
macro, as an example see FindJPEG.cmake.
For internal implementation, it's a generally accepted convention that variables starting with
underscore are for temporary use only. (variable starting with an underscore
are not intended as a reserved prefix).
没有合适的资源?快使用搜索试试~ 我知道了~
支持WinCE的CMake:cmake-2.8.3-win32-x86-ce.zip
共574个文件
cmake:426个
in:48个
txt:22个
4星 · 超过85%的资源 需积分: 9 26 下载量 121 浏览量
2011-08-15
09:28:39
上传
评论
收藏 9.88MB ZIP 举报
温馨提示
支持WinCE交叉编译的CMake:cmake-2.8.3-win32-x86-ce.zip 使用方法: md build cd build cmake .. -G "Visual Studio 8 2005" -DCMAKE_WINCE_SDK="Windows Mobile 6 Professional SDK (ARMV4I)" -DPORT=WinCE
资源推荐
资源详情
资源评论
收起资源包目录
支持WinCE的CMake:cmake-2.8.3-win32-x86-ce.zip (574个子文件)
cmake.1 536KB
cmake-gui.1 506KB
cmakemodules.1 243KB
cmakecommands.1 145KB
ctest.1 107KB
cmakeprops.1 67KB
cmakevars.1 44KB
cmakepolicies.1 22KB
cmakecompat.1 13KB
cpack.1 5KB
SquishRunTestCase.bat 219B
CheckForPthreads.c 765B
CMakeCCompilerABI.c 600B
CheckFunctionExists.c 403B
CheckVariableExists.c 383B
my_module_.c 323B
mymodule_.c 317B
main.c 261B
CMakeTestGNU.c 184B
VerifyC.c 70B
CMakeTestNMakeCLVersion.c 20B
FindCUDA.cmake 54KB
FindBoost.cmake 52KB
FindQt4.cmake 52KB
ExternalProject.cmake 49KB
CPack.cmake 43KB
FindwxWidgets.cmake 39KB
GetPrerequisites.cmake 30KB
BundleUtilities.cmake 29KB
CPackRPM.cmake 28KB
FindwxWindows.cmake 26KB
FindGTK2.cmake 21KB
FindX11.cmake 20KB
FindPkgConfig.cmake 15KB
Qt4Macros.cmake 15KB
FindMPI.cmake 15KB
KDE3Macros.cmake 15KB
FindSDL_sound.cmake 14KB
UseVTKConfig40.cmake 14KB
CMakeDetermineCompilerId.cmake 14KB
FindHDF5.cmake 14KB
FindBLAS.cmake 14KB
CPackDeb.cmake 14KB
Windows-cl.cmake 13KB
FindQt3.cmake 12KB
InstallRequiredSystemLibraries.cmake 12KB
FindFLTK.cmake 12KB
FortranCInterface.cmake 12KB
FindKDE3.cmake 11KB
FindPackageHandleStandardArgs.cmake 11KB
CTest.cmake 11KB
UseSWIG.cmake 11KB
UseEcos.cmake 11KB
CMakeCXXInformation.cmake 11KB
Darwin.cmake 11KB
run_nvcc.cmake 11KB
FindRuby.cmake 11KB
CMakeDetermineFortranCompiler.cmake 10KB
FindJNI.cmake 10KB
FindFLTK2.cmake 10KB
FindLAPACK.cmake 10KB
CMakeFortranInformation.cmake 9KB
FeatureSummary.cmake 9KB
FindOpenSceneGraph.cmake 9KB
Qt4ConfigDependentSettings.cmake 9KB
CMakeDetermineCXXCompiler.cmake 8KB
FindImageMagick.cmake 8KB
FindPerlLibs.cmake 8KB
FindTCL.cmake 8KB
CMakeCInformation.cmake 8KB
FindPostgreSQL.cmake 8KB
CMakeDetermineSystem.cmake 8KB
FindPythonLibs.cmake 8KB
CMakeDetermineCCompiler.cmake 8KB
FindCxxTest.cmake 8KB
FindJava.cmake 8KB
CheckTypeSize.cmake 7KB
FindCurses.cmake 7KB
FindBISON.cmake 7KB
Detect.cmake 7KB
FindSDL.cmake 6KB
FindQt.cmake 6KB
CMakeGenericSystem.cmake 6KB
FindVTK.cmake 6KB
FindSubversion.cmake 6KB
FindFLEX.cmake 6KB
Darwin-icc.cmake 6KB
CMakeParseArguments.cmake 6KB
FindThreads.cmake 6KB
HP-UX.cmake 6KB
FindXMLRPC.cmake 6KB
FindGTest.cmake 6KB
Windows-GNU.cmake 5KB
CMakeDetermineASMCompiler.cmake 5KB
BlueGeneP-base.cmake 5KB
CMakeASMInformation.cmake 5KB
TestBigEndian.cmake 5KB
FindOpenGL.cmake 5KB
CMakeFindEclipseCDT4.cmake 5KB
Windows-icl.cmake 5KB
共 574 条
- 1
- 2
- 3
- 4
- 5
- 6
资源评论
- gjghost2014-09-28不错,帮我解决了问题
Love_Qiu
- 粉丝: 5
- 资源: 18
上传资源 快速赚钱
- 我的内容管理 展开
- 我的资源 快来上传第一个资源
- 我的收益 登录查看自己的收益
- 我的积分 登录查看自己的积分
- 我的C币 登录后查看C币余额
- 我的收藏
- 我的下载
- 下载帮助
安全验证
文档复制为VIP权益,开通VIP直接复制
信息提交成功