On Friday 25 March 2011, Chatterjee, Shash wrote:
> Hi Alex,
>
> >- CMakeFindEclipseCDT4.cmake : this is slightly changed version from the
> > one shipped with cmake 2.8.4, it produces debug output. Please replace
> > the CMakeFindEclipseCDT4.cmake in your cmake 2.8.4 installation with this
> > file. Then create a fresh and empty build directory, and let cmake run
> > there, with the same command line as you posted. Capture the output, both
> > stdout and stderr in a log file and post it here.
>
> Thanks for sending this, most illuminating :-)
>
> >I saw that you are using ccache, maybe this behaves slightly different for
> >some things ?
>
> I am using Fedora Core 14, with all latest yum updates. I have not done
> anything knowingly for cmake to prefer ccache over gcc directly, so looks
> like by default cmake will use ccache over straight GCC if it finds it. Of
> course, the speedup is most welcome.
>
> I have attached two versions of the log output. The first one is with the
> problem reproduced.
>
> I noticed in your debug output that the C compiler was being detected as
> blank, and no C++ include directories were being found even though the
> compiler was detected as "GNU". I changed the project definition in my
> CMakeLists.txt from "project ( eclipsetest CXX ) " to "project ( eclipstest
> C CXX ) " and everything worked as expected.
Ah, indeed, it was using CMAKE_C_COMPILER also when finding out the C++ stuff,
which works, but only if CMAKE_C_COMPILER is actually set.
Please try the attached version, this should also work with your CXX-only
project.
Let me know whether it works for you.
Thanks
Alex
#=
# Copyright 2009 Kitware, Inc.
#
# Distributed under the OSI-approved BSD License (the "License");
# see accompanying file Copyright.txt for details.
#
# This software is distributed WITHOUT ANY WARRANTY; without even the
# implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
# See the License for more information.
#=
# (To distribute this file outside of CMake, substitute the full
# License text for the above reference.)
# This file is included in CMakeSystemSpecificInformation.cmake if
# the Eclipse CDT4 extra generator has been selected.
FIND_PROGRAM(CMAKE_ECLIPSE_EXECUTABLE NAMES eclipse DOC "The Eclipse executable")
# This variable is used by the Eclipse generator and appended to the make invocation commands.
SET(CMAKE_ECLIPSE_MAKE_ARGUMENTS "" CACHE STRING "Additional command line arguments when Eclipse invokes make. Enter e.g. -j to get parallel builds")
# This variable is used by the Eclipse generator in out-of-source builds only.
SET(ECLIPSE_CDT4_GENERATE_SOURCE_PROJECT FALSE CACHE BOOL "If enabled, CMake will generate a source project for Eclipse in CMAKE_SOURCE_DIR")
MARK_AS_ADVANCED(ECLIPSE_CDT4_GENERATE_SOURCE_PROJECT)
# The Eclipse generator needs to know the standard include path
# so that Eclipse ca find the headers at runtime and parsing etc. works better
# This is done here by actually running gcc with the options so it prints its
# system include directories, which are parsed then and stored in the cache.
MACRO(_DETERMINE_GCC_SYSTEM_INCLUDE_DIRS _lang _resultIncludeDirs _resultDefines)
message(STATUS "Getting include dirs for ${_lang} ...")
SET(${_resultIncludeDirs})
SET(_gccOutput)
FILE(WRITE "${CMAKE_BINARY_DIR}/CMakeFiles/dummy" "\n" )
IF (${_lang} STREQUAL "CXX")
SET(_compilerExecutable "${CMAKE_CXX_COMPILER}")
ELSE (${_lang} STREQUAL "CXX")
SET(_compilerExecutable "${CMAKE_C_COMPILER}")
ENDIF (${_lang} STREQUAL "CXX")
EXECUTE_PROCESS(COMMAND ${_compilerExecutable} -v -E -x ${_lang} -dD dummy
WORKING_DIRECTORY ${CMAKE_BINARY_DIR}/CMakeFiles
ERROR_VARIABLE _gccOutput
OUTPUT_VARIABLE _gccStdout )
FILE(REMOVE "${CMAKE_BINARY_DIR}/CMakeFiles/dummy")
MESSAGE(STATUS "stderr: -${_gccOutput}-")
MESSAGE(STATUS "stdout: -${_gccStdout}-")
# First find the system include dirs:
IF( "${_gccOutput}" MATCHES "> search starts here[^\n]+\n *(.+) *\n *End of (search) list" )
# split the output into lines and then remove leading and trailing spaces from each of them:
STRING(REGEX MATCHALL "[^\n]+\n" _includeLines "${CMAKE_MATCH_1}")
FOREACH(nextLine ${_includeLines})
STRING(STRIP "${nextLine}" _includePath)
LIST(APPEND ${_resultIncludeDirs} "${_includePath}")
ENDFOREACH(nextLine)
ENDIF( "${_gccOutput}" MATCHES "> search starts here[^\n]+\n *(.+) *\n *End of (search) list" )
# now find the builtin macros:
STRING(REGEX MATCHALL "#define[^\n]+\n" _defineLines "${_gccStdout}")
# A few example lines which the regexp below has to match properly:
# #define MAX(a,b) ((a) > (b) ? (a) : (b))
# #define __fastcall __attribute__((__fastcall__))
# #define FOO (23)
# #define __UINTMAX_TYPE__ l
