[Paraview-developers] Superbuild cpack
Ben Boeckel
ben.boeckel at kitware.com
Fri Dec 15 16:23:51 EST 2017
On Fri, Dec 15, 2017 at 16:43:31 +0000, Michal Wozniak wrote:
> vtkpqApplicationComponents-pv1.0.dll
> vtkUtilitiesPythonInitializer-pv1.0.dll
> vtkpqComponents-pv1.0.dll
> vtkpqPython-pv1.0.dll
> vtkpqCore-pv1.0.dll
> vtkpqWidgets-pv1.0.dll
So these are the missing ones...
> QtTesting.dll
> vtkPVServerManagerDefault-pv1.0.dll
> vtkPVServerManagerCore-pv1.0.dll
> vtkPVClientServerCoreRendering-pv1.0.dll
> vtkPVClientServerCoreCore-pv1.0.dll
> vtkPVCommon-pv1.0.dll
> Qt5Widgets.dll
> Qt5Gui.dll
> Qt5Network.dll
> Qt5Core.dll
> vtksys-pv1.0.dll
> USER32.dll
> MSVCP140.dll
> dwmapi.dll
> WTSAPI32.dll
> VCRUNTIME140.dll
> api-ms-win-crt-heap-l1-1-0.dll
> api-ms-win-crt-environment-l1-1-0.dll
> api-ms-win-crt-locale-l1-1-0.dll
> api-ms-win-crt-runtime-l1-1-0.dll
> api-ms-win-crt-string-l1-1-0.dll
> api-ms-win-crt-math-l1-1-0.dll
> api-ms-win-crt-stdio-l1-1-0.dll
> KERNEL32.dll
> SHELL32.dll
...but these are installed (well, except for some system ones)?
If you look at the output from CPack, is there anything mentioning
the missing libraries that looks like an error of some kind that isn't
being caught as an error?
--Ben
More information about the Paraview-developers
mailing list