On Wed, Oct 3, 2012 at 8:36 AM, Pere Mato Vila wrote:
>
> On Oct 3, 2012, at 1:36 PM, David Cole wrote:
>
>> The mismatch problem should be fixed in the builds of CMake 2.8.10-rc1
>> that we released yesterday. Give that a try and see if the default
>> compiler selection is better here -- it shoul
On Oct 3, 2012, at 1:36 PM, David Cole wrote:
> The mismatch problem should be fixed in the builds of CMake 2.8.10-rc1
> that we released yesterday. Give that a try and see if the default
> compiler selection is better here -- it should be.
>
> Let us know if there's still an issue...
Yes., I
On Wed, Oct 3, 2012 at 3:49 AM, Nick Overdijk wrote:
> I'm not sure where it was, but CMake prefers gcc over cc, and cxx over g++.
> You can force it by setting CC=clang.
>
> On 2012-03-10, at 09:27:28 , Pere Mato Vila wrote:
>
>> In my Mac system (10.7.4) with Xcode (4.4.1) CMake finds by defau
I'm not sure where it was, but CMake prefers gcc over cc, and cxx over g++. You
can force it by setting CC=clang.
On 2012-03-10, at 09:27:28 , Pere Mato Vila wrote:
> In my Mac system (10.7.4) with Xcode (4.4.1) CMake finds by default the GNU
> compiler for C and Clang for C++. This posses pro
In my Mac system (10.7.4) with Xcode (4.4.1) CMake finds by default the GNU
compiler for C and Clang for C++. This posses problems later when building my
package. The package can be built correctly either with Clang or with GCC but
not in a mixed mode. See the cmake output:
-- The C compile
