On Apr 16, 2010, at 5:06 PM, David MacMahon wrote: > > On Apr 16, 2010, at 15:56 , Jerry wrote: > >> /usr/bin/c++ -bundle -headerpad_max_install_names -o qt.so >> CMakeFiles/qt.dir/qt.cpp.o CMakeFiles/qt.dir/__/bindings/qt_gui/ >> plqt.cpp.o ../src/libplplotd.9.7.0.dylib /usr/lib/libm.dylib - >> framework QtSvg -framework QtGui -framework Carbon -framework >> AppKit -framework QtXml -framework QtCore /usr/lib/libz.dylib - >> framework ApplicationServices /usr/lib/libltdl.dylib /usr/lib/ >> libdl.dylib ../lib/csa/libcsirocsa.0.0.1.dylib ../lib/qsastime/ >> libqsastime.0.0.1.dylib /usr/lib/libm.dylib > > Maybe the "-framework Carbon" is confusing things? I thought you > were using the Cocoa version of Qt, so where does that come from? > > Dave > I am using the Cocoa version of Qt and I have no idea why the Carbon framework is being linked. From my earlier post:
* All Apple-supplied files are both 32- and 64-bits for both PPC and Intel processors EXCEPT THE CARBON FRAMEWORK WHICH IS 32 BITS AND SHOULD NOT BE LINKED WHEN DOING A 64-BIT BUILD. I suppose that Carbon is also linked when using Cocoa version of Qt when doing 32-bit builds but it doesn't create a problem then. Is there ever a reason to use the Carbon version of Qt and if not, then maybe PLplot should _never_ link the Carbon Qt. This still doesn't explain why the two PLplot libraries are being built as 32 bit. Jerry ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Plplot-devel mailing list Plplot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-devel
