/freebsd/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). 51 ```cmake [all …]
|
H A D | pkgconfig.md | 17 ### CMake subsection 19 Using `pkg-config` in CMake is fairly easy: 21 ```cmake 47 tutorial and you try to run `cmake`. It is very possible that you get a failure 52 CMake Error at /usr/share/cmake/Modules/FindPkgConfig.cmake:640 (message): 75 mkdir build && cmake -DCMAKE_INSTALL_PREFIX=/usr ..
|
/freebsd/contrib/ntp/sntp/libevent/ |
H A D | Makefile.am | 112 cmake/AddCompilerFlags.cmake \ 113 cmake/AddEventLibrary.cmake \ 114 cmake/CheckConstExists.cmake \ 115 cmake/CheckFileOffsetBits.c \ 116 cmake/CheckFileOffsetBits.cmake \ 117 cmake/CheckFunctionKeywords.cmake \ 118 cmake/CheckPrototypeDefinition.c.in \ 119 cmake/CheckPrototypeDefinition.cmake \ 120 cmake/CheckWorkingKqueue.cmake \ 121 cmake/CodeCoverage.cmake \ [all …]
|
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 35 EVENT_INSTALL_CMAKE_DIR:PATH=lib/cmake/libevent 70 # on the the cross compilation target to verify that it works. See CMake 75 __More variables can be found by running `cmake -LAH <sourcedir_path>`__ 78 ## CMake (Windows) 80 Install CMake: <https://www.cmake.org> 84 …$ cmake -G "Visual Studio 10" .. # Or whatever generator you want to use cmake --help for a list. 87 ## CMake (Unix) [all …]
|
/freebsd/contrib/libevent/ |
H A D | Makefile.am | 112 cmake/AddCompilerFlags.cmake \ 113 cmake/AddEventLibrary.cmake \ 114 cmake/CheckConstExists.cmake \ 115 cmake/CheckFileOffsetBits.c \ 116 cmake/CheckFileOffsetBits.cmake \ 117 cmake/CheckFunctionKeywords.cmake \ 118 cmake/CheckPrototypeDefinition.c.in \ 119 cmake/CheckPrototypeDefinition.cmake \ 120 cmake/CheckWorkingKqueue.cmake \ 121 cmake/CodeCoverage.cmake \ [all …]
|
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 35 EVENT_INSTALL_CMAKE_DIR:PATH=lib/cmake/libevent 70 # on the the cross compilation target to verify that it works. See CMake 75 __More variables can be found by running `cmake -LAH <sourcedir_path>`__ 78 ## CMake (Windows) 80 Install CMake: <https://www.cmake.org> 84 …$ cmake -G "Visual Studio 10" .. # Or whatever generator you want to use cmake --help for a list. 87 ## CMake (Unix) [all …]
|
/freebsd/contrib/libyaml/ |
H A D | CMakeLists.txt | 33 set(INSTALL_CMAKE_DIR cmake) 52 cmake/config.h.in 107 # Generate 'yamlConfig.cmake', 'yamlConfigVersion.cmake' and 'yamlTargets.cmake' 111 # Configure 'yamlConfig.cmake' for a build tree 113 set(config_file ${PROJECT_BINARY_DIR}/yamlConfig.cmake) 115 yamlConfig.cmake.in 122 # Configure 'yamlTargets.cmake' for a build tree 124 FILE ${PROJECT_BINARY_DIR}/yamlTargets.cmake 127 # Configure and install 'yamlConfig.cmake' for an install tree 129 set(install_config_file ${PROJECT_BINARY_DIR}${CMAKE_FILES_DIRECTORY}/yamlConfig.cmake ) [all …]
|
/freebsd/contrib/expat/ |
H A D | Makefile.am | 62 cmake/autotools/expat.cmake 65 cmake/autotools/expat-config-version.cmake \ 66 cmake/autotools/expat-noconfig.cmake \ 67 cmake/expat-config.cmake 69 cmakedir = $(libdir)/cmake/expat-@PACKAGE_VERSION@ directory 73 cmake/autotools/expat-noconfig__linux.cmake.in \ 74 cmake/autotools/expat-noconfig__macos.cmake.in \ 75 cmake/autotools/expat-noconfig__windows.cmake.in \ 76 cmake/autotools/expat-package-init.cmake \ 77 cmake/mingw-toolchain.cmake \ [all …]
|
H A D | Changes | 29 !! - smart ideas on fixing the Autotools CMake files generation issue !! 93 #935 #937 Autotools: Make generated CMake files look for 95 #925 Autotools: Sync CMake templates with CMake 3.29 96 #945 #962 #966 CMake: Drop support for CMake <3.13 97 #942 CMake: Small fuzzing related improvements 103 for CMake 159 #903 CMake: Add alias target "expat::expat" 160 #905 docs: Document use via CMake >=3.18 with FetchContent 206 #851 #879 Autotools: Sync CMake templates with CMake 3.28 211 #856 Autotools|CMake: Fix main() to main(void) [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… 55 ```cmake 73 - libexpat >=2.2.8 where packaging uses the CMake build system 83 ```cmake 99 This approach — as demonstrated below — requires CMake >=3.18 for both the 100 [`FetchContent` module](https://cmake.org/cmake/help/latest/module/FetchContent.html) 113 ```cmake 246 ### b) Building with CMake [all …]
|
H A D | Makefile.in | 153 CONFIG_CLEAN_FILES = expat.pc cmake/expat-config.cmake \ 154 cmake/autotools/expat-config-version.cmake \ 155 cmake/autotools/expat-noconfig.cmake run.sh 243 $(top_srcdir)/cmake/autotools/expat-config-version.cmake.in \ 244 $(top_srcdir)/cmake/expat-config.cmake.in \ 462 cmake/autotools/expat.cmake 465 cmake/autotools/expat-config-version.cmake \ 466 cmake/autotools/expat-noconfig.cmake \ 467 cmake/expat-config.cmake 469 cmakedir = $(libdir)/cmake/expat-@PACKAGE_VERSION@ [all …]
|
H A D | configure.ac | 379 dnl Configure CMake file templates 403 PACKAGE_INIT="${srcdir}"/cmake/autotools/expat-package-init.cmake 434 dnl Emulate the use of CMAKE_SHARED_LIBRARY_PREFIX under CMake 443 [darwin*], [CMAKE_NOCONFIG_SOURCE=cmake/autotools/expat-noconfig__macos.cmake.in], 444 [mingw*|cygwin*], [CMAKE_NOCONFIG_SOURCE=cmake/autotools/expat-noconfig__windows.cmake.in], 445 [CMAKE_NOCONFIG_SOURCE=cmake/autotools/expat-noconfig__linux.cmake.in]) 448 [cmake/expat-config.cmake] 449 [cmake/autotools/expat-config-version.cmake] 450 [cmake/autotools/expat-noconfig.cmake:${CMAKE_NOCONFIG_SOURCE}]
|
/freebsd/contrib/libpcap/doc/ |
H A D | README.windows.md | 74 ### CMake ### subsection 79 It does provide files for CMake, which is a cross-platform tool that 84 Visual Studio 2015 does not provide CMake; an installer can be 87 https://cmake.org/download/ 89 When you run the installer, you should choose to add CMake to the system 92 CMake can also be installed as the Chocolatey package "cmake": 94 choco install -y cmake 96 Visual Studio 2017 and later provide CMake, so you will not need to 97 install CMake if you have installed Visual Studio 2017 or later. They 98 include built-in support for CMake-based projects: [all …]
|
H A D | README.solaris.md | 11 * CMake 3.23.1 works. 17 * CMake 3.21.1 works. 27 developer/build/cmake 36 * CMake 3.21.0 works. 44 * CMake 3.14.3 works. 51 * CMake 3.14.3 works. 57 * CMake 2.8.9 does not work.
|
/freebsd/contrib/libcbor/.circleci/ |
H A D | config.yml | 8 - run: sudo NEEDRESTART_MODE=l apt-get install -y cmake ${TOOLCHAIN_PACKAGES} 13 cmake -DWITH_TESTS=ON \ 23 cmake -DWITH_TESTS=ON \ 103 - run: sudo NEEDRESTART_MODE=l apt-get install -y cmake gcc-multilib g++-multilib libc6-dev-i386 108 cmake ~/cmocka -DCMAKE_TOOLCHAIN_FILE=~/cmocka/cmake/Toolchain-cross-m32.cmake && 113 cmake -DWITH_TESTS=ON \ 115 -DCMAKE_TOOLCHAIN_FILE=~/cmocka/cmake/Toolchain-cross-m32.cmake \ [all...] |
/freebsd/contrib/libfido2/windows/ |
H A D | build.ps1 | 7 [string]$CMakePath = "C:\Program Files\CMake\bin\cmake.exe", 47 # Find CMake. 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" global() variable 145 & $CMake ..\..\..\${LIBRESSL} -A "${Arch}" ` global() variable 151 & $CMake --build . --config ${Config} --verbose; ExitOnError global() variable 152 & $CMake --build . --config ${Config} --target install --verbose; ` global() variable 163 & $CMake ..\..\..\${LIBCBOR} -A "${Arch}" ` global() variable 170 & $CMake --build . --config ${Config} --verbose; ExitOnError global() variable 171 & $CMake --build . --config ${Config} --target install --verbose; ` global() variable 182 & $CMake ..\..\..\${ZLIB} -A "${Arch}" ` global() variable 188 & $CMake --build . --config ${Config} --verbose; ExitOnError global() variable 189 & $CMake --build . --config ${Config} --target install --verbose; ` global() variable 210 & $CMake ..\..\.. -A "${Arch}" ` global() variable 227 & $CMake --build . --config ${Config} --verbose; ExitOnError global() variable 228 & $CMake --build . --config ${Config} --target regress --verbose; ` global() variable 230 & $CMake --build . --config ${Config} --target install --verbose; ` global() variable [all...] |
/freebsd/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 15 <https://cmake.org/>. 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 32 cmake .. # Generate native build scripts for GoogleTest. 39 cmake .. -DBUILD_GMOCK=OFF 57 #### Incorporating Into An Existing CMake Project argument [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. 30 include(cmake/hermetic_build.cmake OPTIONAL) 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 81 include(cmake/internal_utils.cmake) 83 config_compiler_and_linker() # Defined in internal_utils.cmake. 89 # Create the CMake package file descriptors. 94 set(cmake_files_install_dir "${CMAKE_INSTALL_LIBDIR}/cmake/${cmake_package_name}") 95 set(version_file "${generated_dir}/${cmake_package_name}ConfigVersion.cmake") [all …]
|
/freebsd/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 | 22 # AirPcap_ROOT to point cmake to the *root* of a directory with include and 24 # Alternatively, AirPcap_ROOT may also be set from the CMake command 25 # line or GUI (e.g cmake -DAirPcap_ROOT=C:\path\to\airpcap_sdk [...]) 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
|
/freebsd/sys/contrib/zstd/ |
H A D | appveyor.yml | 28 HOST: "cmake-visual" 88 - if [%HOST%]==[cmake-visual] ( 91 PUSHD build\cmake && 92 cmake -DBUILD_TESTING=ON . && 93 cmake --build . --config %CONFIGURATION% -j4 && 102 - if [%TEST%]==[cmake] ( 103 mkdir build\cmake\build && 104 cd build\cmake\build && 107 cmake -G "Visual Studio 14 2015 Win64" .. && 143 HOST: "cmake-visual" [all …]
|
/freebsd/contrib/googletest/ |
H A D | .gitignore | 4 cmake-build-debug/ 29 cmake-variants.yaml 53 # Ignore cmake generated directories and files. 55 CTestTestfile.cmake 57 cmake_install.cmake 59 googlemock/CTestTestfile.cmake 61 googlemock/cmake_install.cmake
|
H A D | CONTRIBUTING.md | 93 * [CMake](https://cmake.org/) v2.8.12 or newer 103 tests. For that you can use CMake: 108 cmake -Dgtest_build_tests=ON -Dgmock_build_tests=ON ${GTEST_REPO_DIR} 112 cmake command to be one of each 115 cmake -Dgtest_build_tests=ON ${GTEST_DIR} # sets up Google Test tests 116 cmake -Dgmock_build_tests=ON ${GMOCK_DIR} # sets up Google Mock tests 120 in Python. If the cmake command complains about not being able to find Python 125 cmake -DPYTHON_EXECUTABLE=path/to/python ...
|
/freebsd/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. 21 include("${gtest_dir}/cmake/hermetic_build.cmake" OPTIONAL) 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 65 config_compiler_and_linker() # from ${gtest_dir}/cmake/internal_utils.cmake 127 # or specifying the -Dgmock_build_tests=ON flag when running cmake.
|
/freebsd/contrib/libpcap/ |
H A D | INSTALL.md | 3 with CMake and any build system supported by CMake. 30 To build libpcap with CMake and the build system of your choice, from 33 * Create a build directory into which CMake will put the build files it 34 generates; CMake does not work as well with builds done in the source 39 * Change to the build directory and run CMake with the path from the 41 can be used to select the CMake "generator" appropriate for the build 49 An `uninstall` target is supported with both `./configure` and CMake. 63 or CMake says: 78 CMake, although the circumstances where this works are limited. One 80 type in the case where the configure or CMake scripts fails to detect [all …]
|