, vtkm::cont::StorageTagBasic\> const&, vtkm::filter::FieldMetadata const&, vtkm::filter::PolicyBasevtkm::filter::PolicyDefault)’
collect2.exe: error: ld returned 1 exit status
mingw32-make[2]: \*\*\* [Accelerators\Vtkm\Filters\CMakeFiles\AcceleratorsVTKmFilters.dir\build.make:499: bin/libvtkAcceleratorsVTKmFilters-9.1.dll] Error 1
mingw32-make[1]: \*\*\* [CMakeFiles\Makefile2:16044: Accelerators/Vtkm/Filters/CMakeFiles/AcceleratorsVTKmFilters.dir/all] Error 2
mingw32-make: \*\*\* [Makefile:135: all] Error 2
---
### Author:  [@ben.boeckel](https://discourse.vtk.org/u/ben.boeckel)
#### Post date: [November 24, 2021, 3:05pm UTC](https://discourse.vtk.org/t/mingw-compile-error-for-vtkm/7265/2 "2021-11-24T15:05:59Z")
I don’t think VTK-m is well-tested with MinGW (not that VTK is either).
@jschueller Have you managed to compile VTK-m with MinGW?
Cc: @vbolea
---
### Author:  [@jschueller](https://discourse.vtk.org/u/jschueller)
#### Post date: [November 24, 2021, 3:14pm UTC](https://discourse.vtk.org/t/mingw-compile-error-for-vtkm/7265/3 "2021-11-24T15:14:04Z")
No, I always disable it.
---
### Author:  [@lassoan](https://discourse.vtk.org/u/lassoan)
#### Post date: [November 26, 2021, 3:28am UTC](https://discourse.vtk.org/t/mingw-compile-error-for-vtkm/7265/4 "2021-11-26T03:28:58Z")
You will probably run into many issues at all stages (development, build, run, test, package) if you try to use mingw instead of a Visual Studio build toolset. With the help of CMake you can develop code that is compiled using the best supported build toolset on each platform.
---
### Author:  [@jschueller](https://discourse.vtk.org/u/jschueller)
#### Post date: [November 26, 2021, 12:58pm UTC](https://discourse.vtk.org/t/mingw-compile-error-for-vtkm/7265/5 "2021-11-26T12:58:56Z")
let me disagree. vtk (and paraview) works generally fine with mingw except for minor compilation problems from time to time. that’s understandable because upstream does not support it.
---
### Author:  [@lassoan](https://discourse.vtk.org/u/lassoan)
#### Post date: [November 26, 2021, 1:56pm UTC](https://discourse.vtk.org/t/mingw-compile-error-for-vtkm/7265/6 "2021-11-26T13:56:23Z")
I believe you that things are expected to _mostly work_ if you use mingw for development on Windows, but things are expected to _work_ if you use MSVC because magnitudes more people use it (and so any errors are found and fixed sooner, more convenience features are available, etc.).
---
### Author:  [@ben.boeckel](https://discourse.vtk.org/u/ben.boeckel)
#### Post date: [November 26, 2021, 4:19pm UTC](https://discourse.vtk.org/t/mingw-compile-error-for-vtkm/7265/7 "2021-11-26T16:19:44Z")
Yes, this is the difference between “supported” and “patches accepted”. Julien is a valued contributor by verifying MinGW support for VTK and ParaView that we just do not have the resources allocated to continually verify.
---
### Author:  [@rockydut](https://discourse.vtk.org/u/rockydut)
#### Post date: [November 30, 2021, 2:25am UTC](https://discourse.vtk.org/t/mingw-compile-error-for-vtkm/7265/8 "2021-11-30T02:25:11Z")
I add one new file in ThirdParty\vtkm\vtkvtkm\vtk-m\vtkm\filter. I named it GradientPoints.cxx. Then the vtkm can be compiled. It’s great.
The code is:
// the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR
// PURPOSE. See the above copyright notice for more information.
//============================================================================
#ifndef vtk\_m\_filter\_Gradient\_point\_cxx
#define vtk\_m\_filter\_Gradient\_point\_cxx
#include \
#include \
namespace vtkm
{
namespace filter
{
template VTKM\_FILTER\_GRADIENT\_TEMPLATE\_EXPORT vtkm::cont::DataSet Gradient::DoExecute(
const vtkm::cont::DataSet&,
const vtkm::cont::ArrayHandle\, vtkm::cont::StorageTagBasic\>&,
const vtkm::filter::FieldMetadata&,
vtkm::filter::PolicyBasevtkm::filter::PolicyDefault);
template VTKM\_FILTER\_GRADIENT\_TEMPLATE\_EXPORT vtkm::cont::DataSet Gradient::DoExecute(
const vtkm::cont::DataSet&,
const vtkm::cont::ArrayHandle\, vtkm::cont::StorageTagSOA\>&,
const vtkm::filter::FieldMetadata&,
vtkm::filter::PolicyBasevtkm::filter::PolicyDefault);
}
}
#endif