[CMake] CMake 2.8.2 with WindRiver diab compiler dcc.exe/dplus.exe on WinXP: CMake Error: Could not COPY_FILE. while detecting compiler ABI

[Molsen, Hannes]

Hi all,

if this is of any help or interest: I added the option --debug-output, which does not solve the problem, but gives at least some additional information and a nicer workaround:

=== CMake Output : snip ===
-- Detecting C compiler ABI info
   Called from: [2]     C:/Program Files/CMake 2.8/share/cmake-2.8/Modules/CMakeTestCCompiler.cmake
                [1]     D:/CCView/rat/Framework/CMakeLists.txt
CMake Error: Could not COPY_FILE.
  OutputFile: ''
    copyFile: [...]

=== CMake Output : snap ===

All following fails have the same "Called from:" output.

In CMakeTestCCompiler.cmake I found a flag called "CMAKE_C_COMPILER_FORCED". If this is set, the ABI detection is skipped. Does --debug-trycompile set this flag?

If I set this flag manually in my cmake call
cmake -G "MinGW Makefiles" -DCMAKE_C_COMPILER_FORCED=TRUE -DCMAKE_CXX_COMPILER_FORCED=TRUE [...]
the problem does not occur anymore, because the problematic code is skipped.
This is a way nicer workaround, because I have to run CMake only once and don't have an error output, but it does not solve the problem, it just ignores it.
So I still want to get the ABI detection working correctly.

Yours,
Hannes

-----Original Message-----
From: Brad King [mailto:brad.king at kitware.com] 
Sent: Donnerstag, 16. September 2010 18:11
To: Molsen, Hannes
Cc: David Cole; cmake at cmake.org
Subject: Re: [CMake] CMake 2.8.2 with WindRiver diab compiler dcc.exe/dplus.exe on WinXP: CMake Error: Could not COPY_FILE. while detecting compiler ABI

On 09/16/2010 08:11 AM, Molsen, Hannes wrote:
>        -- Detecting C compiler ABI info
>        CMake Error: Could not COPY_FILE.
>          OutputFile: ''
>            copyFile: 'D:/CCView/binaries/PPC603diab/rat/Framework/CMakeFiles/CMakeDetermineCompilerABI_C.bin'
> 
>        Unable to find executable for try_compile: tried        "D:/CCView/binaries/PPC603diab/rat/Framework/CMakeFiles/CMakeTmp/cmTryCompileExec" and  "D:/CCView/binaries/PPC603diab/rat/Framework/CMakeFiles/CMakeTmp/Debug/cmTryCompileExec" and    "D:/CCView/binaries/PPC603diab/rat/Framework/CMakeFiles/CMakeTmp/Development/cmTryCompileExec".
[snip]
> What causes CMake to fail at the COPY_FILE stage?
> How can I fix this without having to run CMake a second time with --debug-trycompile?

The message you mentioned [1] is suggesting the --debug-trycompile
option to help diagnose the problem, not as a workaround.  In a
fresh build tree, without --debug-trycompile, after this error
is reported, look for CMakeFiles/CMakeOutput.log.  It should have
the ABI detection attempt.  What is the reported output?

-Brad

[1] http://www.cmake.org/pipermail/cmake/2010-May/037118.html
---
This communication contains confidential information. If you are not the intended recipient please return this email to the sender and delete it from your records.

Diese Nachricht enthält vertrauliche Informationen. Sollten Sie nicht der beabsichtigte Empfänger dieser E-mail sein, senden Sie bitte diese an den Absender zurück und löschen Sie die E-mail aus Ihrem System.