VTK 8.1

[ShamanTcler]

Now that Bincrafters has a viable Qt offering, the next layer lib is VTK with the Qt option turned on.

[bilke]

I recently made this: https://github.com/bilke/conan-vtk/tree/stable/8.1.1

[ShamanTcler]

Lars ... thanks for the prompt reply, but this is where I get picky, particular, or just a pain in the butt.

I am stuck in a "enterprise" environment, so to work with 3'rd party tools I will need a MSVS 2015, 64 bit, Qt 5.9 (version. 5.9 is one of Qt's long term support versions 5.11 is not).

Now I also see your dependency on Qt/5.11.0@bilke/stable, curious, could this just be replaced with qt/5.9.8@bincrafters/stable and rebuilt?

Being in an enterprise I end up with quite a stack of intertwined libraries, so insuring they all share common dependencies is important. When I say intertwined I mean I may have say two layers of Open source:

Using the dot language format Vtk ->Qt QtCsv ->Qt Ourlib ->Vtk OurLib -> QtCsv

So I think I am looking to bincrafters / Conan to weave a consistent view.

With that said does it seem reasonable to build off of your work and see if Bincrafters will adopt it?

If I am all confused and turned around please set me straight.

Best regards and thanks again for the comments

[lucasahli]

+1

[Croydon]

@lucasahli Please use GitHub reactions, +1 spam is just flooding everyone's inbox :)

[Croydon]

There is also https://github.com/danimtb/conan-vtk

[barcharcraz]

I have a rpm spec file sitting around if that's helpful. Do yourself a favor and install ccache before starting this one :D

[Morwenn]

I tried to build VTK 8.1.2 using the unmodified recipe from denimtb and had an issue because some of the modules rely on netCDF, so it might be another library worth packaging in the process.

[bilke]

@Morwenn I am currently in the process of creating a netCDF package. I will post my results here...

[Morwenn]

The following optional dependencies are already available either on conan-center or bincrafters and can be used to minimize the number of 3rd parties VTK has to ship & build:

• Expat/2.2.6@pix4d/stable
• freetype/2.9.1@bincrafters/stable
• glew/2.1.0@bincrafters/stable (though that one didn't always work)
• libjpeg/9c@bincrafters/stable
• jsoncpp/1.8.4@theirix/stable
• libxml2/2.9.9@bincrafters/stable
• lz4/1.8.3@bincrafters/stable
• libpng/1.6.36@bincrafters/stable
• libtiff/4.0.9@bincrafters/stable
• zlib/1.2.11@conan/stable

All those libraries should be used by VTK whenever a corresponding VTK_USE_SYSTEM_* CMake option is given to VTK.

I had to make sure some of the libraries were built specifically with fPIC (or shared for those who don't support the fPIC option directly) to make sure everything built correctly. I'm not sure whether this issue is due to the way I build my projects.