head 1.2; access; symbols pkgsrc-2026Q1:1.2.0.46 pkgsrc-2026Q1-base:1.2 pkgsrc-2025Q4:1.2.0.44 pkgsrc-2025Q4-base:1.2 pkgsrc-2025Q3:1.2.0.42 pkgsrc-2025Q3-base:1.2 pkgsrc-2025Q2:1.2.0.40 pkgsrc-2025Q2-base:1.2 pkgsrc-2025Q1:1.2.0.38 pkgsrc-2025Q1-base:1.2 pkgsrc-2024Q4:1.2.0.36 pkgsrc-2024Q4-base:1.2 pkgsrc-2024Q3:1.2.0.34 pkgsrc-2024Q3-base:1.2 pkgsrc-2024Q2:1.2.0.32 pkgsrc-2024Q2-base:1.2 pkgsrc-2024Q1:1.2.0.30 pkgsrc-2024Q1-base:1.2 pkgsrc-2023Q4:1.2.0.28 pkgsrc-2023Q4-base:1.2 pkgsrc-2023Q3:1.2.0.26 pkgsrc-2023Q3-base:1.2 pkgsrc-2023Q2:1.2.0.24 pkgsrc-2023Q2-base:1.2 pkgsrc-2023Q1:1.2.0.22 pkgsrc-2023Q1-base:1.2 pkgsrc-2022Q4:1.2.0.20 pkgsrc-2022Q4-base:1.2 pkgsrc-2022Q3:1.2.0.18 pkgsrc-2022Q3-base:1.2 pkgsrc-2022Q2:1.2.0.16 pkgsrc-2022Q2-base:1.2 pkgsrc-2022Q1:1.2.0.14 pkgsrc-2022Q1-base:1.2 pkgsrc-2021Q4:1.2.0.12 pkgsrc-2021Q4-base:1.2 pkgsrc-2021Q3:1.2.0.10 pkgsrc-2021Q3-base:1.2 pkgsrc-2021Q2:1.2.0.8 pkgsrc-2021Q2-base:1.2 pkgsrc-2021Q1:1.2.0.6 pkgsrc-2021Q1-base:1.2 pkgsrc-2020Q4:1.2.0.4 pkgsrc-2020Q4-base:1.2 pkgsrc-2020Q3:1.2.0.2 pkgsrc-2020Q3-base:1.2 pkgsrc-2020Q2:1.1.0.22 pkgsrc-2020Q2-base:1.1 pkgsrc-2020Q1:1.1.0.2 pkgsrc-2020Q1-base:1.1 pkgsrc-2019Q4:1.1.0.24 pkgsrc-2019Q4-base:1.1 pkgsrc-2019Q3:1.1.0.20 pkgsrc-2019Q3-base:1.1 pkgsrc-2019Q2:1.1.0.18 pkgsrc-2019Q2-base:1.1 pkgsrc-2019Q1:1.1.0.16 pkgsrc-2019Q1-base:1.1 pkgsrc-2018Q4:1.1.0.14 pkgsrc-2018Q4-base:1.1 pkgsrc-2018Q3:1.1.0.12 pkgsrc-2018Q3-base:1.1 pkgsrc-2018Q2:1.1.0.10 pkgsrc-2018Q2-base:1.1 pkgsrc-2018Q1:1.1.0.8 pkgsrc-2018Q1-base:1.1 pkgsrc-2017Q4:1.1.0.6 pkgsrc-2017Q4-base:1.1 pkgsrc-2017Q3:1.1.0.4 pkgsrc-2017Q3-base:1.1; locks; strict; comment @# @; 1.2 date 2020.07.31.09.02.31; author wiz; state Exp; branches; next 1.1; commitid QLBAoNvMZYTcbdiC; 1.1 date 2017.07.19.17.44.34; author adam; state Exp; branches; next ; commitid NExfkGAyFXRZFRZz; desc @@ 1.2 log @cmake: update to 3.18.1. Some of the more significant changes in CMake 3.18 are: * The “CUDA” language can now be compiled using Clang on non-Windows platforms. Separable compilation is not yet supported on any platform. * “cmake(1)” gained support for profiling of CMake scripts through the parameters “–profiling-output” and “–profiling-format”. * The “add_library()” and “add_executable()” commands learned to create Alias Targets referencing non-“GLOBAL” Imported Targets. * The “cmake_language()” command was added for meta-operations on scripted or built-in commands, starting with a mode to “CALL” other commands, and “EVAL CODE” to inplace evaluate a CMake script. * The “file(CONFIGURE)” subcommand was created in order to replicate the “configure_file()” functionality without resorting to a pre- existing file on disk as input. The content is instead passed as a string. * The “find_program()”, “find_library()”, “find_path()” and “find_file()” commands gained a new “REQUIRED” option that will stop processing with an error message if nothing is found. * A “CMAKE_CUDA_ARCHITECTURES” variable was added to specify CUDA output architectures. Users are encouraged to use this instead of specifying options manually, as this approach is compiler-agnostic. The variable is initialized automatically when “CMAKE_CUDA_COMPILER_ID” is “NVIDIA”. The variable is used to initialize the new “CUDA_ARCHITECTURES” target property. See policy “CMP0104”. * The “UNITY_BUILD_MODE” target property was added to tell generators which algorithm (“BATCH”, “GROUP”) to use for grouping included source files. * The “CheckLinkerFlag” module has been added to provide a facility to check validity of link flags. * The “$” and “$” “generator expressions” were added to manage device and host link steps. * The “$” and “$” “generator expressions” were added. * “ctest(1)” gained a new “CTEST_RESOURCE_SPEC_FILE” variable, which can be used to specify a resource specification file. * “ccmake(1)” learned to read a “CCMAKE_COLORS” environment variable to customize colors. * On Windows, the “Ninja” and “Ninja Multi-Config” generators, when a compiler is not explicitly specified, now select the first compiler (of any name) found in directories listed by the “PATH” environment variable. @ text @$NetBSD: patch-Modules_Platform_UnixPaths.cmake,v 1.1 2017/07/19 17:44:34 adam Exp $ Patch in pkgsrc paths for finding stuff. --- Modules/Platform/UnixPaths.cmake.orig 2020-07-15 11:19:20.000000000 +0000 +++ Modules/Platform/UnixPaths.cmake @@@@ -27,7 +27,7 @@@@ get_filename_component(_CMAKE_INSTALL_DI # synchronized list(APPEND CMAKE_SYSTEM_PREFIX_PATH # Standard - /usr/local /usr / + @@LOCALBASE@@ /usr/local /usr / # CMake install location "${_CMAKE_INSTALL_DIR}" @@@@ -47,20 +47,20 @@@@ endif() # Non "standard" but common install prefixes list(APPEND CMAKE_SYSTEM_PREFIX_PATH - /usr/X11R6 - /usr/pkg + @@X11BASE@@ + @@LOCALBASE@@ /opt ) # List common include file locations not under the common prefixes. list(APPEND CMAKE_SYSTEM_INCLUDE_PATH # X11 - /usr/include/X11 + @@X11BASE@@/include ) list(APPEND CMAKE_SYSTEM_LIBRARY_PATH # X11 - /usr/lib/X11 + @@X11BASE@@/lib ) list(APPEND CMAKE_PLATFORM_IMPLICIT_LINK_DIRECTORIES @ 1.1 log @3.9.0: * The “Visual Studio 14 2015” generator has been taught about a change to the “v140” toolset made by a VS 2015 update. VS changed the set of values it understands for the “GenerateDebugInformation” linker setting that produces the “-DEBUG” linker flag variants. * “CUDA” is now supported by the Visual Studio Generators for VS 2010 and above. This complements the existing support by the Makefile Generators and the “Ninja” generator. CUDA 8.0.61 or higher is recommended due to known bugs in the VS integration by earlier versions. * CMake is now aware of the “C++ standards” and “C standards” and their associated meta-features for the following “compiler ids”: “Cray”, “PGI”, and “XL”. * The “add_library()” command “IMPORTED” option learned to support Object Libraries. * All “find_” commands now have a “PACKAGE_ROOT” search path group that is first in the search heuristics. If a “find_” command is called from inside a find module, then the CMake variable and environment variable named “_ROOT” are used as prefixes and are the first set of paths to be searched. * The “install(TARGETS)” command learned a new “OBJECTS” option to specify where to install Object Libraries. * The “install(EXPORT)” command learned how to export Object Libraries. * A “BUILD_WITH_INSTALL_NAME_DIR” target property and corresponding “CMAKE_BUILD_WITH_INSTALL_NAME_DIR” variable were added to control whether to use the “INSTALL_NAME_DIR” target property value for binaries in the build tree. This is for macOS “install_name” as “BUILD_WITH_INSTALL_RPATH” is for “RPATH”. * A “CUDA_PTX_COMPILATION” target property was added to Object Libraries to support compiling to “.ptx” files instead of host object files. * A new “GoogleTest” module was added to provide the “gtest_add_tests()” function independently of the “FindGTest” module. The function was also updated to support keyword arguments, with functionality expanded to allow a test name prefix and suffix to be specified, the dependency on the source files to be optional and the list of discovered test cases to be returned to the caller. * The “Ninja” generator has loosened the dependencies of object compilation. Object compilation now depends only on custom targets and custom commands associated with libraries on which the object’s target depends and no longer depends on the libraries themselves. Source files in dependent targets may now compile without waiting for their targets’ dependencies to link. * Interprocedural optimization (IPO) is now supported for GNU and Clang compilers using link time optimization (LTO) flags. See the “INTERPROCEDURAL_OPTIMIZATION” target property and “CheckIPOSupported” module. * The “TARGET_OBJECTS” “generator expression” is now supported by the “add_custom_command()” and “file(GENERATE)” commands. @ text @d1 1 a1 1 $NetBSD$ d5 1 a5 1 --- Modules/Platform/UnixPaths.cmake.orig 2017-07-18 15:22:54.000000000 +0000 d7 2 a8 2 @@@@ -23,7 +23,7 @@@@ get_filename_component(_CMAKE_INSTALL_DI # search types. d16 1 a16 1 @@@@ -43,20 +43,20 @@@@ endif() @