<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 11/8/18 3:15 PM, David Gobbi wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CANwS1=HUyPfL24emMeXFOiuNpz2OungbZ+7WT28JUQ3oHr6Bjg@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div class="gmail_quote">
<div dir="ltr">On Thu, Nov 8, 2018 at 12:18 PM Ben Boeckel
<<a href="mailto:ben.boeckel@kitware.com" target="_blank"
moz-do-not-send="true">ben.boeckel@kitware.com</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
> * Building any VTK module either externally or along
with the VTK project<br>
> ? (e.g this will be useful for creating python wheels)<br>
<br>
I'm not sure the use case is clear to me. How are Python
wheels related<br>
to remote modules?<br>
</blockquote>
<div><br>
</div>
<div>Package managers like to be able to subdivide VTK into
multiple packages.</div>
<div>Being able to modularize the build itself, so that VTK
can be built kit-by-kit</div>
<div>instead of all at once, is a logical extension of the
multiple package idea.</div>
<div>If I recall correctly, the CI system for pypi was failing
to build VTK due to</div>
<div>timeouts (I'm not sure what the workaround was, I suspect
that Prabhu</div>
<div>built the wheels manually).</div>
</div>
</div>
</blockquote>
<p>Yes, I built the wheels with the VTKPythonPackage,
(<a class="moz-txt-link-freetext" href="https://github.com/KitwareMedical/VTKPythonPackage">https://github.com/KitwareMedical/VTKPythonPackage</a>), it is
largely automated but I did build it by hand and uploaded it. <br>
</p>
<p>I am not sure if this is still broken with 8.2 and hope to check
this weekend.<br>
</p>
<p>cheers,</p>
<p>Prabhu<br>
</p>
</body>
</html>