seanzig at users.sourceforge.net
Wed Feb 27 14:24:28 EST 2008
I had problems with vtkEncodeString myself before I started having
other trouble in cmake (I posted about it earlier on the paraview
list). It all went away when I started over with a fresh cvs checkout.
I assume my original checkout failed midstream and cvs update would
not add the missing files. I'd suggest trying that.
Quoting Francois Bertel <francois.bertel at kitware.com>:
> All the VTK dashboard work fine.
> vtkEncodeString is an executable generated in the bin directory of
> your build tree. I don't know why in the process there is a path to
> VTK/VolumeRendering. The location of the source file is
> Do you use the last stable cmake (2.4.8)?
> Feng Ding wrote:
>> Dear list,
>> I just updated VTK source using CVS. After ccmake, make gave me some
>> errors as follows:
>> make: *** No rule to make target
>> `../VTK/VolumeRendering/vtkEncodeString', needed by
>> make: *** [VolumeRendering/CMakeFiles/vtkVolumeRendering.dir/all] Error 2
>> make: *** [all] Error 2
>> I checked that there were no vtkEncodeString.* files under the
>> VolumeRendering directory. Any one can help? Thanks!
>> Best regards,
>> DING Feng
>> This is the private VTK discussion list. Please keep messages
>> on-topic. Check the FAQ at: http://www.vtk.org/Wiki/VTK_FAQ
>> Follow this link to subscribe/unsubscribe:
> François Bertel, PhD | Kitware Inc. Suite 204
> 1 (518) 371 3971 x113 | 28 Corporate Drive
> | Clifton Park NY 12065, USA
> This is the private VTK discussion list.
> Please keep messages on-topic. Check the FAQ at:
> Follow this link to subscribe/unsubscribe:
More information about the vtkusers