summaryrefslogtreecommitdiff
path: root/Modules/FindRuby.cmake
Commit message (Collapse)AuthorAgeFilesLines
* FindRuby: Simplify version matchingDiego Pino Garcia2022-06-301-46/+7
|
* FindRuby: evict non-matching binaries and keep scanning.Mihai Moldovan2022-01-311-1/+12
| | | | | | | | | | | | The possible executable names list always starts with a plain "ruby" binary, which is scanned for first. If that does exist (which satisfies find_program), but doesn't match the requested version, the executable will be dismissed by _RUBY_VALIDATE_INTERPRETER (which is sane), but searching also stops. Fix that by keeping the search going, removing items from the list as we go, until find_program returns a path that _RUBY_VALIDATE_INTERPRETER is happy with or the list is empty.
* FindRuby: add support for versions up to 3.1.Mihai Moldovan2022-01-311-6/+16
|
* FindRuby: Consider ruby names with full nodot version suffixesPedro Luis Castedo Cepeda2021-03-251-1/+1
|
* Help: Add `.. versionadded` directives to module docsNikita Nemkin2020-12-021-4/+8
| | | | Issue: #19715
* FindRuby: Consider more VS runtime suffix combinationsSilvio Traversaro2020-11-111-7/+13
| | | | | | | These are needed to find recent Ruby versions for builds using recent VS versions. Fixes: #21066
* FindRuby: Restore compatibility variable RUBY_VENDORLIB_DIRBrad King2020-10-271-0/+1
| | | | | | | | | | Since commit e672db628b (FindRuby: Rename variables to match case of module name, 2020-03-11, v3.18.0-rc1~546^2), the result variables named with the old `RUBY_` prefix are provided by compatibility code that maps from the new `Ruby_` prefix variables. This variable was accidentally left out. Fixes: #21369
* FindRuby: Add documentation for deprecated variablesDaniele E. Domenichelli2020-08-121-2/+13
| | | | | | | | | Since commit e672db628b (FindRuby: Rename variables to match case of module name, 2020-03-11, v3.18.0-rc1~546^2), the upper-case-prefixed variable names are for compatibility only but still exist. Put them back in the documentation. Issue: #21064
* FindRuby: Restore compatibility variable RUBY_INCLUDE_PATHBrad King2020-08-071-2/+1
| | | | | | | | | | | | Since commit e672db628b (FindRuby: Rename variables to match case of module name, 2020-03-11, v3.18.0-rc1~546^2), the result variables named with the old `RUBY_` prefix are provided by compatibility code that maps from the new `Ruby_` prefix variables. There is no `Ruby_INCLUDE_PATH` variable, so do not try to map it to `RUBY_INCLUDE_PATH`. The latter is provided by dedicated compatibility code left from before that transition. Fixes: #21064
* FindRuby: Add support for RVM installationsJulien Marrec2020-03-231-5/+93
|
* FindRuby: Validate Ruby_EXECUTABLE before accepting itJulien Marrec2020-03-231-0/+40
|
* FindRuby: Add support for versions up to 2.7Julien Marrec2020-03-171-30/+82
| | | | Fixes: #20370
* FindRuby: Update MSVC runtime library selectionBrad King2020-03-171-15/+4
| | | | | | | Use the `MSVC_TOOLSET_VERSION` variable computed by CMake to get the matching Ruby library name component. Inspired-by: Julien Marrec <julien.marrec@gmail.com>
* FindRuby: Remove extra whitespaceJulien Marrec2020-03-161-1/+1
|
* FindRuby: Include FPHSA closer to where it is usedBrad King2020-03-161-1/+1
|
* FindRuby: Provide Ruby_LIBRARIES result variableBrad King2020-03-161-2/+6
| | | | | The `cmake-developer(7)` manual documents that a plural non-cached name should be used for results.
* FindRuby: Fix compatibility with upper-case cache variablesBrad King2020-03-131-0/+16
| | | | | | In commit e672db628b (FindRuby: Rename variables to match case of module name, 2020-03-11) compatibility was provided for result variables but not for the cache entries that scripts might set.
* FindRuby: Fix name of Ruby_LIBRARY variableBrad King2020-03-131-5/+5
| | | | | Fix a typo in the variable name caused by commit e672db628b (FindRuby: Rename variables to match case of module name, 2020-03-11).
* FindRuby: Rename variables to match case of module nameJulien Marrec2020-03-111-157/+185
| | | | | | | | | | | | | | Use recommended case for variable names, i.e. matching name of the module as passed to `find_package`. For backwards compatibility, the upper case versions of both input and output variables are used and defined when appropriate. Skip this for the _FOUND variable because FPHSA already does it. This follows the approach from commit a7b09e7f43 (FindProtobuf: Rename variables to match case of module name, 2016-03-01, v3.6.0-rc1~273^2). Issue: #20370
* Modules: Consistently use 2 space indentationKitware Robot2019-05-141-156/+157
|
* Help: Convert remaining modules to block-style commentsKitware Robot2018-10-221-31/+32
|
* FindRuby: Add support for versions 2.2, 2.3, and 2.4Brad King2017-11-161-0/+18
| | | | | Author: J. Peter Mugaas (jpmugaas on gitlab.kitware.com) Fixes: #17475
* FindRuby: Fix match of '.' in version numbersBrad King2017-11-161-3/+3
| | | | | Escape `.` so that it is matched literally and not treated as a special match of any character by the regex.
* FindRuby: Use `MSVC_VERSION` instead of `MSVC##`Brad King2017-03-231-5/+5
|
* Simplify CMake per-source license noticesBrad King2016-09-271-14/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | Per-source copyright/license notice headers that spell out copyright holder names and years are hard to maintain and often out-of-date or plain wrong. Precise contributor information is already maintained automatically by the version control tool. Ultimately it is the receiver of a file who is responsible for determining its licensing status, and per-source notices are merely a convenience. Therefore it is simpler and more accurate for each source to have a generic notice of the license name and references to more detailed information on copyright holders and full license terms. Our `Copyright.txt` file now contains a list of Contributors whose names appeared source-level copyright notices. It also references version control history for more precise information. Therefore we no longer need to spell out the list of Contributors in each source file notice. Replace CMake per-source copyright/license notice headers with a short description of the license and links to `Copyright.txt` and online information available from "https://cmake.org/licensing". The online URL also handles cases of modules being copied out of our source into other projects, so we can drop our notices about replacing links with full license text. Run the `Utilities/Scripts/filter-notices.bash` script to perform the majority of the replacements mechanically. Manually fix up shebang lines and trailing newlines in a few files. Manually update the notices in a few files that the script does not handle.
* FindRuby: Fix finding 64-bit Ruby on WindowsMichael Smith2015-02-101-4/+9
| | | | | Ruby 2.0.0 and 2.1.5 have 64-bit binaries for Windows, with "x64-" prefix.
* Merge topic 'FindRuby-fix-version'Brad King2015-01-151-1/+1
|\ | | | | | | | | 802d0aa0 FindRuby: Fix output check in _RUBY_CONFIG_VAR
| * FindRuby: Fix output check in _RUBY_CONFIG_VAREvangelos Foutras2015-01-111-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Since commit v2.8.8~173^2 (FindRuby: clean up querying variables from Ruby, 2012-02-17) we query RbConfig::CONFIG first and, if the command fails or its output equates to a false constant, then fall back to querying Config::CONFIG. Due to the above, an error condition exists with Ruby 2.2.0; when querying RbConfig::CONFIG['TEENY'], the output of '0' will be discarded since it matches the false constant '0'. In previous versions this wasn't a problem, but Ruby 2.2 has completely removed Config::CONFIG. This causes RUBY_VERSION_PATCH to be set to an empty string and the Ruby version to be detected as '2.2.' (instead of '2.2.0'). Fix the output check to explicitly look for an empty string before using the fallback query method. (Someone more familiar with Ruby might be able to deem the fallback as unnecessary and fully remove it.)
* | FindRuby: fix selection of version x.0 (#15345)David Coppa2015-01-121-1/+1
|/ | | | | When "Ruby_FIND_VERSION_MINOR" is 0, the "if(Ruby_FIND_VERSION_MAJOR AND Ruby_FIND_VERSION_MINOR)" check evaluated to false.
* Modules: Format documentation to avoid over-long preformatted linesBrad King2014-10-221-11/+13
| | | | | | Convert several preformatted code block literals that enumerate lists of options or variables to use reST definition lists instead. Manually wrap other long lines in code blocks.
* FindRuby: Add support for Ruby 2.0 and 2.1Bas Couwenberg2014-02-281-4/+20
| | | | | | The most significant change since Ruby 1.9 is the changed path of config.h, from RbConfig::CONFIG['rubyhdrdir'] to RbConfig::CONFIG['rubyarchhdrdir'].
* Convert builtin help to reStructuredText source filesKitware Robot2013-10-151-12/+23
| | | | | | | | Run the convert-help.bash script to convert documentation: ./convert-help.bash "/path/to/CMake-build/bin" Then remove it.
* FindRuby: improve version selectionRolf Eike Beer2013-03-181-4/+13
| | | | | This will stop e.g. looking for a ruby1.9 executable first if "1.8 EXACT" was given.
* Remove CMake-language block-end command argumentsKitware Robot2012-08-131-19/+19
| | | | | | | | | | | | | | | | | Ancient versions of CMake required else(), endif(), and similar block termination commands to have arguments matching the command starting the block. This is no longer the preferred style. Run the following shell code: for c in else endif endforeach endfunction endmacro endwhile; do echo 's/\b'"$c"'\(\s*\)(.\+)/'"$c"'\1()/' done >convert.sed && git ls-files -z -- bootstrap '*.cmake' '*.cmake.in' '*CMakeLists.txt' | egrep -z -v '^(Utilities/cm|Source/kwsys/)' | egrep -z -v 'Tests/CMakeTests/While-Endwhile-' | xargs -0 sed -i -f convert.sed && rm convert.sed
* Convert CMake-language commands to lower caseKitware Robot2012-08-131-112/+112
| | | | | | | | | | | | | | | | | Ancient CMake versions required upper-case commands. Later command names became case-insensitive. Now the preferred style is lower-case. Run the following shell code: cmake --help-command-list | grep -v "cmake version" | while read c; do echo 's/\b'"$(echo $c | tr '[:lower:]' '[:upper:]')"'\(\s*\)(/'"$c"'\1(/g' done >convert.sed && git ls-files -z -- bootstrap '*.cmake' '*.cmake.in' '*CMakeLists.txt' | egrep -z -v '^(Utilities/cm|Source/kwsys/)' | xargs -0 sed -i -f convert.sed && rm convert.sed
* FindRuby: clean up querying variables from RubyRolf Eike Beer2012-02-171-31/+26
| | | | | | | Newer Ruby versions (from 1.9 onward) seem to warn if you query Config::CONFIG and print a warning to use RbConfig instead. RbConfig seems to also work in older versions, at least in 1.8. Use a macro to query RbConfig first and only if that doesn't give anything fall back to Config.
* FindRuby: do not blindly set version to 1.8.0Rolf Eike Beer2012-01-251-9/+10
| | | | | | | RUBY_VERSION was always set, even if no RUBY_EXECUTABLE was found. While it may make sense to assume a default version if we can't execute the binary, it certainly doesn't make sense to report a version if there is no executable at all.
* FindRuby.cmake: add more debug outputAlex Neundorf2012-01-051-0/+4
| | | | Alex
* FindRuby: add more possible library names (for ubuntu, #12172)Alex Neundorf2012-01-051-1/+1
| | | | Alex
* FindRuby: fix usage of RUBY_VERSION_MAJOR (#12172)Alex Neundorf2012-01-051-2/+2
| | | | Alex
* Find Ruby on OpenBSD when installed from ports (#12507)Alex Neundorf2011-10-121-1/+1
| | | | | | | The ruby library on OpenBSD is named rubyXY, not ruby X.y. Find that too. Alex
* Remove trailing whitespaceAlex Neundorf2011-10-121-4/+4
| | | | Alex
* Modules: Include builtin FindPackageHandleStandardArgs directlyBrad King2011-01-201-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The FindPackageHandleStandardArgs module was originally created outside of CMake. It was added for CMake 2.6.0 by commit e118a627 (add a macro FIND_PACKAGE_HANDLE_STANDARD_ARGS..., 2007-07-18). However, it also proliferated into a number of other projects that at the time required only CMake 2.4 and thus could not depend on CMake to provide the module. CMake's own find modules started using the module in commit b5f656e0 (use the new FIND_PACKAGE_HANDLE_STANDARD_ARGS in some of the FindXXX modules..., 2007-07-18). Then commit d358cf5c (add 2nd, more powerful mode to find_package_handle_standard_args, 2010-07-29) added a new feature to the interface of the module that was fully optional and backward compatible with all existing users of the module. Later commit 5f183caa (FindZLIB: use the FPHSA version mode, 2010-08-04) and others shortly thereafter started using the new interface in CMake's own find modules. This change was also backward compatible because it was only an implementation detail within each module. Unforutnately these changes introduced a problem for projects that still have an old copy of FindPackageHandleStandardArgs in CMAKE_MODULE_PATH. When any such project uses one of CMake's builtin find modules the line include(FindPackageHandleStandardArgs) loads the copy from the project which does not have the new interface! Then the including find module tries to use the new interface with the old module and fails. Whether this breakage can be considered a backward incompatible change in CMake is debatable. The situation is analagous to copying a standard library header from one version of a compiler into a project and then observing problems when the next version of the compiler reports errors in its other headers that depend on its new version of the original header. Nevertheless it is a change to CMake that causes problems for projects that worked with previous versions. This problem was discovered during the 2.8.3 release candidate cycle. It is an instance of a more general problem with projects that provide their own versions of CMake modules when other CMake modules depend on them. At the time we resolved this instance of the problem with commit b0118402 (Use absolute path to FindPackageHandleStandardArgs.cmake everywhere, 2010-09-28) for the 2.8.3 release. In order to address the more general problem we introduced policy CMP0017 in commit db44848f (Prefer files from CMAKE_ROOT when including from CMAKE_ROOT, 2010-11-17). That change was followed by commit ce28737c (Remove usage of CMAKE_CURRENT_LIST_DIR now that we have CMP0017, 2010-12-20) which reverted the original workaround in favor of using the policy. However, existing project releases do not set the policy behavior to NEW and therefore still exhibit the problem. We introduced in commit a364daf1 (Allow users to specify defaults for unset policies, 2011-01-03) an option for users to build existing projects by adding -DCMAKE_POLICY_DEFAULT_CMP0017=NEW to the command line. Unfortunately this solution still does not allow such projects to build out of the box, and there is no good way to suggest the use of the new option. The only remaining solution to keep existing projects that exhibit this problem building is to restore the change originally made in commit b0118402 (Use absolute path to FindPackageHandleStandardArgs.cmake everywhere, 2010-09-28). This also avoids policy CMP0017 warnings for this particular instance of the problem the policy addresses.
* Remove usage of CMAKE_CURRENT_LIST_DIR now that we have CMP0017Alex Neundorf2011-01-041-1/+1
| | | | | | | | This puts the new search behaviour for included files in action, i.e. now when a file from Modules/ include()s another file, it also gets the one from Modules/ included, i.e. the one it expects. Alex
* Use absolute path to FindPackageHandleStandardArgs.cmake everywhereAlex Neundorf2010-09-281-1/+1
| | | | | | | This is to avoid getting an (older) copy of FPHSA.cmake which is e.g. installed with KDE 4.5.0 and 4.5.1. Alex
* Merge topic 'ImprovedVersionCheckingInSomeModules'Brad King2010-08-101-19/+7
|\ | | | | | | | | | | | | | | | | | | | | | | | | 430336c Merge branch 'findsubversion_fphsa_cleanup' b6c6156 Use FPHSA() in FindSWIG, including version checking. 656cd2f Improved version checking for FindCUDA using the new mode of FPHSA 126db7b Improved version checking for FindSubversion using the new mode of FPHSA() 77d909b Fix DETAILS string with version number in FHPSA() 19b68b9 Improved version checking for FindJava using the new FPHSA() mode 6bb0b6e Improved version checking for FindRuby using the new mode of FPHSA() 946493f FindSquish doesn't detect the version, remove that from the documentation cb9d1ea Add version checking support to FindFlex and FindPerlLibs
| * Improved version checking for FindRuby using the new mode of FPHSA()Alex Neundorf2010-08-071-19/+7
| | | | | | | | Alex
* | Modules: Fix spelling 'To distributed' -> 'To distribute'Todd Gamblin2010-08-091-1/+1
|/
* -remove unnecessary debug outputAlexander Neundorf2010-01-271-1/+0
| | | | Alex
* make FindRuby work on Windows e.g. with ruby 1.9.1 (version string was ↵Alexander Neundorf2010-01-031-4/+5
| | | | | | constructed wrong) Alex
View Lorry Controller Status