paraview: add viskores in newer versions#828
Conversation
kmorel
force-pushed
the
paraview-viskores
branch
from
1772dba to
6765f44
Compare
|
@kwryankrattiger Can you please review this? |
kmorel
force-pushed
the
paraview-viskores
branch
from
6765f44 to
dc4e687
Compare
kwryankrattiger
left a comment
kwryankrattiger
left a comment
There was a problem hiding this comment.
Sorry for taking so long on this, I have been back and forth on how best to handle this going forward.
It may be better to just prune this variant at enable the accelerator implicitly. And then external Viskores would be really nice to not have to rebuild it from scratch if we don't have to, especially for the GPU stuff.
kmorel
force-pushed
the
paraview-viskores
branch
from
dc4e687 to
c79002c
Compare
|
@kwryankrattiger I've updated this package to use an external viskores package. It also removes the I have not extensively tested this, but the spec at least works. |
kmorel
changed the title
kmorel
force-pushed
the
paraview-viskores
branch
2 times, most recently
from
048e346 to
d0612b8
Compare
kmorel
force-pushed
the
paraview-viskores
branch
2 times, most recently
from
fcf314e to
8a606eb
Compare
kmorel
force-pushed
the
paraview-viskores
branch
3 times, most recently
from
adcbac9 to
7f62338
Compare
|
Ported these changes to #192 with other ParaView 6 Updates |
Starting with ParaView 6.0, the VTK-m accelerator library changed to Viskores. Update the options to use the new accelerator library. The approach has changed slightly. Earlier there was a use_vtkm option to specify whether VTK-m should be compiled, and it always compiled the version provided with ParaView. However, the API for Viskores is stable, so use the external viskores package. Co-authored-by: Ryan Krattiger <80296582+kwryankrattiger@users.noreply.github.com>
kmorel
force-pushed
the
paraview-viskores
branch
from
7f62338 to
e21f146
Compare
2 participants
Starting with ParaView 6.0, the VTK-m accelerator library changed to Viskores. Update the options to use the new accelerator library.