On Sunday, April 13, 2014 12:12:10 Rolf Eike Beer wrote:
> > include (CMakeForceCompiler)
> > CMAKE_FORCE_C_COMPILER (gcc gcc)
> > CMAKE_FORCE_CXX_COMPILER (g++ g++)
>
> A more general question: is there any reason one would have to force a
> compiler in a toolchain file? Just set CMAKE_*_COMPILER
> include (CMakeForceCompiler)
> CMAKE_FORCE_C_COMPILER (gcc gcc)
> CMAKE_FORCE_CXX_COMPILER (g++ g++)
A more general question: is there any reason one would have to force a
compiler in a toolchain file? Just set CMAKE_*_COMPILER to the path, that
should be all that is needed, no? I've seen this
Am Sonntag, 13. April 2014, 11:05:44 schrieb Tim Blechmann:
> hi all,
>
> i'm trying to use the iOS.cmake toolchain file from [1]. it works fine
> with cmake-2.8.12.2, but fails with cmake-3.0 (today's master), which
> gives me:
>
> -->8---
> CMake Error at CMakeLists.txt:16 (project):
>
hi all,
i'm trying to use the iOS.cmake toolchain file from [1]. it works fine
with cmake-2.8.12.2, but fails with cmake-3.0 (today's master), which
gives me:
-->8---
CMake Error at CMakeLists.txt:16 (project):
The CMAKE_C_COMPILER:
gcc
is not a full path and was not found in th