| /src/contrib/libfido2/windows/ |
| H A D | build.ps1 | 48 $CMake = $(Get-Command cmake -ErrorAction Ignore | ` variable
50 if ([string]::IsNullOrEmpty($CMake)) { variable
51 $CMake = $CMakePath variable
53 if (-Not (Test-Path $CMake)) { variable
54 throw "Unable to find CMake at $CMake" variable
89 Write-Host "CMake: $CMake" variable
145 & $CMake ..\..\..\${LIBRESSL} -A "${Arch}" ` variable
151 & $CMake --build . --config ${Config} --verbose; ExitOnError variable
152 & $CMake --build . --config ${Config} --target install --verbose; ` variable
163 & $CMake ..\..\..\${LIBCBOR} -A "${Arch}" ` variable
[all …]
|
| /src/contrib/expat/ |
| H A D | Changes | 33 !! - smart ideas on fixing the Autotools CMake files generation issue !!
81 #1039 CI|FreeBSD: Do not install CMake meta-package
129 #1008 #1017 Autotools|macOS: Sync CMake templates with CMake 3.31
130 #1007 CMake: Drop support for CMake <3.15
131 #1004 CMake: Fix off_t detection for -Werror
132 #1007 CMake|Windows: Fix -DEXPAT_MSVC_STATIC_CRT=ON
224 #935 #937 Autotools: Make generated CMake files look for
226 #925 Autotools: Sync CMake templates with CMake 3.29
227 #945 #962 #966 CMake: Drop support for CMake <3.13
228 #942 CMake: Small fuzzing related improvements
[all …]
|
| H A D | README.md | 45 ## Using libexpat in your CMake-Based Project
47 There are three documented ways of using libexpat with CMake:
51 This approach leverages CMake's own [module `FindEXPAT`](https://cmake.org/cmake/help/latest/module…
73 - libexpat >=2.2.8 where packaging uses the CMake build system
99 This approach — as demonstrated below — requires CMake >=3.18 for both the
246 ### b) Building with CMake
248 The CMake build system is still *experimental* and may replace the primary
254 For an idea of the available (non-advanced) options for building with CMake:
|
| H A D | FREEBSD-Xlist | 11 CMake*
|
| /src/contrib/libpcap/doc/ |
| H A D | README.solaris.md | 11 * CMake 4.0.3 works.
17 * CMake 3.23.1 works.
23 * CMake 3.21.1 works.
41 * CMake 3.24.0 works.
47 * CMake 3.21.0 works.
53 * CMake 3.14.3 works.
60 * CMake 3.14.3 works.
|
| H A D | README.windows.md | 69 ### CMake ### subsection
74 It does provide files for CMake, which is a cross-platform tool that
79 Visual Studio 2015 does not provide CMake; an installer can be
82 When you run the installer, you should choose to add CMake to the system
85 Visual Studio 2017, 2019, and 2022 provide CMake, so you will not need
86 to install CMake if you have installed one of those versions of Visual
87 Studio or later. They include built-in support for CMake-based projects
91 For Visual Studio 2017, make sure "Visual C++ tools for CMake" is
92 installed; for Visual Studio 2019 and 2022, make sure "C++ CMake tools
95 CMake can also be installed as the Chocolatey package `cmake`:
[all …]
|
| /src/contrib/libpcap/cmake/Modules/ |
| H A D | Finddpdk.cmake | 59 # This depends on CMake support for "imported targets",
60 # which are not supported until CMake 3.19.
62 # Ubuntu 20.04 provides CMake 3.16.3, so we are *NOT*
63 # going to require CMake 3.19. If you want to use
66 # provide CMake, provide 3.19 or later.
71 # at least, do it that way on older versions of CMake.
81 # This is *NOT* the case for CMake; not only do you need
82 # CMake in order to build a package using CMake, you need
84 # CMake files use.
86 # Please keep this in mind when changing any CMake files,
[all …]
|
| H A D | FindAirPcap.cmake | 24 # Alternatively, AirPcap_ROOT may also be set from the CMake command
35 # The only way to *FORCE* CMake to look in the Lib/x64 directory
39 # In newer versions of CMake, CMAKE_LIBRARY_ARCHITECTURE is set according to
|
| /src/contrib/googletest/docs/ |
| H A D | quickstart-cmake.md | 1 # Quickstart: Building with CMake
3 This tutorial aims to get you up and running with GoogleTest using CMake. If
14 * [CMake](https://cmake.org/) and a compatible build tool for building the
19 [CMake Generators](https://cmake.org/cmake/help/latest/manual/cmake-generators.7.html)
25 If you don't already have CMake installed, see the
26 [CMake installation guide](https://cmake.org/install).
34 CMake uses a file named `CMakeLists.txt` to configure the build system for a
45 GoogleTest. There are many ways to express dependencies in the CMake ecosystem;
47 [`FetchContent` CMake module](https://cmake.org/cmake/help/latest/module/FetchContent.html).
75 [CMake Tutorial](https://cmake.org/cmake/help/latest/guide/tutorial/index.html).
[all …]
|
| /src/contrib/googletest/googletest/ |
| H A D | README.md | 9 ### Build with CMake
11 GoogleTest comes with a CMake build script
14 If you don't have CMake installed already, you can download it for free from
17 CMake works by generating native makefiles or build projects that can be used in
19 standalone project or it can be incorporated into an existing CMake build for
22 #### Standalone CMake Project argument
57 #### Incorporating Into An Existing CMake Project argument
59 If you want to use GoogleTest in a project which already uses CMake, the easiest
68 the main build and adding it using CMake's `add_subdirectory()` command. This
84 * Use CMake to download GoogleTest as part of the build's configure step. This
[all …]
|
| H A D | CMakeLists.txt | 2 # Note: CMake support is community-based. The maintainers do not use CMake
5 # CMake build script for Google Test.
42 # CMake files in this project can refer to the root source directory
59 # BUILD_SHARED_LIBS is a standard CMake variable, but we declare it here to
89 # Create the CMake package file descriptors.
|
| /src/contrib/libevent/ |
| H A D | README.md | 23 ## CMake (General)
26 The following Libevent specific CMake variables are as follows (the values being
34 # Installation directory for CMake files
70 # on the the cross compilation target to verify that it works. See CMake
78 ## CMake (Windows)
80 Install CMake: <https://www.cmake.org>
87 ## CMake (Unix)
137 ## CMake (Windows)
140 environment for Libevent; the CMake instructions here are new and
141 experimental, though they _should_ be solid. We hope that CMake will
[all …]
|
| /src/contrib/ntp/sntp/libevent/ |
| H A D | README.md | 23 ## CMake (General)
26 The following Libevent specific CMake variables are as follows (the values being
34 # Installation directory for CMake files
70 # on the the cross compilation target to verify that it works. See CMake
78 ## CMake (Windows)
80 Install CMake: <https://www.cmake.org>
87 ## CMake (Unix)
137 ## CMake (Windows)
140 environment for Libevent; the CMake instructions here are new and
141 experimental, though they _should_ be solid. We hope that CMake will
[all …]
|
| /src/contrib/libevent/cmake/ |
| H A D | Copyright.txt | 1 CMake - Cross Platform Makefile Generator
37 CMake in source and binary form. Some source files contain additional
39 for details. Third-party software packages supplied with CMake under
45 CMake was initially developed by Kitware with the following sponsorship:
|
| /src/contrib/ntp/sntp/libevent/cmake/ |
| H A D | Copyright.txt | 1 CMake - Cross Platform Makefile Generator
37 CMake in source and binary form. Some source files contain additional
39 for details. Third-party software packages supplied with CMake under
45 CMake was initially developed by Kitware with the following sponsorship:
|
| /src/contrib/nvi/ |
| H A D | INSTALL.md | 7 - CMake >= 3.17;
19 …CMake build system generator. By specifying "Ninja Multi-Config" as the build system to generate, …
|
| /src/crypto/openssl/exporters/cmake/ |
| H A D | OpenSSLConfig.cmake.in | 27 # Unixifying of paths, because that's what CMake understands.
86 # since before CMake 3.0
92 # $OpenSSL::safe::installdata::PREFIX[0], have CMake figure out the parent directory.
115 # available. The best course of action is to simply return and leave it to CMake to
167 # Directories and names compatible with CMake's FindOpenSSL.cmake
202 # Directories and names compatible with CMake's FindOpenSSL.cmake
221 # Directories and names compatible with CMake's FindOpenSSL.cmake
|
| /src/contrib/llvm-project/compiler-rt/lib/memprof/ |
| H A D | README.txt | 14 MemProf runtime can only be built by CMake. You can run MemProf tests
15 from the root of your CMake build tree:
|
| /src/contrib/googletest/googlemock/ |
| H A D | CMakeLists.txt | 2 # Note: CMake support is community-based. The maintainers do not use CMake
5 # CMake build script for Google Mock.
35 # CMake files in this project can refer to the root source directory
46 # Instructs CMake to process Google Test's CMakeLists.txt and add its
55 # BUILD_SHARED_LIBS is a standard CMake variable, but we declare it here to
|
| /src/contrib/googletest/ |
| H A D | CMakeLists.txt | 1 # Note: CMake support is community-based. The maintainers do not use CMake
|
| /src/contrib/llvm-project/compiler-rt/lib/asan/ |
| H A D | README.txt | 20 ASan runtime can only be built by CMake. You can run ASan tests
21 from the root of your CMake build tree:
|
| /src/contrib/libpcap/ |
| H A D | INSTALL.md | 3 with CMake and any build system supported by CMake.
34 To build libpcap with CMake and the build system of your choice, from
37 * Create a build directory into which CMake will put the build files it
38 generates; CMake does not work as well with builds done in the source
43 * Change to the build directory and run CMake with the path from the
45 can be used to select the CMake "generator" appropriate for the build
53 An `uninstall` target is supported with both `./configure` and CMake.
67 or CMake says:
82 CMake, although the circumstances where this works are limited. One
84 type in the case where the configure or CMake scripts fails to detect
[all …]
|
| /src/contrib/googletest/googletest/cmake/ |
| H A D | internal_utils.cmake | 15 # Tweaks CMake's default compiler/linker settings to suit Google Test's needs.
21 # For MSVC and Clang, CMake sets certain flags to defaults we want to
23 # This replacement code is taken from sample in the CMake Wiki at
36 # on CRT DLLs being available. CMake always defaults to using shared
74 # Newlines inside flags variables break CMake's NMake generator.
126 # CMake 2.8 changes Visual Age's compiler ID to "XL".
292 # Make the Python import path consistent between Bazel and CMake.
|
| /src/contrib/xz/ |
| H A D | ChangeLog | 24 CMake: Bump maximum policy version to 4.2
35 tuklib_integer/CMake: Log a message about unaligned access check
44 tuklib_integer/CMake: Don't run unaligned access checks unnecessarily
61 CMake >= 4.1 sets CMAKE_<LANG>_COMPILER_ARCHITECTURE_ID on many
63 variable when available. On older CMake versions CMAKE_SYSTEM_PROCESSOR
66 With old CMake versions, checking CMAKE_C_COMPILER_ARCHITECTURE_ID
225 CMake: Autodetect unaligned access support on LoongArch
227 This still relies on CMAKE_SYSTEM_PROCESSOR. CMake 4.1 added more
1017 CMake: With symbol versioning, try to pass --undefined-version to linker
1042 CMake: Fix comments
[all …]
|
| /src/contrib/tcpdump/ |
| H A D | CMakeLists.txt | 11 # if this is a version of CMake less than 3.5, require only
12 # 2.8.12, just in case somebody is configuring with CMake
14 # version supplies an older version of CMake;
17 # 3.5, just in case somebody is configuring with CMake
19 # version supplies an older version of CMake;
22 # that support for versions of CMake lower than 3.10 is
50 # However, by default, CMake adds a rule to the install CMake script
51 # a CMake command (using an undocumented subcommand of file()) that
108 # CMake will try to determine the sizes of some data types, including
112 # At least as of CMake 2.8.6, it does so by checking the size of
[all …]
|