Oh, sorry for the misunderstanding.  I'm really more of a Linux guy, but
I'm building Paraview for some of my Mac users.  Anyway, I _am_ using
Makefiles.  It fails here:
[ 91%] Building CXX object Qt/Core/CMakeFiles/pqCore.dir/pq3DWidgetFactory.o

Would it help to post the verbose make output for this file?

-Sean

Mike Jackson wrote:
Can you post the actual build command for the file from the Xcode detailed display? I would say that there is a missing include path somehow.

Just for giggles, can you build paraview using Makefiles instead of Xcode?

Mike Jackson

Sean Ziegeler wrote:
I thought I'd seen something on the mailing list a while back on this, but I can't seem to find it now. I'm trying to build Paraview from source on OS X 10.5 but I get missing header errors, e.g.:

In file included from /Users/ziegeler/paraview/qt/4.3.5/lib/QtCore.framework/Headers/QObject:1, from /Users/ziegeler/paraview/src/3.4.0/Qt/Core/pq3DWidgetFactory.h:36, from /Users/ziegeler/paraview/src/3.4.0/Qt/Core/pq3DWidgetFactory.cxx:32: /Users/ziegeler/paraview/qt/4.3.5/lib/QtCore.framework/Headers/qobject.h:49:32: error: QtCore/qobjectdefs.h: No such file or directory /Users/ziegeler/paraview/qt/4.3.5/lib/QtCore.framework/Headers/qobject.h:50:28: error: QtCore/qstring.h: No such file or directory /Users/ziegeler/paraview/qt/4.3.5/lib/QtCore.framework/Headers/qobject.h:51:31: error: QtCore/qbytearray.h: No such file or directory /Users/ziegeler/paraview/qt/4.3.5/lib/QtCore.framework/Headers/qobject.h:52:26: error: QtCore/qlist.h: No such file or directory
[snip]

It's PV 3.4.0 with Python and 64-bit ID's, Qt 4.3.5 built from source with no special options other than "-release", and XCode 3.0 w/gcc 4.0.1. Should I use a different version of Qt or XCode?

Thanks,
Sean
_______________________________________________
ParaView mailing list
[email protected]
http://www.paraview.org/mailman/listinfo/paraview

_______________________________________________
ParaView mailing list
[email protected]
http://www.paraview.org/mailman/listinfo/paraview

Reply via email to