summaryrefslogtreecommitdiffstats
path: root/Help/module
Commit message (Collapse)AuthorAgeFilesLines
* Help: Improve documentation formatingBartosz Kosiorek2019-04-041-1/+2
|
* FindEnvModules: Provide a CMake interface to environment modulesChuck Atkins2019-03-181-0/+1
|
* FindOctave: Remove module pending further workBrad King2019-02-261-1/+0
| | | | | | | | | | | The `FindOctave` module added by commit 170bcb6fdc (FindOctave: Add module to find GNU octave, 2018-11-17, v3.14.0-rc1~283^2) has a few problems in its implementation that need to be worked out before the module can be included in a CMake release. These were missed during review. Remove the module for now. It can be restored later with a fresh review. Issue: #18991
* CheckFortranSourceRuns: Add module to check if Fortran code runsMichael Hirsch, Ph.D2019-01-101-0/+1
| | | | | Add a Fortran equivalent to the existing `Check{C,CXX}SourceRuns` modules.
* PIE link options: Update strategy to fix performance regressionMarc Chevrier2018-12-191-0/+1
| | | | Fixes: #18700
* FindOctave: Add module to find GNU octaveMichael Hirsch, Ph.D2018-12-061-0/+1
|
* Merge topic 'FindSQLite3-module'Brad King2018-11-071-0/+1
|\ | | | | | | | | | | | | fe40570608 FindSQLite3: Add module to find SQLite3 Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !2557
| * FindSQLite3: Add module to find SQLite3Chuck Atkins2018-11-061-0/+1
| |
* | Merge topic 'cpack-doc-gen-names'Brad King2018-11-063-3/+3
|\ \ | |/ |/| | | | | | | | | 12deb051b3 Help: Use correct CPack generator names Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !2563
| * Help: Use correct CPack generator namesCraig Scott2018-11-063-3/+3
| | | | | | | | | | | | | | | | | | | | CPack generator names were not used consistently throughout the documentation, resulting in ambiguity about what the correct name was for use with the `cpack -G` option. With the changes in this commit, the cpack-generators(7) page of the manual now shows the correct names and other help pages no longer use inconsistent or incorrect names.
* | FindFontconfig: Add module to find FontconfigFrederik Gladhorn2018-10-181-0/+1
| | | | | | | | This module is inspired by one from KDE's KWin.
* | FindLibinput: Add module to find libinputFrederik Gladhorn2018-10-111-0/+1
|/ | | | This module is inspired by one from KDE's KWin.
* Help: Add new section for CPack generatorsKyle Edwards2018-06-2112-12/+48
| | | | | | | | | | | | | | | | | | | | The documentation for CPack generators previously lived in their respective internal CMake modules. This setup was misleading, because it implied that you should include the modules in your own code, which is not the case. Moving the documentation into a separate section does a better job of hiding the internal modules, which are just an implementation detail. The generator documentation has also been modified to remove any references to the module name. The CPackIFW module is a special exception: since it has user-facing macros, the documentation for these macros has been kept in the module page, while all other documentation related to the IFW generator has been moved into the new section. To make it easier to find the new documentation, the old help pages for the CPack*.cmake modules have not been deleted, but have been replaced with a link to their respective help page in the new documentation section.
* FindODBC: Add module to search for ODBC libraryMateusz Loskot2018-05-221-0/+1
| | | | Add tests for FindODBC module.
* CPack: Add NuGet supportAlex Turbov2018-05-111-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | Create a CPack generator that uses `nuget.exe` to create packages: https://docs.microsoft.com/en-us/nuget/what-is-nuget NuGet packages could be easily produced from a `*.nuspec` file (running `nuget pack` in the directory w/ the spec file). The spec filename does not affect the result `*.nupkg` name -- only `id` and `version` elements of the spec are used (by NuGet). Some implementation details: * Minimize C++ code -- use CMake script do to the job. It just let the base class (`cmCPackGenerator`) to preinstall everything to a temp directory, render the spec file and run `nuget pack` in it, harvesting `*.nupkg` files...; * Ignore package name (and use default paths) prepared by the base class (only `CPACK_TEMPORARY_DIRECTORY` is important) -- final package filename is a responsibility of NuGet, so after generation just scan the temp directory for the result `*.nupkg` file(s) and update `packageFileNames` data-member of the generator; * The generator supports _all-in-one_ (default), _one-group-per-package_ and _one-component-per-package_ modes.
* FindPython*: New implementation for Python stuffMarc Chevrier2018-03-203-0/+3
| | | | Fixes: #16142
* FindIconv: Add the FindIconv module.Christian Pfeiffer2017-11-291-0/+1
| | | | | This module provides abstraction over the various ways POSIX platforms handle the iconv calls defined in POSIX.1-2001 and later versions.
* FetchContent: New module for populating content at configure timeCraig Scott2017-10-161-0/+1
|
* FindOpenACC: Add module to detect compiler support for OpenACCTin Huynh2017-09-221-0/+1
|
* FindPatch: Add module to find 'patch' command-line toolJean-Christophe Fillion-Robin2017-09-011-0/+1
|
* CPack-FreeBSD: add a generator for FreeBSD pkg(8)Adriaan de Groot2017-06-101-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Adds an option CPACK_ENABLE_FREEBSD_PKG to allow CPack to look for FreeBSD's libpkg / pkg(8). If this is set and the libpkg headers and library are found (which they will be, by default, on any FreeBSD system), then add a FreeBSD pkg(8) generator. The FreeBSD package tool pkg(8) uses tar.xz files (.txz) with two metadata files embedded (+MANIFEST and +COMPACT_MANIFEST). This introduces a bunch of FreeBSD-specific CPACK_FREEBSD_PACKAGE_* variables for filling in the metadata; the Debian generator does something similar. Documentation for the CPack CMake-script is styled after the Debian generator. Implementation notes: - Checks for libpkg -- the underlying implementation for pkg(8) -- and includes FreeBSD package-generation if building CMake on a UNIX host. Since libpkg can be used on BSDs, Linux and OSX, this potentially adds one more packaging format. In practice, this will only happen on FreeBSD and DragonflyBSD. - Copy-paste from cmCPackArchiveGenerator to special-case the metadata generation and to run around the internal archive generation: use libpkg instead. - Generating the metadata files is a little contrived. - Most of the validation logic for package settings is in CPackFreeBSD.cmake, as well as the code that tries to re-use packaging settings that may already be set up for Debian. - libpkg has its own notion of output filename, so we have another contrived bit of code that munges the output file list so that CPack can find the output. - Stick with C++98.
* CPack/Archive: per component filenames supportDomen Vrankar2017-05-161-0/+1
| | | | | | Support for setting archive packager specific per component filenames and monolithic package filenames.
* CheckIPOSupported: New module to check for compiler/cmake IPO supportRuslan Baratov2017-03-111-0/+1
|
* Merge topic 'csproj_add_free_source_tags'Brad King2017-03-021-0/+1
|\ | | | | | | | | | | | | 506207f9 VS: add test for VS_CSHARP_* source file property a202749c VS: add CSharpUtilities module 9588d0a2 VS: add VS_CSHARP_<tagname> sourcefile property
| * VS: add CSharpUtilities moduleMichael Stürmer2017-03-011-0/+1
| |
* | GoogleTest: Add module to contain gtest_add_tests independentlyBradley Lowekamp2017-02-071-0/+1
|/ | | | | | | | | | | | Extract the `gtest_add_tests` macro from `FindGTest` into a separate module. GTest or GoogleTest can be used by a project in a several different ways, including installed libraries in the system, from an ExternalProject, or adding the GTest source directory as a sub directory of the project. As not all of these uses are supported by the FindGTest module the useful `gtest_add_tests` macro is separated to easily enable reuse. Issue: #14151
* Add cpack_ifw_configure_file commandKonstantin Podsvirov2017-01-111-0/+1
|
* AndroidTestUtilities: Add module to help drive Android device testsSchuyler Kylstra2016-09-301-0/+1
| | | | | | Add a module to manage the data needed for the project tests. It will move the test data to the build directory and transfer necessary data to an Android device if that is enabled.
* FindICU: New moduleRoger Leigh2016-07-131-0/+1
|
* Merge topic 'add-FindVulkan'Brad King2016-06-081-0/+1
|\ | | | | | | | | adf4df28 Add FindVulkan.cmake.
| * Add FindVulkan.cmake.Matthäus G. Chajdas2016-06-081-0/+1
| | | | | | | | This adds FindVulkan with corresponding tests.
* | productbuild: Add new productbuild cpack generator.Clinton Stimpson2016-06-031-0/+1
|/ | | | This cpack generator basically replaces the obsolete PackageMaker generator.
* Add FindLTTngUST module to find LTTng-UST libraryPhilippe Proulx2016-03-071-0/+1
| | | | | | | Also detect the library version number. Provide results as variables and as an imported target, LTTng::UST. Signed-off-by: Philippe Proulx <eeppeliteloop@gmail.com>
* FindXalanC: New module to find the Apache Xalan-C++ libraryRoger Leigh2016-01-201-0/+1
|
* OS X: Add FindXCTest moduleGregor Jasny2015-03-231-0/+1
| | | | | | | Add a module to lookup XCTest Framework and xctest utility. It also provides APIs for creating 'xctest' targets. Signed-off-by: Gregor Jasny <gjasny@googlemail.com>
* Merge topic 'private-FindJsonCpp'Brad King2015-02-231-1/+0
|\ | | | | | | | | | | a41d621d bootstrap: Add --(no-)system-jsoncpp options a5768442 FindJsonCpp: Drop new module due to upstream jsoncpp providing package
| * FindJsonCpp: Drop new module due to upstream jsoncpp providing packageBrad King2015-02-201-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Since jsoncpp 0.7.0 (2014-11-20) the upstream may provide a CMake package configuration file such that find_package(jsoncpp) will find a jsoncppConfig.cmake file. In order to avoid conflicting with this (especially on case-insensitive filesystems), and since we always prefer projects to provide package config files (that they maintain), it is better to not provide FindJsonCpp publicly. Move FindJsonCpp into a private source directory that is not installed so that we can still use it for building CMake itself. Reported-by: Ryan Pavlik <ryan.pavlik@gmail.com>
* | CheckFortranCompilerFlag: Add module to check Fortran flag existenceNicolas Bock2015-02-051-0/+1
|/ | | | | | Copy the CheckCCompilerFlag module and replace 'C' with 'Fortran'. Also update the common patterns module to match some Fortran compiler messages.
* CTestCoverageCollectGCOV: Add module to run gcovBill Hoffman2015-01-221-0/+1
| | | | | | | Provide a function to run gcov and create a tarball of results. Since CDash tracks the md5sum of the files uploaded, use the --mtime option with "cmake -E tar" so that tar files could be created that would have the same md5sum with the same content.
* FindJsonCpp: Add module to find JsonCpp packageBrad King2015-01-191-0/+1
|
* FindGSL: Add module to find the GNU Scientific LibraryKelly Thompson2014-12-171-0/+1
|
* Merge topic 'xerces-rename'Brad King2014-12-052-1/+1
|\ | | | | | | | | 27141eed Modules: Rename FindXerces to FindXercesC
| * Modules: Rename FindXerces to FindXercesCBrad King2014-12-042-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The FindXerces module was added in commit v3.1.0-rc1~155^2 (FindXerces: New module to find Apache Xerces-C++, 2014-08-17). However, there are two implementations of Xerces, one in C++: http://xerces.apache.org/xerces-c/ and one in Java: http://xerces.apache.org/xerces-j/ Rename FindXerces to FindXercesC to clarify that it is about the C++ implementation. While at it, add the missing CMake 3.1 release note about this module. Suggested-by: Erik Sjölund <erik.sjolund@gmail.com>
* | FindIntl: New module to find Gettext libintlRoger Leigh2014-11-111-0/+1
|/ | | | | | | | | | | | | | | | Add support for Sun/Uniforum/GNU gettext libintl. This belongs in CMake rather than upstream because: * There are multiple upstreams (Sun, GNU). * It may or may not be in the glibc C library depending upon the platform and build options used. Although we already have a FindGettext module, that is for the tools. This module is for the library, and is independent because it's perfectly OK to use libintl without the gettext tools (and vice versa), and they might not all be found. Add cross references between the two modules in notes to make the relationship clearer.
* FindVTK: Drop this ancient compatibility moduleBrad King2014-10-021-1/+10
| | | | | | | The FindVTK module only existed to help find_package(VTK) calls work in old projects written to use "USE_VTK_FILE" instead of "VTK_USE_FILE". Drop it to allow find_package(VTK) calls to search for VTKConfig.cmake directly.
* FindITK: Drop this ancient compatibility moduleBrad King2014-10-021-1/+10
| | | | | | | The FindITK module only existed to help find_package(ITK) calls work in old projects written to use "USE_ITK_FILE" instead of "ITK_USE_FILE". Drop it to allow find_package(ITK) calls to search for ITKConfig.cmake directly.
* Merge topic 'FindXerces'Brad King2014-08-221-0/+1
|\ | | | | | | | | 20407006 FindXerces: New module to find Apache Xerces-C++
| * FindXerces: New module to find Apache Xerces-C++Roger Leigh2014-08-211-0/+1
| |
* | FindIce: New module to find ZeroC IceRoger Leigh2014-08-211-0/+1
|/ | | | | | | | | - autodetects Ice on all major platforms - allows building with all supported Visual Studio versions on Windows - autodetects the slice path on most platforms - separately detects the Ice programs, headers, slice files and libraries so that any Ice configuration or installation errors can be accurately reported, making diagnosis of Ice problems simpler
* Add CheckFortranSourceCompiles module (#14656)Brad King2014-08-181-0/+1
| | | | | | | Copy the CheckCSourceCompiles module and port it to Fortran. Extend the FortranOnly test to try using the new module. Suggested-by: Nicolas Bock <nicolasbock@gmail.com>
generated by cgit v0.12 at 2024-09-22 18:22:55 (GMT)