Re: [CMake] CMake incorrectly passes linker flags to ar

2016-01-11 Thread Alan Burlison
7;t call CMake directly. I suspect that's not too uncommon, when CMake is used to build just the native components of a larger platform-independent system. -- Alan Burlison -- -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org

Re: [CMake] CMake incorrectly passes linker flags to ar

2016-01-11 Thread Alan Burlison
On 11/01/2016 16:13, Brad King wrote: On 01/11/2016 10:49 AM, Alan Burlison wrote: So is the answer here to add -m64 just to CMAKE_EXE_LINKER_FLAGS and CMAKE_SHARED_LINKER_FLAGS and not to CMAKE_STATIC_LINKER_FLAGS? Are CMAKE_STATIC_LINKER_FLAGS only ever used with ar? Yes and yes. Actually

Re: [CMake] CMake incorrectly passes linker flags to ar

2016-01-11 Thread Alan Burlison
de, i.e. 64 bit. We therefore force it to either 'amd64' or 'sparcv9'. There seems to be an assumption baked into CMake that if the underlying OS is *nix and is 32-bit then all executables that run on it are 32 bit and if it is 64-bit then all the executables are 64-bit as

[CMake] CMake incorrectly passes linker flags to ar

2016-01-11 Thread Alan Burlison
struggling to understand when passing in linker flags to ar *ever* makes sense, at least on *nix platforms. And that code seems to be the same in 2.8.6 and 3.3.2 so it doesn't explain why the incorrect flags to ar have appeared in 3.3.2. This looks like a bug to me... -- Alan Burlison --