A slightly different result:

[ 99%] Generating ../VTKExamples
Internal cmake changing into directory: /Users/ystarrev/Development/ vtkbin/Examples/All
======== CMake output     ======
CMake Warning (dev) at GUI/Qt/ImageViewer/CMakeLists.txt:28 (ADD_EXECUTABLE):
  Policy CMP0003 should be set before this line.  Add code such as

    if(COMMAND cmake_policy)
      cmake_policy(SET CMP0003 NEW)
    endif(COMMAND cmake_policy)
....



On 1-May-08, at 2:16 PM, [EMAIL PROTECTED] wrote:


Do you still have the problem if you delete your  build_dir/Examples
directory, re-run cmake, and rebuild? Perhaps you have some leftovers from a
previous VTK configuration still stuck in your examples?

Clint

On Thursday 01 May 2008 2:02:31 pm Yves Starreveld wrote:
When building cvs VTK with qt4 on OSX.5.2:

[ 99%] Generating ../VTKExamples
Internal cmake changing into directory: /Users/ystarrev/Development/
vtkbin/Examples/All
======== CMake output     ======
Multiple versions of QT found please set DESIRED_QT_VERSION
Multiple versions of QT found please set DESIRED_QT_VERSION
Multiple versions of QT found please set DESIRED_QT_VERSION
CMake Warning (dev) at GUI/Qt/ImageViewer/CMakeLists.txt:28
(ADD_EXECUTABLE):
 Policy CMP0003 should be set before this line.  Add code such as

   if(COMMAND cmake_policy)
     cmake_policy(SET CMP0003 NEW)
   endif(COMMAND cmake_policy)




Despite having DESIRED_QT_VERSION set to 4 in the main CMakeCache.txt
file.

(qt4 built with -no-frameworks option)

Yves

On 1-May-08, at 1:48 PM, Bill Hoffman wrote:
I am happy to announce that CMake 2.6.0 RC10 is ready for testing.
You can find the source and binaries here:
http://www.cmake.org/files/v2.6/

Please give it a try soon. I really mean it this time...  I am going
to release 2.6.0 soon.  :)

_______________________________________________
CMake mailing list
[email protected]
http://www.cmake.org/mailman/listinfo/cmake



_______________________________________________
CMake mailing list
[email protected]
http://www.cmake.org/mailman/listinfo/cmake

Reply via email to