vtk relies heavily on cmake, so it does not support pkg-config or autotools
explicitly.
what it provides is a VTKConfig.cmake generated during the
configuration/installation.
inquiring it with this CMakeLists.txt
find_package(VTK)
message("VTK_DEFINITIONS = ${VTK_DEFINITIONS}")
message("VTK_LIBRARIES = ${VTK_LIBRARIES}")
message("VTK_INCLUDE_DIRS = ${VTK_INCLUDE_DIRS}")
message("VTK_LIBRARY_DIRS = ${VTK_LIBRARY_DIRS}")
gives all the relevant information (there is also a UseVTK.cmake that
automates this).
I do not see a way to parse the cmake files to get those flags in a easy
way without depending on cmake.
the easy way I see is to make vtk.m4 test with and without extension for
the set of libraries, and rely on the user to properly set
--with-vtk-include and --with-vtk-lib during configuration.
my experience with autotools is very limited, but I will try to prepare a
patch.
On Wed, 7 Oct 2015 at 16:19 Roy Stogner <royst...@ices.utexas.edu> wrote:
>
> On Wed, 7 Oct 2015, John Peterson wrote:
>
> > Do you think it's worth trying to actually support the distros' alternate
> > naming scheme in libmesh's m4 files? I don't think it would be too
> > difficult. Other than Arch and Fedora, are there any others that do
> this?
>
> It's not a crazy alternate scheme. I've no time to add support but if
> anyone else wanted to I'd be thrilled.
> ---
> Roy
>
------------------------------------------------------------------------------
Full-scale, agent-less Infrastructure Monitoring from a single dashboard
Integrate with 40+ ManageEngine ITSM Solutions for complete visibility
Physical-Virtual-Cloud Infrastructure monitoring from one console
Real user monitoring with APM Insights and performance trend reports
Learn More http://pubads.g.doubleclick.net/gampad/clk?id=247754911&iu=/4140
_______________________________________________
Libmesh-users mailing list
Libmesh-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmesh-users
