<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7651.59">
<TITLE>RE: [CMake] Eclipse generator - scanner-discovered include pathsand pre-processor symbols</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>Hi Alex,<BR>
<BR>
>- CMakeFindEclipseCDT4.cmake : this is slightly changed version from the one<BR>
>shipped with cmake 2.8.4, it produces debug output. Please replace the<BR>
>CMakeFindEclipseCDT4.cmake in your cmake 2.8.4 installation with this file.<BR>
>Then create a fresh and empty build directory, and let cmake run there, with<BR>
>the same command line as you posted. Capture the output, both stdout and<BR>
>stderr in a log file and post it here.<BR>
<BR>
Thanks for sending this, most illuminating :-)<BR>
<BR>
>I saw that you are using ccache, maybe this behaves slightly different for<BR>
>some things ?<BR>
<BR>
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.<BR>
<BR>
I have attached two versions of the log output. The first one is with the problem reproduced.<BR>
<BR>
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. <BR>
<BR>
Thanks,<BR>
Shash<BR>
</FONT>
</P>
</BODY>
</HTML>