[vtk-developers] Bug Tracker: How to deal with issues closed in error?

[Dan Lipsa]

Peter,
I would file a new bug as this is FindProj4 specific, rather than the fact
that VTK used in the past a very old proj4 which was not compatible with
recent versions.

Thanks,
Dan


On Fri, Jul 29, 2016 at 7:57 AM, Peter Mattern <pmattern at arcor.de> wrote:

> → PROJ.4 / #14126
> After setting -DLIBPROJ4_INCLUDE_DIR=/usr/include and
> -DLIBPROJ4_LIBRARIES=/usr/lib/libproj.so.9.1.0 (or to the linker name
> ./libproj.so only) VTK commit 981a1e1 compiled flawlessly against both
> PROJ.4 release 4.9.2 and commit 06a708d.
> Both headers and shared libraries of various other dependencies like
> netCDF-C++ legacy, GDAL or GL2PS are found automatically at the very same
> locations, though. Some of them where used by path /usr/lib64 which is a
> symbolic link to /usr/lib on Arch Linux which shouldn't matter with regards
> to PROJ.4, IMO.
> So all in all I still think a but in VTK regarding PROJ.4 remains and the
> question is whether a new one should be opened or #14126 should be
> continued.
>
> → netCDF-C++ / #15549
>
>> I've changed this to backlog.
>>
> That's pretty good. The dependency on that legacy version should be
> removed in the long run. It doesn't offer all features of the current API
> besides this probably wasn't relevant for VTK yet.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/vtk-developers/attachments/20160729/89a152d4/attachment.html>