summaryrefslogtreecommitdiffstats
path: root/Modules/Compiler/GNU-FindBinUtils.cmake
Commit message (Collapse)AuthorAgeFilesLines
* Allow toolchain suffix without leading dashDan McGregor2023-05-091-0/+2
| | | | | | | | FreeBSD installs both LLVM and gcc with tools named after the major version, in the form "clang<major>", such as "clang16". Detect compilers named this way, and find the related toolchain tools.
* BinUtils: Avoid searching CMAKE_PREFIX_PATHCristian Adam2021-08-091-0/+2
| | | | | | | | | Our `find_program` calls specify `HINTS` to look in the toolchain's directory first, and then in `PATH`. `CMAKE_PREFIX_PATH` may be specified by the user to help find packages for project dependencies, but this should not override the binutils. Fixes: #22512
* FindBinUtils: Revert "Use the compiler to get the path to compiler tools"Brad King2019-11-071-16/+10
| | | | | | | | Revert commit b2fd479df5 (FindBinUtils: Use the compiler to get the path to compiler tools, 2019-09-22, v3.16.0-rc1~51^2). The compiler's answer may incorrectly come from the `PATH`. Another approach will be needed. Fixes: #19934
* FindBinUtils: Use the compiler to get the path to compiler toolsIsuru Fernando2019-09-271-10/+16
| | | | Fixes: #19728
* MinGW: Fix locating BinUtils when compiler has a suffixRegina Pfeifer2019-02-061-2/+2
| | | | | | | | While all executables from a mingw toolchain share a common prefix, only the ones provided with the compiler have a suffix, the binutils do not. Fixes: #18879
* GCC,Clang: Mark CMAKE_<LANG>_COMPILER_{AR,RANLIB} as advancedBrad King2017-06-221-0/+2
|
* GCC: more patterns for ar/ranlibRuslan Baratov2017-05-141-2/+10
|
* Rename CMAKE_GCC_{AR,RANLIB} to CMAKE_LANG_COMPILER_{AR,RANLIB}Ruslan Baratov2017-04-031-2/+2
| | | | | | The variables recently added by commit b9d36826 (Add 'CMAKE_GCC_AR' and 'CMAKE_GCC_RANLIB' variables, 2017-03-08) are more appropriately managed with language-specific names rather than toolchain-specific names.
* GNU-FindBinUtils: Avoid setting policy CMP0054Brad King2017-03-101-3/+1
| | | | | | | The `cmake_policy(SET)` call triggers `CMP0011` warnings when this module is used in a project that does not set `CMP0011` to NEW. We could avoid these with a `cmake_policy` PUSH/POP pair, but it is simpler to adjust our code to not trigger `CMP0054` in the first place.
* Add 'CMAKE_GCC_AR' and 'CMAKE_GCC_RANLIB' variablesRuslan Baratov2017-03-081-0/+27