[vtkusers] vcpkg

[Dženan Zukić]

If there is no undergoing effort to "port" VTK to vcpkg, we could go ahead
and add ITK with VTKGlue disabled. Once VTK is added, we could turn on
VTKGlue and make VTK a dependency.

P.S. I originally cross-posted this to ITK and VTK developers lists, but
since I am only subscribed to VTK-users my message was bounced from
VTK-developers. Hence this "merge" message including Francois' response.


Francois Budin
9:45 AM (52 minutes ago)
to me, vtk-developers, ITK
Never heard of it before. It does look interesting. We could try to
estimate how much work it would be to port ITK (and VTK?)  to that
platform. Since it supports CMake [1], it may not be much work.

Francois

[1] https://github.com/Microsoft/vcpkg/blob/master/docs/
EXAMPLES.md#example-1-2-b


On Tue, Jan 10, 2017 at 10:15 AM, Ben Boeckel <ben.boeckel at kitware.com>
wrote:

> On Mon, Jan 09, 2017 at 18:58:40 -0500, Dženan Zukić wrote:
> > vcpkg
> > <https://blogs.msdn.microsoft.com/vcblog/2016/09/19/vcpkg-a-
> tool-to-acquire-and-build-c-open-source-libraries-on-windows/>
> > looks
> > like a good effort for easing library installation for usage in Visual
> > Studio. Should we join the effort by adding ITK and VTK? Has anyone
> > tried/started doing this?
>
> CPack would likely need to support it first. Moving VTK over to the new
> superbuild would also help there.
>
> --Ben
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/vtkusers/attachments/20170110/680d4234/attachment.html>