Re: [cmake-developers] [CMake] Toolchains and CMAKE_FORCE_C_COMPILER in 3.5

On 02/26/2016 07:18 AM, James Crosby wrote: > Can confirm it works for armcc - thanks! Great, thanks for testing! I've merged the feature to 'master' for inclusion in CMake 3.6. With this we can re-consider deprecating CMakeForceCompiler for that release too. Thanks, -Brad -- Powered by

Re: [cmake-developers] [CMake] Toolchains and CMAKE_FORCE_C_COMPILER in 3.5

> On 24 Feb 2016, at 16:08, Brad King wrote: > > try_compile: Add option to control type of target > https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=7f1bd9fe > > One should be able to simply add > >set(CMAKE_TRY_COMPILE_TARGET_TYPE STATIC_LIBRARY) > > to the

Re: [cmake-developers] [CMake] Toolchains and CMAKE_FORCE_C_COMPILER in 3.5

On 02/17/2016 01:46 PM, James Crosby wrote: >> Perhaps we could have a setting in a toolchain file like [snip] >> that tells CMake to use add_library(STATIC) instead of add_executable() >> in its generated try_compile projects. That would avoid linking through >> the toolchain. > > OK this makes

Re: [cmake-developers] [CMake] Toolchains and CMAKE_FORCE_C_COMPILER in 3.5

> On 17 Feb 2016, at 14:33, Brad King wrote: > > One could look at adding hooks to the compiler id logic to add alternatives > provided by the toolchain file. Or, we could provide a way to set the > compiler > id but not also skip other checks. In the worst case such a

Re: [cmake-developers] [CMake] Toolchains and CMAKE_FORCE_C_COMPILER in 3.5

Moving discussion to cmake-developers. On 02/15/2016 12:47 PM, James Crosby wrote: > I'm worried that built-in compiler detection might not be possible across > the variety of cross-compilers used. In some cases, for example, the > existence of a particular compiler, or a modified version of it,