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] Toolchains and CMAKE_FORCE_C_COMPILER in 3.5

On 02/15/2016 12:47 PM, James Crosby wrote: > Using a dummy link command to check that linking works seems to > undermine the purpose of checking in the first place, which suggests > that perhaps it should still be possible to skip the check? For reference, this discussion has moved to the

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,

Re: [CMake] Toolchains and CMAKE_FORCE_C_COMPILER in 3.5

Hi Brad, For context, I'm the maintainer of yotta (github: ARMmbed/yotta), a module system primarily for cross-compiled embedded software, which uses CMake for the build. > Basically CMake now needs to detect a lot more from the compiler than > we can expect a caller to provide in a

Re: [CMake] Toolchains and CMAKE_FORCE_C_COMPILER in 3.5

[mailto:cmake-boun...@cmake.org] On Behalf Of Thibault Genessay Sent: Dienstag, 9. Februar 2016 15:10 To: cmake@cmake.org Subject: [CMake] Toolchains and CMAKE_FORCE_C_COMPILER in 3.5 Hi, I'm a long time user of CMake (and huge fan of it) but newly registered on this list, so please forgive me

Re: [CMake] Toolchains and CMAKE_FORCE_C_COMPILER in 3.5

[Note: this was erroneously sent off-list to Brad only, sorry for the noise] Hi Brad, On Tue, Feb 9, 2016 at 6:02 PM, Brad King wrote: > Thanks for trying the release candidate! > Well, the download page is a bit nasty as when you click "download the latest release

Re: [CMake] Toolchains and CMAKE_FORCE_C_COMPILER in 3.5

On 02/10/2016 09:30 AM, Thibault Genessay wrote: >> While CMakeForceCompiler is deprecated we think it should still work >> in most cases where it worked before, just with a warning. What >> actually breaks? > > I downloaded 3.5 this morning and tried again. I get all the warnings, > but the

Re: [CMake] Toolchains and CMAKE_FORCE_C_COMPILER in 3.5

On 02/10/2016 03:49 AM, Vania Joloboff wrote: > We have not yet moved to 3.5 but seeing this discussion, I am wondering > what we will have to do. In our project, we have several C and C++ cross > compilers and we want to compare them on selected benchmarks. We also > want to compare different

Re: [CMake] Toolchains and CMAKE_FORCE_C_COMPILER in 3.5

Hi We have not yet moved to 3.5 but seeing this discussion, I am wondering what we will have to do. In our project, we have several C and C++ cross compilers and we want to compare them on selected benchmarks. We also want to compare different compile options and different linking options. We

[CMake] Toolchains and CMAKE_FORCE_C_COMPILER in 3.5

Hi, I'm a long time user of CMake (and huge fan of it) but newly registered on this list, so please forgive me if I have missed something regarding the new 3.5 series. I use CMake with the GCC ARM Embedded compiler ( https://launchpad.net/gcc-arm-embedded) to cross-compile my project (Windows

Re: [CMake] Toolchains and CMAKE_FORCE_C_COMPILER in 3.5

Hi Thibault, Can you post your toolchain file? - Chuck On Tue, Feb 9, 2016 at 9:10 AM, Thibault Genessay wrote: > Hi, > > I'm a long time user of CMake (and huge fan of it) but newly registered on > this list, so please forgive me if I have missed something regarding the >

Re: [CMake] Toolchains and CMAKE_FORCE_C_COMPILER in 3.5

Hi Thibault, Thanks for trying the release candidate! On 02/09/2016 09:10 AM, Thibault Genessay wrote: > I installed 3.5 and the build broke While CMakeForceCompiler is deprecated we think it should still work in most cases where it worked before, just with a warning. What actually breaks? >