[Paraview] Compiling ParaView 3 on Mac OS X (PowerPC)

[Mike Jackson]

On May 10, 2007, at 5:28 PM, Bernhard Gschaider wrote:

>
>>>>>> On Thu, 10 May 2007 09:01:28 -0600
>>>>>> "c" == clinton  <clinton at elemtech.com> wrote:
>
>>> But this problem still persists: I don't know too much about
>>> cmake, but am I right that this is a problem with cmake(I'm
>>> using 2.4.6) or the cmake-Files that come with the soure,
>>> because I don't find where QT4_WRAP_CPP is being defined.
>
>     c> QT4_WRAP_CPP is defined in CMake's FindQt4.cmake file, and the
>     c> macro doesn't get defined until qmake is found.  Set the
>     c> QT_QMAKE_EXECUTABLE variable to "/your/path/to/qt4/bin/qmake"
>     c> You said you are using Trolltech's DMG install?  I've used that
>     c> too.
>
> Thanks. It was a stupid typo to the path of qmake. Now everything
> compiles OK until at 90% (after a lot of the QT-stuff was successfully
> compiled) it says:
>
> [90%] Building CXX object QT/Core/CMakeFiles/pqCore.dir/ 
> pqFormBuilder.o
> /Library/Frameworks/QTCore.framework/Headers/qglobal.h:606: error:  
> template with C linkage
>
> then lots of similar messages follow. Googling around told me that the
> problem could be an unterminated
>
> extern "C" {
>
> could be the cause.
>
> And this is where I am stuck: usually in that situation I would copy
> the last compiler call, add the -E option, look at the output and
> find out which header might be the problem. But cmake "protects" me
> from that knowledge. Is there a way to find out how the compiler is
> called for that file?
>

Use ccmake to enable CMAKE_VERBOSE_MAKEFILE. Then recompile and all  
the calls to gcc and the linker can be seen.

Simple as pie...
-- 
Mike Jackson   Senior Research Engineer
Innovative Management & Technology Services