<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Greetings to all!<br>
<br>
We at blueCAPE have made available an unofficial SDK of ParaView
4.1.0 for Windows 32 and 64-bit, based on the official SuperBuild
and respective build options. It's available here:
<a class="moz-txt-link-freetext" href="https://code.google.com/p/unofficial-paraview-dev-install/wiki/Downloads#ParaView_4.1.0">https://code.google.com/p/unofficial-paraview-dev-install/wiki/Downloads#ParaView_4.1.0</a><br>
Instructions on how these packages were built is provided here:
<a class="moz-txt-link-freetext" href="https://code.google.com/p/unofficial-paraview-dev-install/wiki/Notes410">https://code.google.com/p/unofficial-paraview-dev-install/wiki/Notes410</a><br>
<br>
According to our tests, it's possible to use this SDK to build
plug-ins and any other associated applications, which will work with
the respective official ParaView 4.1.0 builds for Windows. A proof
of concept we've used is the vtkPOFFReader plug-in which was
successfully built with these SDK packages:
<a class="moz-txt-link-freetext" href="https://code.google.com/p/unofficial-paraview-dev-install/wiki/vtkPOFFReaderBuilds">https://code.google.com/p/unofficial-paraview-dev-install/wiki/vtkPOFFReaderBuilds</a><br>
<br>
Note: We roughly used the same development environment as the
original ParaView 4.1.0 binaries for Windows:
<a class="moz-txt-link-freetext" href="http://www.paraview.org/Wiki/ParaView_Binaries">http://www.paraview.org/Wiki/ParaView_Binaries</a> - although we've used
MSVC 2008 C++ Express and did not have a respective FORTRAN compiler
(which requires the Professional version either way), which is why
we needed to do some adjustments to build Open-MPI with success.<br>
<br>
Furthermore, here's a bit of a back story and the current status of
this endeavour:<br>
<ul>
<li>Back in January 2012 we at blueCAPE began to try to bring back
the development installers of ParaView for Windows, which was
last officially available for ParaView 3.8.1.</li>
<li>The overall features available in the development installers
we created were still missing important files, because we were
still basing ourselves on the infrastructure that was still
remnant from ParaView 3.8.1.</li>
<li>Nonetheless, we made available our findings and builds for
ParaView 3.12.0, 3.14.0, 3.14.1 and 3.98.0, where the last
release we managed to build was back in January 2013.<br>
</li>
<li>ParaView fortunately kept evolving since then. We missed the
versions 3.98.1 and 4.0.1, due to time constraints on our side
and a few failed builds.</li>
<li>As far as we can see, ParaView 4.1.0 already has a pretty good
SDK structure which evolved overtime. The official SuperBuild
repository also already provides many of the necessary features
for making the SDK releases, at least for the Unix-like
environments.</li>
<li>This Summer 2014 we at blueCAPE finally managed to get around
back to trying and adjust the SuperBuild settings to build and
deliver a ParaView 4.1.0 SDK for Windows and believe we have
successfully achieved it. The changes have been shared and
referenced in the following wiki page at our project:
<a class="moz-txt-link-freetext" href="https://code.google.com/p/unofficial-paraview-dev-install/wiki/Notes410">https://code.google.com/p/unofficial-paraview-dev-install/wiki/Notes410</a></li>
<li>In addition to this, after some reviewing and building tests
with the latest commits on the master branch from the SuperBuild
repository, we have adapted most of the changes we've developed
for the SDK build above and have submitted two commits to
Kitware Gerrit, namely:<br>
</li>
<ul>
<li><a class="moz-txt-link-freetext" href="http://review.source.kitware.com/#/t/4487/">http://review.source.kitware.com/#/t/4487/</a></li>
<li><a class="moz-txt-link-freetext" href="http://review.source.kitware.com/#/t/4488/">http://review.source.kitware.com/#/t/4488/</a></li>
</ul>
<li>We haven't managed to create the NSIS and ZIP packages through
CMake/CPack, but our main concern has mostly been on having a
working SDK.</li>
</ul>
Hopefully this can help bring sooner the ParaView SDK in future
versions in a more official way... so that we won't have to look
into generating the NSIS/ZIP packages ourselves, nor build Qt 4.8.6
;)<br>
<br>
If anyone has any questions, feel free to ask!<br>
<br>
Best regards,<br>
Bruno Santos<br>
<br>
PS: I haven't sent this email to the ParaView Developers mailing
list simply because previous emails I've sent on this topic have
been to this main mailing list.
<div class="moz-signature"><br>
</div>
</body>
</html>