Hi Andreas,
On Wednesday 14 May 2008, you wrote:
> Hi,
> Thank you for all these hints. Are details like that described in the
> Mastering CMake book?
Yes and no.
The process how the system and the compiler are determined is described, but
not every implementation detail of the files.
> I trac
Hi,
Thank you for all these hints. Are details like that described in the
Mastering CMake book?
I tracked it down to:
CMakeDetermineCCompiler.cmake: line 97:
IF (NOT _CMAKE_TOOLCHAIN_PREFIX)
GET_FILENAME_COMPONENT(COMPILER_BASENAME "${CMAKE_C_COMPILER}" NAME_WE)
MESSAGE(STATUS "CMAKE_C_COMPILE
On Tuesday 13 May 2008, Andreas Pokorny wrote:
> Hi,
> Can you give me some hints on filtering the strace output. I expected
> to find syscalls
> that try to open "ar" or "ar.exe". There was none.
It's done in Modules/CMakeFindBinUtils.cmake, which is included e.g. in
Modules/CMakeDetermineCCompi
Hi,
Can you give me some hints on filtering the strace output. I expected
to find syscalls
that try to open "ar" or "ar.exe". There was none.
I looked at calls of "symlink_info::check". When grepping for these
calls, there was a
block of:
38 4093345 [main] cmake 528 symlink_info::check: 0 = symlin
On Friday 09 May 2008, Andreas Pokorny wrote:
> Hello,
> I currently try to replace my cmake-2.4 cross compile workarounds with
> proper cmake-2.6 toolchain files.
> The first one I tried was my ARM QNX Neutrino 6.3 file:
>
>
> SET(CMAKE_SYSTEM_NAME QNX)
> SET(CMAKE_SYSTEM_
Hello,
I currently try to replace my cmake-2.4 cross compile workarounds with
proper cmake-2.6 toolchain files.
The first one I tried was my ARM QNX Neutrino 6.3 file:
SET(CMAKE_SYSTEM_NAME QNX)
SET(CMAKE_SYSTEM_VERSION 6.3)
SET(QNX_TARGET $ENV{QNX_TARGET} CACHE PATH "Pat
