[vtkusers] ANNOUNCE: vtk 6.0.0.rc1 is available to download

[Dženan Zukić]

I get compile errors with RC1. 163 projects built OK and 10 failed. Most
common error was "cannot include vtkTestDriver.h". Below is a small sample
of errors. Machine: Win7x64 + VS2010SP1.

6>D:/SDK/vtk-6.0.0/Testing/Rendering/vtkTestingObjectFactory.h(38): fatal
error C1083: Cannot open include file: 'vtkTestDriver.h': No such file or
directory
7>D:\SDK\vtk-6.0.0\Rendering\HybridOpenGL\Testing\Cxx\TestSurfaceLIC.h(27):
fatal error C1083: Cannot open include file: 'vtkRegressionTestImage.h': No
such file or directory
8>D:\SDK\vtk-6.0.0\Rendering\HybridOpenGL\Testing\Cxx\TestStructuredGridLIC2DSlice.h(29):
fatal error C1083: Cannot open include file: 'vtkTestUtilities.h': No such
file or directory


On Mon, May 20, 2013 at 10:24 PM, David E DeMarle
<dave.demarle at kitware.com>wrote:

> Kitware and the VTK team are happy to announce that VTK 6.0 has
> entered the release candidate stage!
>
> You can find the source and data packages here:
> http://www.vtk.org/VTK/resources/software.html#cand
>
> The big news in this release is that VTK has been refactored from a large
> monolithic resource consisting of 19 tightly bound "kits" into a still
> large but now composeable resource consisting of 160 loosely bound
> "modules". Now applications can be built using just the source code for the
> small portions of the VTK library that they actually use instead of the
> whole million plus line enchilada. Conversely, it is easier than ever now
> to add new capabilities to VTK by writing small self-contained external
> modules.
>
> To refactor VTK, we started by cleanly separating VTK's Executive and
> DataObject classes. You may notice this first in the way that
> vtkAlgorithm::SetInput() has now been replaced by
> vtkAlgorithm::SetInputConnection() for connecting Algorithms together and
> vtkAlgorithm::SetInputData() for feeding DataObjects directly into
> Algorithms.
>
> Next, we modernized our CMake build system scripts by sorting the classes
> into small functional groups, removing all of the configure time behavioral
> changes, and replacing the dated KitCommonBlock CMake macros with
> vtkModuleMacro CMake macros to define the content and dependencies of each
> functional group. You may notice this first in the way that platform
> specific classes, such as vtkXRenderWindowInteractor, are not produced
> automatically by calls to vtkRenderWindowInteractor::New() anymore, unless
> CMake knows that your code requires the RenderingOpenGL implementation of
> the RenderingCore module.
>
> For full guideline to upgrading your application from VTK 5.x to VTK 6.x,
> please see the VTK migration guides at:
> http://www.vtk.org/Wiki/VTK/VTK_6_Migration/Overview,
> http://www.vtk.org/Wiki/VTK/Build_System_Migration and
> http://www.vtk.org/Wiki/VTK/Module_Development
>
> Besides modularization, VTK has the usual spate of new features, bug fixes
> and cleanups. These items will be summarized when VTK 6.0.0 final is
> released in a few days time.
>
> The attachment has a complete list of changes in this release
> candidate since VTK5.10.1. Please try this version of VTK and
> report any issues to the list or the bug tracker so that we can try to
> address them before VTK 6.0.0 final.
>  David E DeMarle
> Kitware, Inc.
> R&D Engineer
> 21 Corporate Drive
> Clifton Park, NY 12065-8662
> Phone: 518-881-4909
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the VTK FAQ at:
> http://www.vtk.org/Wiki/VTK_FAQ
>
> Follow this link to subscribe/unsubscribe:
> http://www.vtk.org/mailman/listinfo/vtkusers
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.vtk.org/pipermail/vtkusers/attachments/20130522/4bf33548/attachment.htm>