mirror of
https://github.com/Kitware/CMake.git
synced 2026-04-24 07:08:38 -05:00
Nikita Nemkin
9890cfc4ec
Covers almost all blocks containing actual code, except: * Parsed-literal blocks can't be highlighted, including many command summaries and substitution-heavy docs like find_... commands. This is a Sphinx limitation. * Code with errors, like CMP0049, DEPLOYMENT_ADDITIONAL_FILES, DEPLOYMENT_REMOTE_DIRECTORY, @PACKAGE_INIT@ substitution in the tutorial, bracket arguments/comments in cmake-language.7 and cmake-developer.7. * FindQt4 module, which needs reformatting.
37 lines
1.5 KiB
ReStructuredText
37 lines
1.5 KiB
ReStructuredText
CMP0008
|
|
-------
|
|
|
|
.. |REMOVED_IN_CMAKE_VERSION| replace:: 4.0
|
|
.. include:: REMOVED_PROLOGUE.txt
|
|
|
|
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
|
|
|
|
.. code-block:: cmake
|
|
|
|
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 :ref:`Visual Studio Generators` IDE
|
|
and :generator:`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 Visual Studio 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.
|
|
|
|
.. |INTRODUCED_IN_CMAKE_VERSION| replace:: 2.6.1
|
|
.. |WARNED_OR_DID_NOT_WARN| replace:: warned
|
|
.. include:: REMOVED_EPILOGUE.txt
|