asskoala/CKG
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

first commit

Browse Source
This commit is contained in:
Jose Caban
2025-06-07 11:34:38 -04:00
commit 0eb2d7c07d
4708 changed files with 1500614 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

56
extern/cmake/2.85/doc/cmake-2.8/Copyright.txt vendored Normal file
View File

@@ -0,0 +1,56 @@
CMake - Cross Platform Makefile Generator
Copyright 2000-2009 Kitware, Inc., Insight Software Consortium
All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions
are met:
* Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
* 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.
* 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.
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.
------------------------------------------------------------------------------
The above copyright and license notice applies to distributions of
CMake in source and binary form. Some source files contain additional
notices of original copyright by their contributors; see each source
for details. Third-party software packages supplied with CMake under
compatible licenses provide their own copyright notices documented in
corresponding subdirectories.
------------------------------------------------------------------------------
CMake was initially developed by Kitware with the following sponsorship:
* National Library of Medicine at the National Institutes of Health
as part of the Insight Segmentation and Registration Toolkit (ITK).
* US National Labs (Los Alamos, Livermore, Sandia) ASC Parallel
Visualization Initiative.
* National Alliance for Medical Image Computing (NAMIC) is funded by the
National Institutes of Health through the NIH Roadmap for Medical Research,
Grant U54 EB005149.
* Kitware, Inc.

1001
extern/cmake/2.85/doc/cmake-2.8/cmake-commands.html vendored Normal file
View File

File diff suppressed because one or more lines are too long

3492
extern/cmake/2.85/doc/cmake-2.8/cmake-commands.txt vendored Normal file
View File

File diff suppressed because it is too large Load Diff

184
extern/cmake/2.85/doc/cmake-2.8/cmake-compatcommands.html vendored Normal file
View File

@@ -0,0 +1,184 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head><meta http-equiv="Content-Type" content="text/html;charset=utf-8" /><title>cmake-compatcommands - cmake</title></head><body>
<h2><a name="section_Index">Master Index CMake 2.8.5</a></h2>
<ul>
<li><a href="#section_Introduction"><b>Introduction</b></a></li>
<li><a href="#section_CompatibilityCommands"><b>Compatibility Commands</b></a></li>
<li><a href="#section_Copyright"><b>Copyright</b></a></li>
<li><a href="#section_SeeAlso"><b>See Also</b></a></li>
</ul>
<h2><a name="section_Introduction"/>Introduction</h2>
<p>cmake-compatcommands - Reference of CMake compatibility commands.</p>
<h2><a name="section_CompatibilityCommands"/>Compatibility Commands</h2>
<ul>
<li><a href="#command:build_name"><b><code>build_name</code></b></a></li> <li><a href="#command:exec_program"><b><code>exec_program</code></b></a></li> <li><a href="#command:export_library_dependencies"><b><code>export_library_dependencies</code></b></a></li> <li><a href="#command:install_files"><b><code>install_files</code></b></a></li> <li><a href="#command:install_programs"><b><code>install_programs</code></b></a></li> <li><a href="#command:install_targets"><b><code>install_targets</code></b></a></li> <li><a href="#command:link_libraries"><b><code>link_libraries</code></b></a></li> <li><a href="#command:make_directory"><b><code>make_directory</code></b></a></li> <li><a href="#command:output_required_files"><b><code>output_required_files</code></b></a></li> <li><a href="#command:remove"><b><code>remove</code></b></a></li> <li><a href="#command:subdir_depends"><b><code>subdir_depends</code></b></a></li> <li><a href="#command:subdirs"><b><code>subdirs</code></b></a></li> <li><a href="#command:use_mangled_mesa"><b><code>use_mangled_mesa</code></b></a></li> <li><a href="#command:utility_source"><b><code>utility_source</code></b></a></li> <li><a href="#command:variable_requires"><b><code>variable_requires</code></b></a></li> <li><a href="#command:write_file"><b><code>write_file</code></b></a></li></ul>
<pre> CMake Compatibility Listfile Commands - Obsolete commands supported by CMake for compatibility.</pre>
<p>This is the documentation for now obsolete listfile commands from previous CMake versions, which are still supported for compatibility reasons. You should instead use the newer, faster and shinier new commands. ;-)</p>
<ul>
<li>
<a name="command:build_name"><b><code>build_name</code></b></a>: Deprecated. Use ${CMAKE_SYSTEM} and ${CMAKE_CXX_COMPILER} instead.<br />
<pre> build_name(variable)<br /></pre>
<p>Sets the specified variable to a string representing the platform and compiler settings. These values are now available through the CMAKE_SYSTEM and CMAKE_CXX_COMPILER variables.</p>
</li>
<li>
<a name="command:exec_program"><b><code>exec_program</code></b></a>: Deprecated. Use the execute_process() command instead.<br />
<p>Run an executable program during the processing of the CMakeList.txt file.<br /></p>
<pre> exec_program(Executable [directory in which to run]<br /> [ARGS &lt;arguments to executable&gt;]<br /> [OUTPUT_VARIABLE &lt;var&gt;]<br /> [RETURN_VALUE &lt;var&gt;])<br /></pre>
<p>The executable is run in the optionally specified directory. The executable can include arguments if it is double quoted, but it is better to use the optional ARGS argument to specify arguments to the program. This is because cmake will then be able to escape spaces in the executable path. An optional argument OUTPUT_VARIABLE specifies a variable in which to store the output. To capture the return value of the execution, provide a RETURN_VALUE. If OUTPUT_VARIABLE is specified, then no output will go to the stdout/stderr of the console running cmake.<br /></p>
</li>
<li>
<a name="command:export_library_dependencies"><b><code>export_library_dependencies</code></b></a>: Deprecated. Use INSTALL(EXPORT) or EXPORT command.<br />
<p>This command generates an old-style library dependencies file. Projects requiring CMake 2.6 or later should not use the command. Use instead the install(EXPORT) command to help export targets from an installation tree and the export() command to export targets from a build tree.<br /></p>
<p>The old-style library dependencies file does not take into account per-configuration names of libraries or the LINK_INTERFACE_LIBRARIES target property.<br /></p>
<pre> export_library_dependencies(&lt;file&gt; [APPEND])<br /></pre>
<p>Create a file named &lt;file&gt; that can be included into a CMake listfile with the INCLUDE command. The file will contain a number of SET commands that will set all the variables needed for library dependency information. This should be the last command in the top level CMakeLists.txt file of the project. If the APPEND option is specified, the SET commands will be appended to the given file instead of replacing it.</p>
</li>
<li>
<a name="command:install_files"><b><code>install_files</code></b></a>: Deprecated. Use the install(FILES ) command instead.<br />
<p>This command has been superceded by the install command. It is provided for compatibility with older CMake code. The FILES form is directly replaced by the FILES form of the install command. The regexp form can be expressed more clearly using the GLOB form of the file command.<br /></p>
<pre> install_files(&lt;dir&gt; extension file file ...)<br /></pre>
<p>Create rules to install the listed files with the given extension into the given directory. Only files existing in the current source tree or its corresponding location in the binary tree may be listed. If a file specified already has an extension, that extension will be removed first. This is useful for providing lists of source files such as foo.cxx when you want the corresponding foo.h to be installed. A typical extension is '.h'.<br /></p>
<pre> install_files(&lt;dir&gt; regexp)<br /></pre>
<p>Any files in the current source directory that match the regular expression will be installed.<br /></p>
<pre> install_files(&lt;dir&gt; FILES file file ...)<br /></pre>
<p>Any files listed after the FILES keyword will be installed explicitly from the names given. Full paths are allowed in this form.<br /></p>
<p>The directory &lt;dir&gt; is relative to the installation prefix, which is stored in the variable CMAKE_INSTALL_PREFIX.</p>
</li>
<li>
<a name="command:install_programs"><b><code>install_programs</code></b></a>: Deprecated. Use the install(PROGRAMS ) command instead.<br />
<p>This command has been superceded by the install command. It is provided for compatibility with older CMake code. The FILES form is directly replaced by the PROGRAMS form of the INSTALL command. The regexp form can be expressed more clearly using the GLOB form of the FILE command.<br /></p>
<pre> install_programs(&lt;dir&gt; file1 file2 [file3 ...])<br /> install_programs(&lt;dir&gt; FILES file1 [file2 ...])<br /></pre>
<p>Create rules to install the listed programs into the given directory. Use the FILES argument to guarantee that the file list version of the command will be used even when there is only one argument.<br /></p>
<pre> install_programs(&lt;dir&gt; regexp)<br /></pre>
<p>In the second form any program in the current source directory that matches the regular expression will be installed.<br /></p>
<p>This command is intended to install programs that are not built by cmake, such as shell scripts. See the TARGETS form of the INSTALL command to create installation rules for targets built by cmake.<br /></p>
<p>The directory &lt;dir&gt; is relative to the installation prefix, which is stored in the variable CMAKE_INSTALL_PREFIX.</p>
</li>
<li>
<a name="command:install_targets"><b><code>install_targets</code></b></a>: Deprecated. Use the install(TARGETS ) command instead.<br />
<p>This command has been superceded by the install command. It is provided for compatibility with older CMake code.<br /></p>
<pre> install_targets(&lt;dir&gt; [RUNTIME_DIRECTORY dir] target target)<br /></pre>
<p>Create rules to install the listed targets into the given directory. The directory &lt;dir&gt; is relative to the installation prefix, which is stored in the variable CMAKE_INSTALL_PREFIX. If RUNTIME_DIRECTORY is specified, then on systems with special runtime files (Windows DLL), the files will be copied to that directory.</p>
</li>
<li>
<a name="command:link_libraries"><b><code>link_libraries</code></b></a>: Deprecated. Use the target_link_libraries() command instead.<br />
<p>Link libraries to all targets added later.<br /></p>
<pre> link_libraries(library1 &lt;debug | optimized&gt; library2 ...)<br /></pre>
<p>Specify a list of libraries to be linked into any following targets (typically added with the add_executable or add_library calls). This command is passed down to all subdirectories. The debug and optimized strings may be used to indicate that the next library listed is to be used only for that specific type of build.</p>
</li>
<li>
<a name="command:make_directory"><b><code>make_directory</code></b></a>: Deprecated. Use the file(MAKE_DIRECTORY ) command instead.<br />
<pre> make_directory(directory)<br /></pre>
<p>Creates the specified directory. Full paths should be given. Any parent directories that do not exist will also be created. Use with care.</p>
</li>
<li>
<a name="command:output_required_files"><b><code>output_required_files</code></b></a>: Deprecated. Approximate C preprocessor dependency scanning.<br />
<p>This command exists only because ancient CMake versions provided it. CMake handles preprocessor dependency scanning automatically using a more advanced scanner.<br /></p>
<pre> output_required_files(srcfile outputfile)<br /></pre>
<p>Outputs a list of all the source files that are required by the specified srcfile. This list is written into outputfile. This is similar to writing out the dependencies for srcfile except that it jumps from .h files into .cxx, .c and .cpp files if possible.</p>
</li>
<li>
<a name="command:remove"><b><code>remove</code></b></a>: Deprecated. Use the list(REMOVE_ITEM ) command instead.<br />
<pre> remove(VAR VALUE VALUE ...)<br /></pre>
<p>Removes VALUE from the variable VAR. This is typically used to remove entries from a vector (e.g. semicolon separated list). VALUE is expanded.</p>
</li>
<li>
<a name="command:subdir_depends"><b><code>subdir_depends</code></b></a>: Deprecated. Does nothing.<br />
<pre> subdir_depends(subdir dep1 dep2 ...)<br /></pre>
<p>Does not do anything. This command used to help projects order parallel builds correctly. This functionality is now automatic.</p>
</li>
<li>
<a name="command:subdirs"><b><code>subdirs</code></b></a>: Deprecated. Use the add_subdirectory() command instead.<br />
<p>Add a list of subdirectories to the build.<br /></p>
<pre> subdirs(dir1 dir2 ...[EXCLUDE_FROM_ALL exclude_dir1 exclude_dir2 ...]<br /> [PREORDER] )<br /></pre>
<p>Add a list of subdirectories to the build. The add_subdirectory command should be used instead of subdirs although subdirs will still work. This will cause any CMakeLists.txt files in the sub directories to be processed by CMake. Any directories after the PREORDER flag are traversed first by makefile builds, the PREORDER flag has no effect on IDE projects. Any directories after the EXCLUDE_FROM_ALL marker will not be included in the top level makefile or project file. This is useful for having CMake create makefiles or projects for a set of examples in a project. You would want CMake to generate makefiles or project files for all the examples at the same time, but you would not want them to show up in the top level project or be built each time make is run from the top.</p>
</li>
<li>
<a name="command:use_mangled_mesa"><b><code>use_mangled_mesa</code></b></a>: Copy mesa headers for use in combination with system GL.<br />
<pre> use_mangled_mesa(PATH_TO_MESA OUTPUT_DIRECTORY)<br /></pre>
<p>The path to mesa includes, should contain gl_mangle.h. The mesa headers are copied to the specified output directory. This allows mangled mesa headers to override other GL headers by being added to the include directory path earlier.</p>
</li>
<li>
<a name="command:utility_source"><b><code>utility_source</code></b></a>: Specify the source tree of a third-party utility.<br />
<pre> utility_source(cache_entry executable_name<br /> path_to_source [file1 file2 ...])<br /></pre>
<p>When a third-party utility's source is included in the distribution, this command specifies its location and name. The cache entry will not be set unless the path_to_source and all listed files exist. It is assumed that the source tree of the utility will have been built before it is needed.<br /></p>
<p>When cross compiling CMake will print a warning if a utility_source() command is executed, because in many cases it is used to build an executable which is executed later on. This doesn't work when cross compiling, since the executable can run only on their target platform. So in this case the cache entry has to be adjusted manually so it points to an executable which is runnable on the build host.</p>
</li>
<li>
<a name="command:variable_requires"><b><code>variable_requires</code></b></a>: Deprecated. Use the if() command instead.<br />
<p>Assert satisfaction of an option's required variables.<br /></p>
<pre> variable_requires(TEST_VARIABLE RESULT_VARIABLE<br /> REQUIRED_VARIABLE1<br /> REQUIRED_VARIABLE2 ...)<br /></pre>
<p>The first argument (TEST_VARIABLE) is the name of the variable to be tested, if that variable is false nothing else is done. If TEST_VARIABLE is true, then the next argument (RESULT_VARIABLE) is a variable that is set to true if all the required variables are set. The rest of the arguments are variables that must be true or not set to NOTFOUND to avoid an error. If any are not true, an error is reported.</p>
</li>
<li>
<a name="command:write_file"><b><code>write_file</code></b></a>: Deprecated. Use the file(WRITE ) command instead.<br />
<pre> write_file(filename "message to write"... [APPEND])<br /></pre>
<p>The first argument is the file name, the rest of the arguments are messages to write. If the argument APPEND is specified, then the message will be appended.<br /></p>
<p>NOTE 1: file(WRITE ... and file(APPEND ... do exactly the same as this one but add some more functionality.<br /></p>
<p>NOTE 2: When using write_file the produced file cannot be used as an input to CMake (CONFIGURE_FILE, source file ...) because it will lead to an infinite loop. Use configure_file if you want to generate input files to CMake.</p>
</li>
</ul>
<h2><a name="section_Copyright"/>Copyright</h2>
<p>Copyright 2000-2009 Kitware, Inc., Insight Software Consortium. All rights reserved.</p>
<p>Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:</p>
<p>Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.</p>
<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>
<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>
<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.</p>
<h2><a name="section_SeeAlso"/>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>The following resources are available to get help using CMake:</p>
<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.</p>
</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. </p>
</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.</p>
</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.</p>
</li>
</ul>
<p>Summary of helpful links:<br /></p>
<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>

348
extern/cmake/2.85/doc/cmake-2.8/cmake-compatcommands.txt vendored Normal file
View File

@@ -0,0 +1,348 @@
cmake version 2.8.5
------------------------------------------------------------------------------
Introduction
cmake-compatcommands - Reference of CMake compatibility commands.
------------------------------------------------------------------------------
Compatibility Commands
CMake Compatibility Listfile Commands - Obsolete commands supported by CMake for compatibility.
This is the documentation for now obsolete listfile commands from previous
CMake versions, which are still supported for compatibility reasons. You
should instead use the newer, faster and shinier new commands. ;-)
build_name
Deprecated. Use ${CMAKE_SYSTEM} and ${CMAKE_CXX_COMPILER} instead.
build_name(variable)
Sets the specified variable to a string representing the platform and
compiler settings. These values are now available through the
CMAKE_SYSTEM and CMAKE_CXX_COMPILER variables.
exec_program
Deprecated. Use the execute_process() command instead.
Run an executable program during the processing of the CMakeList.txt
file.
exec_program(Executable [directory in which to run]
[ARGS <arguments to executable>]
[OUTPUT_VARIABLE <var>]
[RETURN_VALUE <var>])
The executable is run in the optionally specified directory. The
executable can include arguments if it is double quoted, but it is
better to use the optional ARGS argument to specify arguments to the
program. This is because cmake will then be able to escape spaces in
the executable path. An optional argument OUTPUT_VARIABLE specifies a
variable in which to store the output. To capture the return value of
the execution, provide a RETURN_VALUE. If OUTPUT_VARIABLE is
specified, then no output will go to the stdout/stderr of the console
running cmake.
export_library_dependencies
Deprecated. Use INSTALL(EXPORT) or EXPORT command.
This command generates an old-style library dependencies file.
Projects requiring CMake 2.6 or later should not use the command. Use
instead the install(EXPORT) command to help export targets from an
installation tree and the export() command to export targets from a
build tree.
The old-style library dependencies file does not take into account
per-configuration names of libraries or the LINK_INTERFACE_LIBRARIES
target property.
export_library_dependencies(<file> [APPEND])
Create a file named <file> that can be included into a CMake listfile
with the INCLUDE command. The file will contain a number of SET
commands that will set all the variables needed for library dependency
information. This should be the last command in the top level
CMakeLists.txt file of the project. If the APPEND option is
specified, the SET commands will be appended to the given file instead
of replacing it.
install_files
Deprecated. Use the install(FILES ) command instead.
This command has been superceded by the install command. It is
provided for compatibility with older CMake code. The FILES form is
directly replaced by the FILES form of the install command. The
regexp form can be expressed more clearly using the GLOB form of the
file command.
install_files(<dir> extension file file ...)
Create rules to install the listed files with the given extension into
the given directory. Only files existing in the current source tree
or its corresponding location in the binary tree may be listed. If a
file specified already has an extension, that extension will be
removed first. This is useful for providing lists of source files
such as foo.cxx when you want the corresponding foo.h to be installed.
A typical extension is '.h'.
install_files(<dir> regexp)
Any files in the current source directory that match the regular
expression will be installed.
install_files(<dir> FILES file file ...)
Any files listed after the FILES keyword will be installed explicitly
from the names given. Full paths are allowed in this form.
The directory <dir> is relative to the installation prefix, which is
stored in the variable CMAKE_INSTALL_PREFIX.
install_programs
Deprecated. Use the install(PROGRAMS ) command instead.
This command has been superceded by the install command. It is
provided for compatibility with older CMake code. The FILES form is
directly replaced by the PROGRAMS form of the INSTALL command. The
regexp form can be expressed more clearly using the GLOB form of the
FILE command.
install_programs(<dir> file1 file2 [file3 ...])
install_programs(<dir> FILES file1 [file2 ...])
Create rules to install the listed programs into the given directory.
Use the FILES argument to guarantee that the file list version of the
command will be used even when there is only one argument.
install_programs(<dir> regexp)
In the second form any program in the current source directory that
matches the regular expression will be installed.
This command is intended to install programs that are not built by
cmake, such as shell scripts. See the TARGETS form of the INSTALL
command to create installation rules for targets built by cmake.
The directory <dir> is relative to the installation prefix, which is
stored in the variable CMAKE_INSTALL_PREFIX.
install_targets
Deprecated. Use the install(TARGETS ) command instead.
This command has been superceded by the install command. It is
provided for compatibility with older CMake code.
install_targets(<dir> [RUNTIME_DIRECTORY dir] target target)
Create rules to install the listed targets into the given directory.
The directory <dir> is relative to the installation prefix, which is
stored in the variable CMAKE_INSTALL_PREFIX. If RUNTIME_DIRECTORY is
specified, then on systems with special runtime files (Windows DLL),
the files will be copied to that directory.
link_libraries
Deprecated. Use the target_link_libraries() command instead.
Link libraries to all targets added later.
link_libraries(library1 <debug | optimized> library2 ...)
Specify a list of libraries to be linked into any following targets
(typically added with the add_executable or add_library calls). This
command is passed down to all subdirectories. The debug and optimized
strings may be used to indicate that the next library listed is to be
used only for that specific type of build.
make_directory
Deprecated. Use the file(MAKE_DIRECTORY ) command instead.
make_directory(directory)
Creates the specified directory. Full paths should be given. Any
parent directories that do not exist will also be created. Use with
care.
output_required_files
Deprecated. Approximate C preprocessor dependency scanning.
This command exists only because ancient CMake versions provided it.
CMake handles preprocessor dependency scanning automatically using a
more advanced scanner.
output_required_files(srcfile outputfile)
Outputs a list of all the source files that are required by the
specified srcfile. This list is written into outputfile. This is
similar to writing out the dependencies for srcfile except that it
jumps from .h files into .cxx, .c and .cpp files if possible.
remove
Deprecated. Use the list(REMOVE_ITEM ) command instead.
remove(VAR VALUE VALUE ...)
Removes VALUE from the variable VAR. This is typically used to remove
entries from a vector (e.g. semicolon separated list). VALUE is
expanded.
subdir_depends
Deprecated. Does nothing.
subdir_depends(subdir dep1 dep2 ...)
Does not do anything. This command used to help projects order
parallel builds correctly. This functionality is now automatic.
subdirs
Deprecated. Use the add_subdirectory() command instead.
Add a list of subdirectories to the build.
subdirs(dir1 dir2 ...[EXCLUDE_FROM_ALL exclude_dir1 exclude_dir2 ...]
[PREORDER] )
Add a list of subdirectories to the build. The add_subdirectory
command should be used instead of subdirs although subdirs will still
work. This will cause any CMakeLists.txt files in the sub directories
to be processed by CMake. Any directories after the PREORDER flag are
traversed first by makefile builds, the PREORDER flag has no effect on
IDE projects. Any directories after the EXCLUDE_FROM_ALL marker will
not be included in the top level makefile or project file. This is
useful for having CMake create makefiles or projects for a set of
examples in a project. You would want CMake to generate makefiles or
project files for all the examples at the same time, but you would not
want them to show up in the top level project or be built each time
make is run from the top.
use_mangled_mesa
Copy mesa headers for use in combination with system GL.
use_mangled_mesa(PATH_TO_MESA OUTPUT_DIRECTORY)
The path to mesa includes, should contain gl_mangle.h. The mesa
headers are copied to the specified output directory. This allows
mangled mesa headers to override other GL headers by being added to
the include directory path earlier.
utility_source
Specify the source tree of a third-party utility.
utility_source(cache_entry executable_name
path_to_source [file1 file2 ...])
When a third-party utility's source is included in the distribution,
this command specifies its location and name. The cache entry will
not be set unless the path_to_source and all listed files exist. It
is assumed that the source tree of the utility will have been built
before it is needed.
When cross compiling CMake will print a warning if a utility_source()
command is executed, because in many cases it is used to build an
executable which is executed later on. This doesn't work when cross
compiling, since the executable can run only on their target platform.
So in this case the cache entry has to be adjusted manually so it
points to an executable which is runnable on the build host.
variable_requires
Deprecated. Use the if() command instead.
Assert satisfaction of an option's required variables.
variable_requires(TEST_VARIABLE RESULT_VARIABLE
REQUIRED_VARIABLE1
REQUIRED_VARIABLE2 ...)
The first argument (TEST_VARIABLE) is the name of the variable to be
tested, if that variable is false nothing else is done. If
TEST_VARIABLE is true, then the next argument (RESULT_VARIABLE) is a
variable that is set to true if all the required variables are set.
The rest of the arguments are variables that must be true or not set
to NOTFOUND to avoid an error. If any are not true, an error is
reported.
write_file
Deprecated. Use the file(WRITE ) command instead.
write_file(filename "message to write"... [APPEND])
The first argument is the file name, the rest of the arguments are
messages to write. If the argument APPEND is specified, then the
message will be appended.
NOTE 1: file(WRITE ... and file(APPEND ... do exactly the same as
this one but add some more functionality.
NOTE 2: When using write_file the produced file cannot be used as an
input to CMake (CONFIGURE_FILE, source file ...) because it will lead
to an infinite loop. Use configure_file if you want to generate input
files to CMake.
------------------------------------------------------------------------------
Copyright
Copyright 2000-2009 Kitware, Inc., Insight Software Consortium. All rights
reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:
Redistributions of source code must retain the above copyright notice, this
list of conditions and the following disclaimer.
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.
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.
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.
------------------------------------------------------------------------------
See Also
The following resources are available to get help using CMake:
Home Page
http://www.cmake.org
The primary starting point for learning about CMake.
Frequently Asked Questions
http://www.cmake.org/Wiki/CMake_FAQ
A Wiki is provided containing answers to frequently asked questions.
Online Documentation
http://www.cmake.org/HTML/Documentation.html
Links to available documentation may be found on this web page.
Mailing List
http://www.cmake.org/HTML/MailingLists.html
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
http://www.cmake.org before posting questions to the list.
Summary of helpful links:
Home: http://www.cmake.org
Docs: http://www.cmake.org/HTML/Documentation.html
Mail: http://www.cmake.org/HTML/MailingLists.html
FAQ: http://www.cmake.org/Wiki/CMake_FAQ

8264
extern/cmake/2.85/doc/cmake-2.8/cmake-gui.docbook vendored Normal file
View File

File diff suppressed because it is too large Load Diff

5581
extern/cmake/2.85/doc/cmake-2.8/cmake-gui.html vendored Normal file
View File

File diff suppressed because one or more lines are too long

13886
extern/cmake/2.85/doc/cmake-2.8/cmake-gui.txt vendored Normal file
View File

File diff suppressed because it is too large Load Diff

2517
extern/cmake/2.85/doc/cmake-2.8/cmake-modules.html vendored Normal file
View File

File diff suppressed because one or more lines are too long

7079
extern/cmake/2.85/doc/cmake-2.8/cmake-modules.txt vendored Normal file
View File

File diff suppressed because it is too large Load Diff

215
extern/cmake/2.85/doc/cmake-2.8/cmake-policies.html vendored Normal file
View File

@@ -0,0 +1,215 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head><meta http-equiv="Content-Type" content="text/html;charset=utf-8" /><title>cmake-policies - cmake</title></head><body>
<h2><a name="section_Index">Master Index CMake 2.8.5</a></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_Policies"><b>Policies</b></a></li>
<li><a href="#section_Copyright"><b>Copyright</b></a></li>
<li><a href="#section_SeeAlso"><b>See Also</b></a></li>
</ul>
<h2><a name="section_Introduction"/>Introduction</h2>
<p>cmake-policies - Reference of CMake policies.</p>
<h2><a name="section_Description"/>Description</h2>
<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>
<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.</p>
<h2><a name="section_Policies"/>Policies</h2>
<ul>
<li><a href="#policy:CMP0000"><b><code>CMP0000</code></b></a></li> <li><a href="#policy:CMP0001"><b><code>CMP0001</code></b></a></li> <li><a href="#policy:CMP0002"><b><code>CMP0002</code></b></a></li> <li><a href="#policy:CMP0003"><b><code>CMP0003</code></b></a></li> <li><a href="#policy:CMP0004"><b><code>CMP0004</code></b></a></li> <li><a href="#policy:CMP0005"><b><code>CMP0005</code></b></a></li> <li><a href="#policy:CMP0006"><b><code>CMP0006</code></b></a></li> <li><a href="#policy:CMP0007"><b><code>CMP0007</code></b></a></li> <li><a href="#policy:CMP0008"><b><code>CMP0008</code></b></a></li> <li><a href="#policy:CMP0009"><b><code>CMP0009</code></b></a></li> <li><a href="#policy:CMP0010"><b><code>CMP0010</code></b></a></li> <li><a href="#policy:CMP0011"><b><code>CMP0011</code></b></a></li> <li><a href="#policy:CMP0012"><b><code>CMP0012</code></b></a></li> <li><a href="#policy:CMP0013"><b><code>CMP0013</code></b></a></li> <li><a href="#policy:CMP0014"><b><code>CMP0014</code></b></a></li> <li><a href="#policy:CMP0015"><b><code>CMP0015</code></b></a></li> <li><a href="#policy:CMP0016"><b><code>CMP0016</code></b></a></li> <li><a href="#policy:CMP0017"><b><code>CMP0017</code></b></a></li></ul>
<ul>
<li>
<a name="policy:CMP0000"><b><code>CMP0000</code></b></a>: A minimum required CMake version must be specified.<br />
<p>CMake requires that projects specify the version of CMake to which they have been written. This policy has been put in place so users trying to build the project may be told when they need to update their CMake. Specifying a version also helps the project build with CMake versions newer than that specified. Use the cmake_minimum_required command at the top of your main CMakeLists.txt file:<br /></p>
<pre> cmake_minimum_required(VERSION &lt;major&gt;.&lt;minor&gt;)<br /></pre>
<p>where "&lt;major&gt;.&lt;minor&gt;" is the version of CMake you want to support (such as "2.6"). The command will ensure that at least the given version of CMake is running and help newer versions be compatible with the project. See documentation of cmake_minimum_required for details.<br /></p>
<p>Note that the command invocation must appear in the CMakeLists.txt file itself; a call in an included file is not sufficient. However, the cmake_policy command may be called to set policy CMP0000 to OLD or NEW behavior explicitly. The OLD behavior is to silently ignore the missing invocation. The NEW behavior is to issue an error instead of a warning. An included file may set CMP0000 explicitly to affect how this policy is enforced for the main CMakeLists.txt file.<br /></p>
<p>This policy was introduced in CMake version 2.6.0.</p>
</li>
<li>
<a name="policy:CMP0001"><b><code>CMP0001</code></b></a>: CMAKE_BACKWARDS_COMPATIBILITY should no longer be used.<br />
<p>The OLD behavior is to check CMAKE_BACKWARDS_COMPATIBILITY and present it to the user. The NEW behavior is to ignore CMAKE_BACKWARDS_COMPATIBILITY completely.<br /></p>
<p>In CMake 2.4 and below the variable CMAKE_BACKWARDS_COMPATIBILITY was used to request compatibility with earlier versions of CMake. In CMake 2.6 and above all compatibility issues are handled by policies and the cmake_policy command. However, CMake must still check CMAKE_BACKWARDS_COMPATIBILITY for projects written for CMake 2.4 and below.<br /></p>
<p>This policy was introduced in CMake version 2.6.0. CMake version 2.8.5 warns when the policy is not set and uses OLD behavior. Use the cmake_policy command to set it to OLD or NEW explicitly.</p>
</li>
<li>
<a name="policy:CMP0002"><b><code>CMP0002</code></b></a>: Logical target names must be globally unique.<br />
<p>Targets names created with add_executable, add_library, or add_custom_target are logical build target names. Logical target names must be globally unique because:<br /></p>
<pre> - Unique names may be referenced unambiguously both in CMake<br /> code and on make tool command lines.<br /> - Logical names are used by Xcode and VS IDE generators<br /> to produce meaningful project names for the targets.<br /></pre>
<p>The logical name of executable and library targets does not have to correspond to the physical file names built. Consider using the OUTPUT_NAME target property to create two targets with the same physical name while keeping logical names distinct. Custom targets must simply have globally unique names (unless one uses the global property ALLOW_DUPLICATE_CUSTOM_TARGETS with a Makefiles generator).<br /></p>
<p>This policy was introduced in CMake version 2.6.0. CMake version 2.8.5 warns when the policy is not set and uses OLD behavior. Use the cmake_policy command to set it to OLD or NEW explicitly.</p>
</li>
<li>
<a name="policy:CMP0003"><b><code>CMP0003</code></b></a>: Libraries linked via full path no longer produce linker search paths.<br />
<p>This policy affects how libraries whose full paths are NOT known are found at link time, but was created due to a change in how CMake deals with libraries whose full paths are known. Consider the code<br /></p>
<pre> target_link_libraries(myexe /path/to/libA.so)<br /></pre>
<p>CMake 2.4 and below implemented linking to libraries whose full paths are known by splitting them on the link line into separate components consisting of the linker search path and the library name. The example code might have produced something like<br /></p>
<pre> ... -L/path/to -lA ...<br /></pre>
<p>in order to link to library A. An analysis was performed to order multiple link directories such that the linker would find library A in the desired location, but there are cases in which this does not work. CMake versions 2.6 and above use the more reliable approach of passing the full path to libraries directly to the linker in most cases. The example code now produces something like<br /></p>
<pre> ... /path/to/libA.so ....<br /></pre>
<p>Unfortunately this change can break code like<br /></p>
<pre> target_link_libraries(myexe /path/to/libA.so B)<br /></pre>
<p>where "B" is meant to find "/path/to/libB.so". This code is wrong because the user is asking the linker to find library B but has not provided a linker search path (which may be added with the link_directories command). However, with the old linking implementation the code would work accidentally because the linker search path added for library A allowed library B to be found.<br /></p>
<p>In order to support projects depending on linker search paths added by linking to libraries with known full paths, the OLD behavior for this policy will add the linker search paths even though they are not needed for their own libraries. When this policy is set to OLD, CMake will produce a link line such as<br /></p>
<pre> ... -L/path/to /path/to/libA.so -lB ...<br /></pre>
<p>which will allow library B to be found as it was previously. When this policy is set to NEW, CMake will produce a link line such as<br /></p>
<pre> ... /path/to/libA.so -lB ...<br /></pre>
<p>which more accurately matches what the project specified.<br /></p>
<p>The setting for this policy used when generating the link line is that in effect when the target is created by an add_executable or add_library command. For the example described above, the code<br /></p>
<pre> cmake_policy(SET CMP0003 OLD) # or cmake_policy(VERSION 2.4)<br /> add_executable(myexe myexe.c)<br /> target_link_libraries(myexe /path/to/libA.so B)<br /></pre>
<p>will work and suppress the warning for this policy. It may also be updated to work with the corrected linking approach:<br /></p>
<pre> cmake_policy(SET CMP0003 NEW) # or cmake_policy(VERSION 2.6)<br /> link_directories(/path/to) # needed to find library B<br /> add_executable(myexe myexe.c)<br /> target_link_libraries(myexe /path/to/libA.so B)<br /></pre>
<p>Even better, library B may be specified with a full path:<br /></p>
<pre> add_executable(myexe myexe.c)<br /> target_link_libraries(myexe /path/to/libA.so /path/to/libB.so)<br /></pre>
<p>When all items on the link line have known paths CMake does not check this policy so it has no effect.<br /></p>
<p>Note that the warning for this policy will be issued for at most one target. This avoids flooding users with messages for every target when setting the policy once will probably fix all targets.<br /></p>
<p>This policy was introduced in CMake version 2.6.0. CMake version 2.8.5 warns when the policy is not set and uses OLD behavior. Use the cmake_policy command to set it to OLD or NEW explicitly.</p>
</li>
<li>
<a name="policy:CMP0004"><b><code>CMP0004</code></b></a>: Libraries linked may not have leading or trailing whitespace.<br />
<p>CMake versions 2.4 and below silently removed leading and trailing whitespace from libraries linked with code like<br /></p>
<pre> target_link_libraries(myexe " A ")<br /></pre>
<p>This could lead to subtle errors in user projects.<br /></p>
<p>The OLD behavior for this policy is to silently remove leading and trailing whitespace. The NEW behavior for this policy is to diagnose the existence of such whitespace as an error. The setting for this policy used when checking the library names is that in effect when the target is created by an add_executable or add_library command.<br /></p>
<p>This policy was introduced in CMake version 2.6.0. CMake version 2.8.5 warns when the policy is not set and uses OLD behavior. Use the cmake_policy command to set it to OLD or NEW explicitly.</p>
</li>
<li>
<a name="policy:CMP0005"><b><code>CMP0005</code></b></a>: Preprocessor definition values are now escaped automatically.<br />
<p>This policy determines whether or not CMake should generate escaped preprocessor definition values added via add_definitions. CMake versions 2.4 and below assumed that only trivial values would be given for macros in add_definitions calls. It did not attempt to escape non-trivial values such as string literals in generated build rules. CMake versions 2.6 and above support escaping of most values, but cannot assume the user has not added escapes already in an attempt to work around limitations in earlier versions.<br /></p>
<p>The OLD behavior for this policy is to place definition values given to add_definitions directly in the generated build rules without attempting to escape anything. The NEW behavior for this policy is to generate correct escapes for all native build tools automatically. See documentation of the COMPILE_DEFINITIONS target property for limitations of the escaping implementation.<br /></p>
<p>This policy was introduced in CMake version 2.6.0. CMake version 2.8.5 warns when the policy is not set and uses OLD behavior. Use the cmake_policy command to set it to OLD or NEW explicitly.</p>
</li>
<li>
<a name="policy:CMP0006"><b><code>CMP0006</code></b></a>: Installing MACOSX_BUNDLE targets requires a BUNDLE DESTINATION.<br />
<p>This policy determines whether the install(TARGETS) command must be given a BUNDLE DESTINATION when asked to install a target with the MACOSX_BUNDLE property set. CMake 2.4 and below did not distinguish application bundles from normal executables when installing targets. CMake 2.6 provides a BUNDLE option to the install(TARGETS) command that specifies rules specific to application bundles on the Mac. Projects should use this option when installing a target with the MACOSX_BUNDLE property set.<br /></p>
<p>The OLD behavior for this policy is to fall back to the RUNTIME DESTINATION if a BUNDLE DESTINATION is not given. The NEW behavior for this policy is to produce an error if a bundle target is installed without a BUNDLE DESTINATION.<br /></p>
<p>This policy was introduced in CMake version 2.6.0. CMake version 2.8.5 warns when the policy is not set and uses OLD behavior. Use the cmake_policy command to set it to OLD or NEW explicitly.</p>
</li>
<li>
<a name="policy:CMP0007"><b><code>CMP0007</code></b></a>: list command no longer ignores empty elements.<br />
<p>This policy determines whether the list command will ignore empty elements in the list. CMake 2.4 and below list commands ignored all empty elements in the list. For example, a;b;;c would have length 3 and not 4. The OLD behavior for this policy is to ignore empty list elements. The NEW behavior for this policy is to correctly count empty elements in a list. <br /></p>
<p>This policy was introduced in CMake version 2.6.0. CMake version 2.8.5 warns when the policy is not set and uses OLD behavior. Use the cmake_policy command to set it to OLD or NEW explicitly.</p>
</li>
<li>
<a name="policy:CMP0008"><b><code>CMP0008</code></b></a>: Libraries linked by full-path must have a valid library file name.<br />
<p>In CMake 2.4 and below it is possible to write code like<br /></p>
<pre> target_link_libraries(myexe /full/path/to/somelib)<br /></pre>
<p>where "somelib" is supposed to be a valid library file name such as "libsomelib.a" or "somelib.lib". For Makefile generators this produces an error at build time because the dependency on the full path cannot be found. For VS IDE and Xcode generators this used to work by accident because CMake would always split off the library directory and ask the linker to search for the library by name (-lsomelib or somelib.lib). Despite the failure with Makefiles, some projects have code like this and build only with VS and/or Xcode. This version of CMake prefers to pass the full path directly to the native build tool, which will fail in this case because it does not name a valid library file.<br /></p>
<p>This policy determines what to do with full paths that do not appear to name a valid library file. The OLD behavior for this policy is to split the library name from the path and ask the linker to search for it. The NEW behavior for this policy is to trust the given path and pass it directly to the native build tool unchanged.<br /></p>
<p>This policy was introduced in CMake version 2.6.1. CMake version 2.8.5 warns when the policy is not set and uses OLD behavior. Use the cmake_policy command to set it to OLD or NEW explicitly.</p>
</li>
<li>
<a name="policy:CMP0009"><b><code>CMP0009</code></b></a>: FILE GLOB_RECURSE calls should not follow symlinks by default.<br />
<p>In CMake 2.6.1 and below, FILE GLOB_RECURSE calls would follow through symlinks, sometimes coming up with unexpectedly large result sets because of symlinks to top level directories that contain hundreds of thousands of files.<br /></p>
<p>This policy determines whether or not to follow symlinks encountered during a FILE GLOB_RECURSE call. The OLD behavior for this policy is to follow the symlinks. The NEW behavior for this policy is not to follow the symlinks by default, but only if FOLLOW_SYMLINKS is given as an additional argument to the FILE command.<br /></p>
<p>This policy was introduced in CMake version 2.6.2. CMake version 2.8.5 warns when the policy is not set and uses OLD behavior. Use the cmake_policy command to set it to OLD or NEW explicitly.</p>
</li>
<li>
<a name="policy:CMP0010"><b><code>CMP0010</code></b></a>: Bad variable reference syntax is an error.<br />
<p>In CMake 2.6.2 and below, incorrect variable reference syntax such as a missing close-brace ("${FOO") was reported but did not stop processing of CMake code. This policy determines whether a bad variable reference is an error. The OLD behavior for this policy is to warn about the error, leave the string untouched, and continue. The NEW behavior for this policy is to report an error.<br /></p>
<p>This policy was introduced in CMake version 2.6.3. CMake version 2.8.5 warns when the policy is not set and uses OLD behavior. Use the cmake_policy command to set it to OLD or NEW explicitly.</p>
</li>
<li>
<a name="policy:CMP0011"><b><code>CMP0011</code></b></a>: Included scripts do automatic cmake_policy PUSH and POP.<br />
<p>In CMake 2.6.2 and below, CMake Policy settings in scripts loaded by the include() and find_package() commands would affect the includer. Explicit invocations of cmake_policy(PUSH) and cmake_policy(POP) were required to isolate policy changes and protect the includer. While some scripts intend to affect the policies of their includer, most do not. In CMake 2.6.3 and above, include() and find_package() by default PUSH and POP an entry on the policy stack around an included script, but provide a NO_POLICY_SCOPE option to disable it. This policy determines whether or not to imply NO_POLICY_SCOPE for compatibility. The OLD behavior for this policy is to imply NO_POLICY_SCOPE for include() and find_package() commands. The NEW behavior for this policy is to allow the commands to do their default cmake_policy PUSH and POP.<br /></p>
<p>This policy was introduced in CMake version 2.6.3. CMake version 2.8.5 warns when the policy is not set and uses OLD behavior. Use the cmake_policy command to set it to OLD or NEW explicitly.</p>
</li>
<li>
<a name="policy:CMP0012"><b><code>CMP0012</code></b></a>: if() recognizes numbers and boolean constants.<br />
<p>In CMake versions 2.6.4 and lower the if() command implicitly dereferenced arguments corresponding to variables, even those named like numbers or boolean constants, except for 0 and 1. Numbers and boolean constants such as true, false, yes, no, on, off, y, n, notfound, ignore (all case insensitive) were recognized in some cases but not all. For example, the code "if(TRUE)" might have evaluated as false. Numbers such as 2 were recognized only in boolean expressions like "if(NOT 2)" (leading to false) but not as a single-argument like "if(2)" (also leading to false). Later versions of CMake prefer to treat numbers and boolean constants literally, so they should not be used as variable names.<br /></p>
<p>The OLD behavior for this policy is to implicitly dereference variables named like numbers and boolean constants. The NEW behavior for this policy is to recognize numbers and boolean constants without dereferencing variables with such names.<br /></p>
<p>This policy was introduced in CMake version 2.8.0. CMake version 2.8.5 warns when the policy is not set and uses OLD behavior. Use the cmake_policy command to set it to OLD or NEW explicitly.</p>
</li>
<li>
<a name="policy:CMP0013"><b><code>CMP0013</code></b></a>: Duplicate binary directories are not allowed.<br />
<p>CMake 2.6.3 and below silently permitted add_subdirectory() calls to create the same binary directory multiple times. During build system generation files would be written and then overwritten in the build tree and could lead to strange behavior. CMake 2.6.4 and above explicitly detect duplicate binary directories. CMake 2.6.4 always considers this case an error. In CMake 2.8.0 and above this policy determines whether or not the case is an error. The OLD behavior for this policy is to allow duplicate binary directories. The NEW behavior for this policy is to disallow duplicate binary directories with an error.<br /></p>
<p>This policy was introduced in CMake version 2.8.0. CMake version 2.8.5 warns when the policy is not set and uses OLD behavior. Use the cmake_policy command to set it to OLD or NEW explicitly.</p>
</li>
<li>
<a name="policy:CMP0014"><b><code>CMP0014</code></b></a>: Input directories must have CMakeLists.txt.<br />
<p>CMake versions before 2.8 silently ignored missing CMakeLists.txt files in directories referenced by add_subdirectory() or subdirs(), treating them as if present but empty. In CMake 2.8.0 and above this policy determines whether or not the case is an error. The OLD behavior for this policy is to silently ignore the problem. The NEW behavior for this policy is to report an error.<br /></p>
<p>This policy was introduced in CMake version 2.8.0. CMake version 2.8.5 warns when the policy is not set and uses OLD behavior. Use the cmake_policy command to set it to OLD or NEW explicitly.</p>
</li>
<li>
<a name="policy:CMP0015"><b><code>CMP0015</code></b></a>: link_directories() treats paths relative to the source dir.<br />
<p>In CMake 2.8.0 and lower the link_directories() command passed relative paths unchanged to the linker. In CMake 2.8.1 and above the link_directories() command prefers to interpret relative paths with respect to CMAKE_CURRENT_SOURCE_DIR, which is consistent with include_directories() and other commands. The OLD behavior for this policy is to use relative paths verbatim in the linker command. The NEW behavior for this policy is to convert relative paths to absolute paths by appending the relative path to CMAKE_CURRENT_SOURCE_DIR.<br /></p>
<p>This policy was introduced in CMake version 2.8.1. CMake version 2.8.5 warns when the policy is not set and uses OLD behavior. Use the cmake_policy command to set it to OLD or NEW explicitly.</p>
</li>
<li>
<a name="policy:CMP0016"><b><code>CMP0016</code></b></a>: target_link_libraries() reports error if only argument is not a target.<br />
<p>In CMake 2.8.2 and lower the target_link_libraries() command silently ignored if it was called with only one argument, and this argument wasn't a valid target. In CMake 2.8.3 and above it reports an error in this case.<br /></p>
<p>This policy was introduced in CMake version 2.8.3. CMake version 2.8.5 warns when the policy is not set and uses OLD behavior. Use the cmake_policy command to set it to OLD or NEW explicitly.</p>
</li>
<li>
<a name="policy:CMP0017"><b><code>CMP0017</code></b></a>: Prefer files from the CMake module directory when including from there.<br />
<p>Starting with CMake 2.8.4, if a cmake-module shipped with CMake (i.e. located in the CMake module directory) calls include() or find_package(), the files located in the the CMake module directory are preferred over the files in CMAKE_MODULE_PATH. This makes sure that the modules belonging to CMake always get those files included which they expect, and against which they were developed and tested. In call other cases, the files found in CMAKE_MODULE_PATH still take precedence over the ones in the CMake module directory. The OLD behaviour is to always prefer files from CMAKE_MODULE_PATH over files from the CMake modules directory.<br /></p>
<p>This policy was introduced in CMake version 2.8.4. CMake version 2.8.5 warns when the policy is not set and uses OLD behavior. Use the cmake_policy command to set it to OLD or NEW explicitly.</p>
</li>
</ul>
<h2><a name="section_Copyright"/>Copyright</h2>
<p>Copyright 2000-2009 Kitware, Inc., Insight Software Consortium. All rights reserved.</p>
<p>Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:</p>
<p>Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.</p>
<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>
<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>
<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.</p>
<h2><a name="section_SeeAlso"/>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>
<p>The following resources are available to get help using CMake:</p>
<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.</p>
</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. </p>
</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.</p>
</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.</p>
</li>
</ul>
<p>Summary of helpful links:<br /></p>
<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>

509
extern/cmake/2.85/doc/cmake-2.8/cmake-policies.txt vendored Normal file
View File

@@ -0,0 +1,509 @@
cmake version 2.8.5
------------------------------------------------------------------------------
Introduction
cmake-policies - Reference of CMake policies.
------------------------------------------------------------------------------
Description
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.
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.
------------------------------------------------------------------------------
Policies
CMP0000
A minimum required CMake version must be specified.
CMake requires that projects specify the version of CMake to which
they have been written. This policy has been put in place so users
trying to build the project may be told when they need to update their
CMake. Specifying a version also helps the project build with CMake
versions newer than that specified. Use the cmake_minimum_required
command at the top of your main CMakeLists.txt file:
cmake_minimum_required(VERSION <major>.<minor>)
where "<major>.<minor>" is the version of CMake you want to support
(such as "2.6"). The command will ensure that at least the given
version of CMake is running and help newer versions be compatible with
the project. See documentation of cmake_minimum_required for details.
Note that the command invocation must appear in the CMakeLists.txt
file itself; a call in an included file is not sufficient. However,
the cmake_policy command may be called to set policy CMP0000 to OLD or
NEW behavior explicitly. The OLD behavior is to silently ignore the
missing invocation. The NEW behavior is to issue an error instead of
a warning. An included file may set CMP0000 explicitly to affect how
this policy is enforced for the main CMakeLists.txt file.
This policy was introduced in CMake version 2.6.0.
CMP0001
CMAKE_BACKWARDS_COMPATIBILITY should no longer be used.
The OLD behavior is to check CMAKE_BACKWARDS_COMPATIBILITY and present
it to the user. The NEW behavior is to ignore
CMAKE_BACKWARDS_COMPATIBILITY completely.
In CMake 2.4 and below the variable CMAKE_BACKWARDS_COMPATIBILITY was
used to request compatibility with earlier versions of CMake. In
CMake 2.6 and above all compatibility issues are handled by policies
and the cmake_policy command. However, CMake must still check
CMAKE_BACKWARDS_COMPATIBILITY for projects written for CMake 2.4 and
below.
This policy was introduced in CMake version 2.6.0. CMake version
2.8.5 warns when the policy is not set and uses OLD behavior. Use the
cmake_policy command to set it to OLD or NEW explicitly.
CMP0002
Logical target names must be globally unique.
Targets names created with add_executable, add_library, or
add_custom_target are logical build target names. Logical target
names must be globally unique because:
- Unique names may be referenced unambiguously both in CMake
code and on make tool command lines.
- Logical names are used by Xcode and VS IDE generators
to produce meaningful project names for the targets.
The logical name of executable and library targets does not have to
correspond to the physical file names built. Consider using the
OUTPUT_NAME target property to create two targets with the same
physical name while keeping logical names distinct. Custom targets
must simply have globally unique names (unless one uses the global
property ALLOW_DUPLICATE_CUSTOM_TARGETS with a Makefiles generator).
This policy was introduced in CMake version 2.6.0. CMake version
2.8.5 warns when the policy is not set and uses OLD behavior. Use the
cmake_policy command to set it to OLD or NEW explicitly.
CMP0003
Libraries linked via full path no longer produce linker search paths.
This policy affects how libraries whose full paths are NOT known are
found at link time, but was created due to a change in how CMake deals
with libraries whose full paths are known. Consider the code
target_link_libraries(myexe /path/to/libA.so)
CMake 2.4 and below implemented linking to libraries whose full paths
are known by splitting them on the link line into separate components
consisting of the linker search path and the library name. The
example code might have produced something like
... -L/path/to -lA ...
in order to link to library A. An analysis was performed to order
multiple link directories such that the linker would find library A in
the desired location, but there are cases in which this does not work.
CMake versions 2.6 and above use the more reliable approach of passing
the full path to libraries directly to the linker in most cases. The
example code now produces something like
... /path/to/libA.so ....
Unfortunately this change can break code like
target_link_libraries(myexe /path/to/libA.so B)
where "B" is meant to find "/path/to/libB.so". This code is wrong
because the user is asking the linker to find library B but has not
provided a linker search path (which may be added with the
link_directories command). However, with the old linking
implementation the code would work accidentally because the linker
search path added for library A allowed library B to be found.
In order to support projects depending on linker search paths added by
linking to libraries with known full paths, the OLD behavior for this
policy will add the linker search paths even though they are not
needed for their own libraries. When this policy is set to OLD, CMake
will produce a link line such as
... -L/path/to /path/to/libA.so -lB ...
which will allow library B to be found as it was previously. When
this policy is set to NEW, CMake will produce a link line such as
... /path/to/libA.so -lB ...
which more accurately matches what the project specified.
The setting for this policy used when generating the link line is that
in effect when the target is created by an add_executable or
add_library command. For the example described above, the code
cmake_policy(SET CMP0003 OLD) # or cmake_policy(VERSION 2.4)
add_executable(myexe myexe.c)
target_link_libraries(myexe /path/to/libA.so B)
will work and suppress the warning for this policy. It may also be
updated to work with the corrected linking approach:
cmake_policy(SET CMP0003 NEW) # or cmake_policy(VERSION 2.6)
link_directories(/path/to) # needed to find library B
add_executable(myexe myexe.c)
target_link_libraries(myexe /path/to/libA.so B)
Even better, library B may be specified with a full path:
add_executable(myexe myexe.c)
target_link_libraries(myexe /path/to/libA.so /path/to/libB.so)
When all items on the link line have known paths CMake does not check
this policy so it has no effect.
Note that the warning for this policy will be issued for at most one
target. This avoids flooding users with messages for every target
when setting the policy once will probably fix all targets.
This policy was introduced in CMake version 2.6.0. CMake version
2.8.5 warns when the policy is not set and uses OLD behavior. Use the
cmake_policy command to set it to OLD or NEW explicitly.
CMP0004
Libraries linked may not have leading or trailing whitespace.
CMake versions 2.4 and below silently removed leading and trailing
whitespace from libraries linked with code like
target_link_libraries(myexe " A ")
This could lead to subtle errors in user projects.
The OLD behavior for this policy is to silently remove leading and
trailing whitespace. The NEW behavior for this policy is to diagnose
the existence of such whitespace as an error. The setting for this
policy used when checking the library names is that in effect when the
target is created by an add_executable or add_library command.
This policy was introduced in CMake version 2.6.0. CMake version
2.8.5 warns when the policy is not set and uses OLD behavior. Use the
cmake_policy command to set it to OLD or NEW explicitly.
CMP0005
Preprocessor definition values are now escaped automatically.
This policy determines whether or not CMake should generate escaped
preprocessor definition values added via add_definitions. CMake
versions 2.4 and below assumed that only trivial values would be given
for macros in add_definitions calls. It did not attempt to escape
non-trivial values such as string literals in generated build rules.
CMake versions 2.6 and above support escaping of most values, but
cannot assume the user has not added escapes already in an attempt to
work around limitations in earlier versions.
The OLD behavior for this policy is to place definition values given
to add_definitions directly in the generated build rules without
attempting to escape anything. The NEW behavior for this policy is to
generate correct escapes for all native build tools automatically.
See documentation of the COMPILE_DEFINITIONS target property for
limitations of the escaping implementation.
This policy was introduced in CMake version 2.6.0. CMake version
2.8.5 warns when the policy is not set and uses OLD behavior. Use the
cmake_policy command to set it to OLD or NEW explicitly.
CMP0006
Installing MACOSX_BUNDLE targets requires a BUNDLE DESTINATION.
This policy determines whether the install(TARGETS) command must be
given a BUNDLE DESTINATION when asked to install a target with the
MACOSX_BUNDLE property set. CMake 2.4 and below did not distinguish
application bundles from normal executables when installing targets.
CMake 2.6 provides a BUNDLE option to the install(TARGETS) command
that specifies rules specific to application bundles on the Mac.
Projects should use this option when installing a target with the
MACOSX_BUNDLE property set.
The OLD behavior for this policy is to fall back to the RUNTIME
DESTINATION if a BUNDLE DESTINATION is not given. The NEW behavior
for this policy is to produce an error if a bundle target is installed
without a BUNDLE DESTINATION.
This policy was introduced in CMake version 2.6.0. CMake version
2.8.5 warns when the policy is not set and uses OLD behavior. Use the
cmake_policy command to set it to OLD or NEW explicitly.
CMP0007
list command no longer ignores empty elements.
This policy determines whether the list command will ignore empty
elements in the list. CMake 2.4 and below list commands ignored all
empty elements in the list. For example, a;b;;c would have length 3
and not 4. The OLD behavior for this policy is to ignore empty list
elements. The NEW behavior for this policy is to correctly count
empty elements in a list.
This policy was introduced in CMake version 2.6.0. CMake version
2.8.5 warns when the policy is not set and uses OLD behavior. Use the
cmake_policy command to set it to OLD or NEW explicitly.
CMP0008
Libraries linked by full-path must have a valid library file name.
In CMake 2.4 and below it is possible to write code like
target_link_libraries(myexe /full/path/to/somelib)
where "somelib" is supposed to be a valid library file name such as
"libsomelib.a" or "somelib.lib". For Makefile generators this
produces an error at build time because the dependency on the full
path cannot be found. For VS IDE and Xcode generators this used to
work by accident because CMake would always split off the library
directory and ask the linker to search for the library by name
(-lsomelib or somelib.lib). Despite the failure with Makefiles, some
projects have code like this and build only with VS and/or Xcode.
This version of CMake prefers to pass the full path directly to the
native build tool, which will fail in this case because it does not
name a valid library file.
This policy determines what to do with full paths that do not appear
to name a valid library file. The OLD behavior for this policy is to
split the library name from the path and ask the linker to search for
it. The NEW behavior for this policy is to trust the given path and
pass it directly to the native build tool unchanged.
This policy was introduced in CMake version 2.6.1. CMake version
2.8.5 warns when the policy is not set and uses OLD behavior. Use the
cmake_policy command to set it to OLD or NEW explicitly.
CMP0009
FILE GLOB_RECURSE calls should not follow symlinks by default.
In CMake 2.6.1 and below, FILE GLOB_RECURSE calls would follow through
symlinks, sometimes coming up with unexpectedly large result sets
because of symlinks to top level directories that contain hundreds of
thousands of files.
This policy determines whether or not to follow symlinks encountered
during a FILE GLOB_RECURSE call. The OLD behavior for this policy is
to follow the symlinks. The NEW behavior for this policy is not to
follow the symlinks by default, but only if FOLLOW_SYMLINKS is given
as an additional argument to the FILE command.
This policy was introduced in CMake version 2.6.2. CMake version
2.8.5 warns when the policy is not set and uses OLD behavior. Use the
cmake_policy command to set it to OLD or NEW explicitly.
CMP0010
Bad variable reference syntax is an error.
In CMake 2.6.2 and below, incorrect variable reference syntax such as
a missing close-brace ("${FOO") was reported but did not stop
processing of CMake code. This policy determines whether a bad
variable reference is an error. The OLD behavior for this policy is
to warn about the error, leave the string untouched, and continue.
The NEW behavior for this policy is to report an error.
This policy was introduced in CMake version 2.6.3. CMake version
2.8.5 warns when the policy is not set and uses OLD behavior. Use the
cmake_policy command to set it to OLD or NEW explicitly.
CMP0011
Included scripts do automatic cmake_policy PUSH and POP.
In CMake 2.6.2 and below, CMake Policy settings in scripts loaded by
the include() and find_package() commands would affect the includer.
Explicit invocations of cmake_policy(PUSH) and cmake_policy(POP) were
required to isolate policy changes and protect the includer. While
some scripts intend to affect the policies of their includer, most do
not. In CMake 2.6.3 and above, include() and find_package() by
default PUSH and POP an entry on the policy stack around an included
script, but provide a NO_POLICY_SCOPE option to disable it. This
policy determines whether or not to imply NO_POLICY_SCOPE for
compatibility. The OLD behavior for this policy is to imply
NO_POLICY_SCOPE for include() and find_package() commands. The NEW
behavior for this policy is to allow the commands to do their default
cmake_policy PUSH and POP.
This policy was introduced in CMake version 2.6.3. CMake version
2.8.5 warns when the policy is not set and uses OLD behavior. Use the
cmake_policy command to set it to OLD or NEW explicitly.
CMP0012
if() recognizes numbers and boolean constants.
In CMake versions 2.6.4 and lower the if() command implicitly
dereferenced arguments corresponding to variables, even those named
like numbers or boolean constants, except for 0 and 1. Numbers and
boolean constants such as true, false, yes, no, on, off, y, n,
notfound, ignore (all case insensitive) were recognized in some cases
but not all. For example, the code "if(TRUE)" might have evaluated as
false. Numbers such as 2 were recognized only in boolean expressions
like "if(NOT 2)" (leading to false) but not as a single-argument like
"if(2)" (also leading to false). Later versions of CMake prefer to
treat numbers and boolean constants literally, so they should not be
used as variable names.
The OLD behavior for this policy is to implicitly dereference
variables named like numbers and boolean constants. The NEW behavior
for this policy is to recognize numbers and boolean constants without
dereferencing variables with such names.
This policy was introduced in CMake version 2.8.0. CMake version
2.8.5 warns when the policy is not set and uses OLD behavior. Use the
cmake_policy command to set it to OLD or NEW explicitly.
CMP0013
Duplicate binary directories are not allowed.
CMake 2.6.3 and below silently permitted add_subdirectory() calls to
create the same binary directory multiple times. During build system
generation files would be written and then overwritten in the build
tree and could lead to strange behavior. CMake 2.6.4 and above
explicitly detect duplicate binary directories. CMake 2.6.4 always
considers this case an error. In CMake 2.8.0 and above this policy
determines whether or not the case is an error. The OLD behavior for
this policy is to allow duplicate binary directories. The NEW
behavior for this policy is to disallow duplicate binary directories
with an error.
This policy was introduced in CMake version 2.8.0. CMake version
2.8.5 warns when the policy is not set and uses OLD behavior. Use the
cmake_policy command to set it to OLD or NEW explicitly.
CMP0014
Input directories must have CMakeLists.txt.
CMake versions before 2.8 silently ignored missing CMakeLists.txt
files in directories referenced by add_subdirectory() or subdirs(),
treating them as if present but empty. In CMake 2.8.0 and above this
policy determines whether or not the case is an error. The OLD
behavior for this policy is to silently ignore the problem. The NEW
behavior for this policy is to report an error.
This policy was introduced in CMake version 2.8.0. CMake version
2.8.5 warns when the policy is not set and uses OLD behavior. Use the
cmake_policy command to set it to OLD or NEW explicitly.
CMP0015
link_directories() treats paths relative to the source dir.
In CMake 2.8.0 and lower the link_directories() command passed
relative paths unchanged to the linker. In CMake 2.8.1 and above the
link_directories() command prefers to interpret relative paths with
respect to CMAKE_CURRENT_SOURCE_DIR, which is consistent with
include_directories() and other commands. The OLD behavior for this
policy is to use relative paths verbatim in the linker command. The
NEW behavior for this policy is to convert relative paths to absolute
paths by appending the relative path to CMAKE_CURRENT_SOURCE_DIR.
This policy was introduced in CMake version 2.8.1. CMake version
2.8.5 warns when the policy is not set and uses OLD behavior. Use the
cmake_policy command to set it to OLD or NEW explicitly.
CMP0016
target_link_libraries() reports error if only argument is not a
target.
In CMake 2.8.2 and lower the target_link_libraries() command silently
ignored if it was called with only one argument, and this argument
wasn't a valid target. In CMake 2.8.3 and above it reports an error
in this case.
This policy was introduced in CMake version 2.8.3. CMake version
2.8.5 warns when the policy is not set and uses OLD behavior. Use the
cmake_policy command to set it to OLD or NEW explicitly.
CMP0017
Prefer files from the CMake module directory when including from
there.
Starting with CMake 2.8.4, if a cmake-module shipped with CMake (i.e.
located in the CMake module directory) calls include() or
find_package(), the files located in the the CMake module directory
are preferred over the files in CMAKE_MODULE_PATH. This makes sure
that the modules belonging to CMake always get those files included
which they expect, and against which they were developed and tested.
In call other cases, the files found in CMAKE_MODULE_PATH still take
precedence over the ones in the CMake module directory. The OLD
behaviour is to always prefer files from CMAKE_MODULE_PATH over files
from the CMake modules directory.
This policy was introduced in CMake version 2.8.4. CMake version
2.8.5 warns when the policy is not set and uses OLD behavior. Use the
cmake_policy command to set it to OLD or NEW explicitly.
------------------------------------------------------------------------------
Copyright
Copyright 2000-2009 Kitware, Inc., Insight Software Consortium. All rights
reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:
Redistributions of source code must retain the above copyright notice, this
list of conditions and the following disclaimer.
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.
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.
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.
------------------------------------------------------------------------------
See Also
.B ccmake(1), cpack(1), ctest(1), cmakecommands(1), cmakecompat(1),
cmakemodules(1), cmakeprops(1), cmakevars(1)
The following resources are available to get help using CMake:
Home Page
http://www.cmake.org
The primary starting point for learning about CMake.
Frequently Asked Questions
http://www.cmake.org/Wiki/CMake_FAQ
A Wiki is provided containing answers to frequently asked questions.
Online Documentation
http://www.cmake.org/HTML/Documentation.html
Links to available documentation may be found on this web page.
Mailing List
http://www.cmake.org/HTML/MailingLists.html
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
http://www.cmake.org before posting questions to the list.
Summary of helpful links:
Home: http://www.cmake.org
Docs: http://www.cmake.org/HTML/Documentation.html
Mail: http://www.cmake.org/HTML/MailingLists.html
FAQ: http://www.cmake.org/Wiki/CMake_FAQ

1050
extern/cmake/2.85/doc/cmake-2.8/cmake-properties.html vendored Normal file
View File

File diff suppressed because one or more lines are too long

1771
extern/cmake/2.85/doc/cmake-2.8/cmake-properties.txt vendored Normal file
View File

File diff suppressed because it is too large Load Diff

921
extern/cmake/2.85/doc/cmake-2.8/cmake-variables.html vendored Normal file
View File

File diff suppressed because one or more lines are too long

1325
extern/cmake/2.85/doc/cmake-2.8/cmake-variables.txt vendored Normal file
View File

File diff suppressed because it is too large Load Diff

8570
extern/cmake/2.85/doc/cmake-2.8/cmake.docbook vendored Normal file
View File

File diff suppressed because it is too large Load Diff

5920
extern/cmake/2.85/doc/cmake-2.8/cmake.html vendored Normal file
View File

File diff suppressed because one or more lines are too long

14605
extern/cmake/2.85/doc/cmake-2.8/cmake.txt vendored Normal file
View File

File diff suppressed because it is too large Load Diff

34
extern/cmake/2.85/doc/cmake-2.8/cmcompress/Copyright.txt vendored Normal file
View File

@@ -0,0 +1,34 @@
Copyright (c) 1985, 1986 The Regents of the University of California.
All rights reserved.
This code is derived from software contributed to Berkeley by
James A. Woods, derived from original work by Spencer Thomas
and Joseph Orost.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions
are met:
1. Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
2. 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.
3. All advertising materials mentioning features or use of this software
must display the following acknowledgement:
This product includes software developed by the University of
California, Berkeley and its contributors.
4. Neither the name of the University nor the names of its contributors
may be used to endorse or promote products derived from this software
without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE REGENTS 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 REGENTS 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.

21
extern/cmake/2.85/doc/cmake-2.8/cmcurl/COPYING vendored Normal file
View File

@@ -0,0 +1,21 @@
COPYRIGHT AND PERMISSION NOTICE
Copyright (c) 1996 - 2009, Daniel Stenberg, <daniel@haxx.se>.
All rights reserved.
Permission to use, copy, modify, and distribute this software for any purpose
with or without fee is hereby granted, provided that the above copyright
notice and this permission notice appear in all copies.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OF THIRD PARTY RIGHTS. IN
NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM,
DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR
OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE
OR OTHER DEALINGS IN THE SOFTWARE.
Except as contained in this notice, the name of a copyright holder shall not
be used in advertising or otherwise to promote the sale, use or other dealings
in this Software without prior written authorization of the copyright holder.

21
extern/cmake/2.85/doc/cmake-2.8/cmexpat/COPYING vendored Normal file
View File

@@ -0,0 +1,21 @@
Copyright (c) 1998, 1999, 2000 Thai Open Source Software Center Ltd
and Clark Cooper
Permission is hereby granted, free of charge, to any person obtaining
a copy of this software and associated documentation files (the
"Software"), to deal in the Software without restriction, including
without limitation the rights to use, copy, modify, merge, publish,
distribute, sublicense, and/or sell copies of the Software, and to
permit persons to whom the Software is furnished to do so, subject to
the following conditions:
The above copyright notice and this permission notice shall be included
in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

60
extern/cmake/2.85/doc/cmake-2.8/cmlibarchive/COPYING vendored Normal file
View File

@@ -0,0 +1,60 @@
The libarchive distribution as a whole is Copyright by Tim Kientzle
and is subject to the copyright notice reproduced at the bottom of
this file.
Each individual file in this distribution should have a clear
copyright/licensing statement at the beginning of the file. If any do
not, please let me know and I will rectify it. The following is
intended to summarize the copyright status of the individual files;
the actual statements in the files are controlling.
* Except as listed below, all C sources (including .c and .h files)
and documentation files are subject to the copyright notice reproduced
at the bottom of this file.
* The following source files are also subject in whole or in part to
a 3-clause UC Regents copyright; please read the individual source
files for details:
libarchive/archive_entry.c
libarchive/archive_read_support_compression_compress.c
libarchive/archive_write_set_compression_compress.c
libarchive/mtree.5
tar/matching.c
* The following source files are in the public domain:
tar/getdate.c
* The build files---including Makefiles, configure scripts,
and auxiliary scripts used as part of the compile process---have
widely varying licensing terms. Please check individual files before
distributing them to see if those restrictions apply to you.
I intend for all new source code to use the license below and hope over
time to replace code with other licenses with new implementations that
do use the license below. The varying licensing of the build scripts
seems to be an unavoidable mess.
Copyright (c) 2003-2009 <author(s)>
All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions
are met:
1. Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer
in this position and unchanged.
2. 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.
THIS SOFTWARE IS PROVIDED BY THE AUTHOR(S) ``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 AUTHOR(S) 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.

31
extern/cmake/2.85/doc/cmake-2.8/cmsys/Copyright.txt vendored Normal file
View File

@@ -0,0 +1,31 @@
KWSys - Kitware System Library
Copyright 2000-2009 Kitware, Inc., Insight Software Consortium
All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions
are met:
* Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
* 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.
* 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.
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.

23
extern/cmake/2.85/doc/cmake-2.8/cmzlib/Copyright.txt vendored Normal file
View File

@@ -0,0 +1,23 @@
'zlib' general purpose compression library
version 1.2.3, July 18th, 2005
Copyright (C) 1995-2005 Jean-loup Gailly and Mark Adler
This software is provided 'as-is', without any express or implied
warranty. In no event will the authors be held liable for any damages
arising from the use of this software.
Permission is granted to anyone to use this software for any purpose,
including commercial applications, and to alter it and redistribute it
freely, subject to the following restrictions:
1. The origin of this software must not be misrepresented; you must not
claim that you wrote the original software. If you use this software
in a product, an acknowledgment in the product documentation would be
appreciated but is not required.
2. Altered source versions must be plainly marked as such, and must not be
misrepresented as being the original software.
3. This notice may not be removed or altered from any source distribution.
Jean-loup Gailly Mark Adler
jloup@gzip.org madler@alumni.caltech.edu

143
extern/cmake/2.85/doc/cmake-2.8/cpack.docbook vendored Normal file
View File

@@ -0,0 +1,143 @@
<?xml version="1.0" ?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V4.2//EN" "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [
<!ENTITY % addindex "IGNORE">
<!ENTITY % English "INCLUDE"> ]>
<article>
<articleinfo>
<title>cpack - cpack</title>
</articleinfo>
<sect1 id="section_Name">
<title>
Name</title>
<itemizedlist>
</itemizedlist>
<literallayout> cpack - Packaging driver provided by CMake.</literallayout>
</sect1>
<sect1 id="section_Usage">
<title>
Usage</title>
<itemizedlist>
</itemizedlist>
<literallayout> cpack -G &lt;generator&gt; [options]</literallayout>
</sect1>
<sect1 id="section_Description">
<title>
Description</title>
<itemizedlist>
</itemizedlist>
<para>The "cpack" executable is the CMake packaging program. CMake-generated build trees created for projects that use the INSTALL_* commands have packaging support. This program will generate the package.</para>
<para>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.</para>
</sect1>
<sect1 id="section_Options">
<title>
Options</title>
<itemizedlist>
<listitem><link linkend="opt_-G &lt;generator&gt;"><emphasis><literal>-G &lt;generator&gt;</literal></emphasis></link></listitem>
<listitem><link linkend="opt_-C &lt;Configuration&gt;"><emphasis><literal>-C &lt;Configuration&gt;</literal></emphasis></link></listitem>
<listitem><link linkend="opt_-D &lt;var&gt;=&lt;value&gt;"><emphasis><literal>-D &lt;var&gt;=&lt;value&gt;</literal></emphasis></link></listitem>
<listitem><link linkend="opt_--config &lt;config file&gt;"><emphasis><literal>--config &lt;config file&gt;</literal></emphasis></link></listitem>
</itemizedlist>
<para id="opt_-G &lt;generator&gt;"><sect2><title>-G &lt;generator&gt;</title></sect2> Use the specified generator to generate package.</para>
<para>CPack may support multiple native packaging systems on certain platforms. A generator is responsible for generating input files for particular system and invoking that systems. Possible generator names are specified in the Generators section.</para>
<para id="opt_-C &lt;Configuration&gt;"><sect2><title>-C &lt;Configuration&gt;</title></sect2> Specify the project configuration</para>
<para>This option specifies the configuration that the project was build with, for example 'Debug', 'Release'.</para>
<para id="opt_-D &lt;var&gt;=&lt;value&gt;"><sect2><title>-D &lt;var&gt;=&lt;value&gt;</title></sect2> Set a CPack variable.</para>
<para>Set a variable that can be used by the generator.</para>
<para id="opt_--config &lt;config file&gt;"><sect2><title>--config &lt;config file&gt;</title></sect2> Specify the config file.</para>
<para>Specify the config file to use to create the package. By default CPackConfig.cmake in the current directory will be used.</para>
</sect1>
<sect1 id="section_Generators">
<title>
Generators</title>
<itemizedlist>
<listitem><link linkend="gen_NSIS"><emphasis><literal>NSIS</literal></emphasis></link></listitem>
<listitem><link linkend="gen_STGZ"><emphasis><literal>STGZ</literal></emphasis></link></listitem>
<listitem><link linkend="gen_TBZ2"><emphasis><literal>TBZ2</literal></emphasis></link></listitem>
<listitem><link linkend="gen_TGZ"><emphasis><literal>TGZ</literal></emphasis></link></listitem>
<listitem><link linkend="gen_TZ"><emphasis><literal>TZ</literal></emphasis></link></listitem>
<listitem><link linkend="gen_ZIP"><emphasis><literal>ZIP</literal></emphasis></link></listitem>
</itemizedlist>
<para id="gen_NSIS"><sect2><title>NSIS</title></sect2> Null Soft Installer</para>
<para id="gen_STGZ"><sect2><title>STGZ</title></sect2> Self extracting Tar GZip compression</para>
<para id="gen_TBZ2"><sect2><title>TBZ2</title></sect2> Tar BZip2 compression</para>
<para id="gen_TGZ"><sect2><title>TGZ</title></sect2> Tar GZip compression</para>
<para id="gen_TZ"><sect2><title>TZ</title></sect2> Tar Compress compression</para>
<para id="gen_ZIP"><sect2><title>ZIP</title></sect2> ZIP file format</para>
</sect1>
<sect1 id="section_Properties">
<title>
Properties</title>
<itemizedlist>
</itemizedlist>
<literallayout> CMake Properties - Properties supported by CMake, the Cross-Platform Makefile Generator.</literallayout>
<para>This is the documentation for the properties supported by CMake. Properties can have different scopes. They can either be assigned to a source file, a directory, a target or globally to CMake. By modifying the values of properties the behaviour of the build system can be customized.</para>
</sect1>
<sect1 id="section_Compatibility Commands">
<title>
Compatibility Commands</title>
<itemizedlist>
</itemizedlist>
<literallayout> CMake Compatibility Listfile Commands - Obsolete commands supported by CMake for compatibility.</literallayout>
<para>This is the documentation for now obsolete listfile commands from previous CMake versions, which are still supported for compatibility reasons. You should instead use the newer, faster and shinier new commands. ;-)</para>
</sect1>
<sect1 id="section_Standard CMake Modules">
<title>
Standard CMake Modules</title>
</sect1>
<sect1 id="section_Copyright">
<title>
Copyright</title>
<itemizedlist>
</itemizedlist>
<para>Copyright 2000-2009 Kitware, Inc., Insight Software Consortium. All rights reserved.</para>
<para>Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:</para>
<para>Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.</para>
<para>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.</para>
<para>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.</para>
<para>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.</para>
</sect1>
<sect1 id="section_See Also">
<title>
See Also</title>
<itemizedlist>
<listitem><link linkend="see_Home Page"><emphasis><literal>Home Page</literal></emphasis></link></listitem>
<listitem><link linkend="see_Frequently Asked Questions"><emphasis><literal>Frequently Asked Questions</literal></emphasis></link></listitem>
<listitem><link linkend="see_Online Documentation"><emphasis><literal>Online Documentation</literal></emphasis></link></listitem>
<listitem><link linkend="see_Mailing List"><emphasis><literal>Mailing List</literal></emphasis></link></listitem>
</itemizedlist>
<para>The following resources are available to get help using CMake:</para>
<para id="see_Home Page"><sect2><title>Home Page</title></sect2> <ulink url="http://www.cmake.org" /></para>
<para>The primary starting point for learning about CMake.</para>
<para id="see_Frequently Asked Questions"><sect2><title>Frequently Asked Questions</title></sect2> <ulink url="http://www.cmake.org/Wiki/CMake_FAQ" /></para>
<para>A Wiki is provided containing answers to frequently asked questions. </para>
<para id="see_Online Documentation"><sect2><title>Online Documentation</title></sect2> <ulink url="http://www.cmake.org/HTML/Documentation.html" /></para>
<para>Links to available documentation may be found on this web page.</para>
<para id="see_Mailing List"><sect2><title>Mailing List</title></sect2> <ulink url="http://www.cmake.org/HTML/MailingLists.html" /></para>
<para>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 <ulink url="http://www.cmake.org" /> before posting questions to the list.</para>
<para>Summary of helpful links:
</para><literallayout> Home: <ulink url="http://www.cmake.org" />
Docs: <ulink url="http://www.cmake.org/HTML/Documentation.html" />
Mail: <ulink url="http://www.cmake.org/HTML/MailingLists.html" />
FAQ: <ulink url="http://www.cmake.org/Wiki/CMake_FAQ" />
</literallayout>
</sect1>
</article>

130
extern/cmake/2.85/doc/cmake-2.8/cpack.html vendored Normal file
View File

@@ -0,0 +1,130 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head><meta http-equiv="Content-Type" content="text/html;charset=utf-8" /><title>cpack - cpack</title></head><body>
<h2><a name="section_Index">Master Index CMake 2.8.5</a></h2>
<ul>
<li><a href="#section_Name"><b>Name</b></a></li>
<li><a href="#section_Usage"><b>Usage</b></a></li>
<li><a href="#section_Description"><b>Description</b></a></li>
<li><a href="#section_Options"><b>Options</b></a></li>
<li><a href="#section_Generators"><b>Generators</b></a></li>
<li><a href="#section_Properties"><b>Properties</b></a></li>
<li><a href="#section_CompatibilityCommands"><b>Compatibility Commands</b></a></li>
<li><a href="#section_StandardCMakeModules"><b>Standard CMake Modules</b></a></li>
<li><a href="#section_Copyright"><b>Copyright</b></a></li>
<li><a href="#section_SeeAlso"><b>See Also</b></a></li>
</ul>
<h2><a name="section_Name"/>Name</h2>
<pre> cpack - Packaging driver provided by CMake.</pre>
<h2><a name="section_Usage"/>Usage</h2>
<pre> cpack -G &lt;generator&gt; [options]</pre>
<h2><a name="section_Description"/>Description</h2>
<p>The "cpack" executable is the CMake packaging program. CMake-generated build trees created for projects that use the INSTALL_* commands have packaging support. This program will generate the package.</p>
<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.</p>
<h2><a name="section_Options"/>Options</h2>
<ul>
<li><a href="#opt:-Ggenerator"><b><code>-G &lt;generator&gt;</code></b></a></li> <li><a href="#opt:-CConfiguration"><b><code>-C &lt;Configuration&gt;</code></b></a></li> <li><a href="#opt:-Dvarvalue"><b><code>-D &lt;var&gt;=&lt;value&gt;</code></b></a></li> <li><a href="#opt:--configconfigfile"><b><code>--config &lt;config file&gt;</code></b></a></li></ul>
<ul>
<li>
<a name="opt:-Ggenerator"><b><code>-G &lt;generator&gt;</code></b></a>: Use the specified generator to generate package.<br />
<p>CPack may support multiple native packaging systems on certain platforms. A generator is responsible for generating input files for particular system and invoking that systems. Possible generator names are specified in the Generators section.</p>
</li>
<li>
<a name="opt:-CConfiguration"><b><code>-C &lt;Configuration&gt;</code></b></a>: Specify the project configuration<br />
<p>This option specifies the configuration that the project was build with, for example 'Debug', 'Release'.</p>
</li>
<li>
<a name="opt:-Dvarvalue"><b><code>-D &lt;var&gt;=&lt;value&gt;</code></b></a>: Set a CPack variable.<br />
<p>Set a variable that can be used by the generator.</p>
</li>
<li>
<a name="opt:--configconfigfile"><b><code>--config &lt;config file&gt;</code></b></a>: Specify the config file.<br />
<p>Specify the config file to use to create the package. By default CPackConfig.cmake in the current directory will be used.</p>
</li>
</ul>
<h2><a name="section_Generators"/>Generators</h2>
<ul>
<li><a href="#gen:NSIS"><b><code>NSIS</code></b></a></li> <li><a href="#gen:STGZ"><b><code>STGZ</code></b></a></li> <li><a href="#gen:TBZ2"><b><code>TBZ2</code></b></a></li> <li><a href="#gen:TGZ"><b><code>TGZ</code></b></a></li> <li><a href="#gen:TZ"><b><code>TZ</code></b></a></li> <li><a href="#gen:ZIP"><b><code>ZIP</code></b></a></li></ul>
<ul>
<li>
<a name="gen:NSIS"><b><code>NSIS</code></b></a>: Null Soft Installer
</li>
<li>
<a name="gen:STGZ"><b><code>STGZ</code></b></a>: Self extracting Tar GZip compression
</li>
<li>
<a name="gen:TBZ2"><b><code>TBZ2</code></b></a>: Tar BZip2 compression
</li>
<li>
<a name="gen:TGZ"><b><code>TGZ</code></b></a>: Tar GZip compression
</li>
<li>
<a name="gen:TZ"><b><code>TZ</code></b></a>: Tar Compress compression
</li>
<li>
<a name="gen:ZIP"><b><code>ZIP</code></b></a>: ZIP file format
</li>
</ul>
<h2><a name="section_Properties"/>Properties</h2>
<pre> CMake Properties - Properties supported by CMake, the Cross-Platform Makefile Generator.</pre>
<p>This is the documentation for the properties supported by CMake. Properties can have different scopes. They can either be assigned to a source file, a directory, a target or globally to CMake. By modifying the values of properties the behaviour of the build system can be customized.</p>
<h2><a name="section_CompatibilityCommands"/>Compatibility Commands</h2>
<pre> CMake Compatibility Listfile Commands - Obsolete commands supported by CMake for compatibility.</pre>
<p>This is the documentation for now obsolete listfile commands from previous CMake versions, which are still supported for compatibility reasons. You should instead use the newer, faster and shinier new commands. ;-)</p>
<h2><a name="section_StandardCMakeModules"/>Standard CMake Modules</h2>
<h2><a name="section_Copyright"/>Copyright</h2>
<p>Copyright 2000-2009 Kitware, Inc., Insight Software Consortium. All rights reserved.</p>
<p>Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:</p>
<p>Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.</p>
<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>
<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>
<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.</p>
<h2><a name="section_SeeAlso"/>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>The following resources are available to get help using CMake:</p>
<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.</p>
</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. </p>
</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.</p>
</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.</p>
</li>
</ul>
<p>Summary of helpful links:<br /></p>
<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>

163
extern/cmake/2.85/doc/cmake-2.8/cpack.txt vendored Normal file
View File

@@ -0,0 +1,163 @@
cpack version 2.8.5
------------------------------------------------------------------------------
Name
cpack - Packaging driver provided by CMake.
------------------------------------------------------------------------------
Usage
cpack -G <generator> [options]
------------------------------------------------------------------------------
Description
The "cpack" executable is the CMake packaging program. CMake-generated build
trees created for projects that use the INSTALL_* commands have packaging
support. This program will generate the package.
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.
------------------------------------------------------------------------------
Options
-G <generator>
Use the specified generator to generate package.
CPack may support multiple native packaging systems on certain
platforms. A generator is responsible for generating input files for
particular system and invoking that systems. Possible generator names
are specified in the Generators section.
-C <Configuration>
Specify the project configuration
This option specifies the configuration that the project was build
with, for example 'Debug', 'Release'.
-D <var>=<value>
Set a CPack variable.
Set a variable that can be used by the generator.
--config <config file>
Specify the config file.
Specify the config file to use to create the package. By default
CPackConfig.cmake in the current directory will be used.
------------------------------------------------------------------------------
Generators
NSIS
Null Soft Installer
STGZ
Self extracting Tar GZip compression
TBZ2
Tar BZip2 compression
TGZ
Tar GZip compression
TZ
Tar Compress compression
ZIP
ZIP file format
------------------------------------------------------------------------------
Properties
CMake Properties - Properties supported by CMake, the Cross-Platform Makefile Generator.
This is the documentation for the properties supported by CMake. Properties
can have different scopes. They can either be assigned to a source file, a
directory, a target or globally to CMake. By modifying the values of
properties the behaviour of the build system can be customized.
------------------------------------------------------------------------------
Compatibility Commands
CMake Compatibility Listfile Commands - Obsolete commands supported by CMake for compatibility.
This is the documentation for now obsolete listfile commands from previous
CMake versions, which are still supported for compatibility reasons. You
should instead use the newer, faster and shinier new commands. ;-)
------------------------------------------------------------------------------
Standard CMake Modules
------------------------------------------------------------------------------
Copyright
Copyright 2000-2009 Kitware, Inc., Insight Software Consortium. All rights
reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:
Redistributions of source code must retain the above copyright notice, this
list of conditions and the following disclaimer.
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.
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.
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.
------------------------------------------------------------------------------
See Also
The following resources are available to get help using CMake:
Home Page
http://www.cmake.org
The primary starting point for learning about CMake.
Frequently Asked Questions
http://www.cmake.org/Wiki/CMake_FAQ
A Wiki is provided containing answers to frequently asked questions.
Online Documentation
http://www.cmake.org/HTML/Documentation.html
Links to available documentation may be found on this web page.
Mailing List
http://www.cmake.org/HTML/MailingLists.html
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
http://www.cmake.org before posting questions to the list.
Summary of helpful links:
Home: http://www.cmake.org
Docs: http://www.cmake.org/HTML/Documentation.html
Mail: http://www.cmake.org/HTML/MailingLists.html
FAQ: http://www.cmake.org/Wiki/CMake_FAQ

1514
extern/cmake/2.85/doc/cmake-2.8/ctest.docbook vendored Normal file
View File

File diff suppressed because it is too large Load Diff

1041
extern/cmake/2.85/doc/cmake-2.8/ctest.html vendored Normal file
View File

File diff suppressed because one or more lines are too long

2792
extern/cmake/2.85/doc/cmake-2.8/ctest.txt vendored Normal file
View File

File diff suppressed because it is too large Load Diff