2015-06-12 20:42:25 +02:00
|
|
|
$NetBSD: distinfo,v 1.72 2015/06/12 18:42:25 richard Exp $
|
import cmake-1.6.6
CMake is an extensible, open-source system that manages the build
process in an operating system and compiler independent manner. Unlike
many cross-platform systems, CMake is designed to be used in
conjunction with the native build environment. Simple configuration
files placed in each source directory (called CMakeLists.txt files)
are used to generate standard build files (e.g., makefiles on Unix and
projects/workspaces in Windows MSVC) which are used in the usual
way. CMake can compile source code, create libraries, generate
wrappers, and build executables in arbitrary combinations. CMake
supports in-place and out-of-place builds, and can therefore support
multiple builds from a single source tree. CMake also supports static
and dynamic library builds. Another nice feature of CMake is that it
generates a cache file that is designed to be used with a graphical
editor. For example, when CMake runs, it locates include files,
libraries, and executable, and may encounter optional build
directives. This information is gathered into the cache, which may be
changed by the user prior to the generation of the native build files.
2003-05-07 13:55:03 +02:00
|
|
|
|
2015-06-09 10:21:40 +02:00
|
|
|
SHA1 (cmake-3.2.3.tar.gz) = fa176cc5b1ccf2e98196b50908432d0268323501
|
|
|
|
RMD160 (cmake-3.2.3.tar.gz) = 7cd30ba8d58d1d312fb59f6f02c34d3842123fab
|
|
|
|
Size (cmake-3.2.3.tar.gz) = 6438938 bytes
|
2015-06-12 20:42:25 +02:00
|
|
|
SHA1 (patch-Modules_FindX11.cmake) = d616d5ad370b115ecd3c735e268dd03199c09a30
|
2014-07-17 15:44:28 +02:00
|
|
|
SHA1 (patch-Modules_Platform_SCO__SV.cmake) = 3ed230b3a06ea693812db8f57bc73aebec12b99f
|
2012-11-15 20:31:54 +01:00
|
|
|
SHA1 (patch-Modules_Platform_SunOS.cmake) = 7a53ae3c902dd69ee22ef9fe0ae2a022d5284f16
|
2015-01-17 14:29:55 +01:00
|
|
|
SHA1 (patch-Source_cmELF.cxx) = 5eb9dc0b3567b5685596ddf0a03ca8e5c76e6f92
|
2014-07-18 12:00:18 +02:00
|
|
|
SHA1 (patch-Source_kwsys_SystemInformation.cxx) = e259da70601cf1b4641f253de3d4f3aaec5e68f6
|
2015-01-17 14:29:55 +01:00
|
|
|
SHA1 (patch-Source_kwsys_SystemTools.cxx) = 634348b9bc8ccf8c72f23837baa6ba0bcacf5961
|
2012-01-08 18:44:23 +01:00
|
|
|
SHA1 (patch-Utilities_KWIML_CMakeLists.txt) = 4e8cef0eab2ad8cb27cd7076e077bb5e7425a95c
|
2015-06-12 20:42:25 +02:00
|
|
|
SHA1 (patch-Utilities_cmjsoncpp_src_lib__json_json__writer.cpp) = 693873cad588dd7e0233d5eeabace18c4f66e734
|
Changes 3.2.1:
* CMake learned to support unicode characters *encoded as UTF-8* on
Windows. This was already supported on platforms whose system APIs
accept UTF-8 encoded strings. Unicode characters may now be used in
CMake code, paths to source files, configured files such as ".h.in"
files, and other files read and written by CMake. Note that because
CMake interoperates with many other tools, there may still be some
limitations when using certain unicode characters.
* The "Compile Features" functionality is now aware of features
supported by more compilers, including:
* Apple Clang ("AppleClang") for Xcode versions 4.4 though 6.1.
* GNU compiler versions 4.4 through 5.0 on UNIX and Apple ("GNU").
* Microsoft Visual Studio ("MSVC") for versions 2010 through 2015.
* Oracle SolarisStudio ("SunPro") version 12.4.
* The "add_custom_command()" and "add_custom_target()" commands
learned a new "BYPRODUCTS" option to specify files produced as side
effects of the custom commands. These are not outputs because they
do not always have to be newer than inputs.
* The "file(GENERATE)" command can now generate files which are used
as source files for buildsystem targets. Generated files
automatically get their "GENERATED" property set to "TRUE".
Deprecated and Removed Features:
* Files written in the "cmake-language(7)", such as "CMakeLists.txt"
or "*.cmake" files, are now expected to be encoded as UTF-8. If
files are already ASCII, they will be compatible. If files were in
a different encoding, including Latin 1, they will need to be
converted.
* The "FindOpenGL" module no longer explicitly searches for any
dependency on X11 libraries with the "FindX11" module. Such
dependencies should not need to be explicit. Applications using X11
APIs themselves should find and link to X11 libraries explicitly.
2015-04-07 22:53:48 +02:00
|
|
|
SHA1 (patch-aa) = bab24334e025b7c1bf7caa2e69d6a439cc421ea9
|
2015-01-17 14:29:55 +01:00
|
|
|
SHA1 (patch-ab) = d1b39bdcd654f2a4fc63463cd20de656cce3cf8f
|
|
|
|
SHA1 (patch-ac) = b5cedc6a2354beaf08e06d416c150154a7dc1f05
|