<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Greetings Simon,<br>
<br>
The reason is simple: because the official builds of ParaView are
usually done with MSVC 2008:
<a class="moz-txt-link-freetext" href="http://www.paraview.org/Wiki/ParaView_Binaries">http://www.paraview.org/Wiki/ParaView_Binaries</a><br>
If we didn't use that version, it would lead to conflicts with the
runtime libraries used by the official ParaView binaries versus
the plug-ins built using the SDK we've provided.<br>
<br>
Best regards,<br>
Bruno<br>
<br>
On 08-08-2014 16:25, Su, Simon M CTR USARMY ARL (US) wrote:<br>
</div>
<blockquote
cite="mid:F02E4EC9F4B4BA4189BBDC8BF3B2AD822549BC1B@umechp9h.easf.csd.disa.mil"
type="cite">
<pre wrap="">Classification: UNCLASSIFIED
Caveats: NONE
Hi Bruno,
Can I ask why you picked MSVC 2008 C++ Express version over MSVC 2013 C++
Express version to do the compilation?
Thanks
-simon
-----Original Message-----
From: ParaView [<a class="moz-txt-link-freetext" href="mailto:paraview-bounces@paraview.org">mailto:paraview-bounces@paraview.org</a>] On Behalf Of Bruno
Santos
Sent: Wednesday, August 06, 2014 8:59 AM
To: <a class="moz-txt-link-abbreviated" href="mailto:paraview@paraview.org">paraview@paraview.org</a>
Subject: [Paraview] [ParaView] Unofficial ParaView 4.1.0 SDK for Windows 32
and 64-bit
Greetings to all!
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#Par">https://code.google.com/p/unofficial-paraview-dev-install/wiki/Downloads#Par</a>
aView_4.1.0
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>
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/vtkPOFFReader">https://code.google.com/p/unofficial-paraview-dev-install/wiki/vtkPOFFReader</a>
Builds
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.
Furthermore, here's a bit of a back story and the current status of this
endeavour:
* 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.
* 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.
* 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.
* 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.
* 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.
* 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>
* 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:
* <a class="moz-txt-link-freetext" href="http://review.source.kitware.com/#/t/4487/">http://review.source.kitware.com/#/t/4487/</a>
* <a class="moz-txt-link-freetext" href="http://review.source.kitware.com/#/t/4488/">http://review.source.kitware.com/#/t/4488/</a>
* 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.
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 ;)
If anyone has any questions, feel free to ask!
Best regards,
Bruno Santos
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.
Classification: UNCLASSIFIED
Caveats: NONE
</pre>
</blockquote>
<br>
<br>
<div class="moz-signature">
<p>-- <br>
<a href="http://bluecape.com.pt">http://www.bluecape.com.pt </a></p>
<p><a href="http://bluecape.com.pt/Facebook"><img
alt="blueCAPE@Facebook" title="blueCAPE@Facebook"
src="cid:part2.02070100.09090505@bluecape.com.pt" border="0"
height="25" width="25"></a> <a
href="http://bluecape.com.pt/LinkedIn"><img
alt="blueCAPE@LinkedIn" title="blueCAPE@LinkedIn"
src="cid:part4.01050007.08010800@bluecape.com.pt" border="0"
height="25" width="25"></a> <a
href="http://bluecape.com.pt/Twitter"><img
alt="blueCAPE@Twitter" title="blueCAPE@Twitter"
src="cid:part6.07070709.03040907@bluecape.com.pt" border="0"
height="25" width="25"></a> <a
href="http://bluecape.com.pt/g+"><img alt="blueCAPE@Google+"
title="blueCAPE@Google+"
src="cid:part8.07070801.08050209@bluecape.com.pt" border="0"
height="25" width="25"></a> <a
href="http://bluecape.com.pt/YouTube"><img
alt="blueCAPE@YouTube" title="blueCAPE@YouTube"
src="cid:part10.02020309.01000301@bluecape.com.pt"
border="0" height="25" width="25"></a> <a
href="http://bluecape.com.pt/RSS"><img alt="blueCAPE RSS"
title="blueCAPE RSS"
src="cid:part12.04030004.07030503@bluecape.com.pt"
border="0" height="25" width="25"></a></p>
<p>blueCAPE Lda - CAE solutions<br>
Rua Fonte dos Corvos, n.29<br>
Casais da Serra<br>
2665-305 Milharado<br>
PORTUGAL<br>
<br>
(+351) 219 755 345 Tel.<br>
(+351) 219 755 345 Fax<br>
(+351) 926 008 657 Mob.</p>
</div>
</body>
</html>