Ok so you're basically saying that I can just tell cmake that I want
to use a different compiler then, I think that would actually work
with my current compiler and cmake...
On Fri, May 6, 2011 at 12:58 PM, j s wrote:
> I'm really sorry I answered this question. I personally hate
> macports, bu
I'm really sorry I answered this question. I personally hate
macports, but it has its own version of cmake that won't work with the apple
compiler:
/opt/local/bin/cmake -DCMAKE_CXX_COMPILER=/opt/local/bin/g++
-DCMAKE_C_COMPILER=/opt/local/bin/gcc ..
make VERBOSE=1
/opt/local/bin/g++-Wl,-sea
Macports works, but be warned that if you use rtti, (exceptions,
dynamic casting), make sure that you only link against C++ libraries
using the same compiler. Macports errantly uses its own system
libraries in its compiler's.
Juan
On Fri, May 6, 2011 at 10:04 AM, Sean McBride wrote:
> On Fri, 6
I got it from here:
http://hpc.sourceforge.net/
But that's just a pre-compiled version. If you compile gcc4.x yourself
on your mac you'll see that it behaves the same way.
I'm not trying to use any part of the Apple toolchain, so it makes
perfect sense to me.
On Fri, May 6, 2011 at 11:04 AM, Sea
On Fri, 6 May 2011 10:51:57 -0400, Michael Allen said:
>I've installed a newer version of gcc because the version supplied by
>Apple is so far out of date, but I don't know how to configure cmake
>such that it uses the normal gcc flags instead of the
>Apple specific flags. Is there a way to config
