[vtk-developers] ThirdParty/verdict installs in odd places
Marcus D. Hanwell
marcus.hanwell at kitware.com
Thu Aug 16 13:28:08 EDT 2012
On Thu, Aug 16, 2012 at 12:14 PM, David Gobbi <david.gobbi at gmail.com> wrote:
> On Thu, Aug 16, 2012 at 9:59 AM, David Thompson
> <david.thompson at kitware.com> wrote:
>> Hi David,
>>
>>> When I run "make install" on VTK master, the verdict module
>>> installs its files in the wrong places, e.g. not inside of a
>>> vtk-6.0 subdirectory:
>>>
>>> /usr/local/doc/verdict
>>> /usr/local/doc/verdict/1.2.0/verdict_test.cpp
>>> /usr/local/include/verdict.h
>>> /usr/local/lib/libvtkverdict-6.0.so.1.2.0
>>>
>>> Is there anyone familiar with this module?
>>
>> Yes. It appears to be using some old pre-modularization CMake variables to determine the install path (e.g., VTK_INSTALL_LIB_DIR_CM24). Its behavior should be no worse than VTK's hdf5 build… is it? The only difference between verdict's and hdf5's use of these install locataions is that verdict only looks for VTK_INSTALL_LIB_DIR_CM24 if the install prefix hasn't been explicitly set in the CMake cache. That was done so that (back in the days of SVN) verdict could be built standalone for use outside VTK.
>
> It's definitely worse than hdf5.
>
> include/vtk-6.0/vtkhdf5/hdf5.h
>
> versus
>
> include/verdict.h
> doc/verdict/...
>
We must have missed this when converting over. I was intending to take
a pass for any further references to VTK_*_CM24 as they should all be
removed and using the new variables. CM24 is CMake 2.4 compatibility,
I don't think that needs preserving any more!
Marcus
More information about the vtk-developers
mailing list