(Array1T *,Array2T *) const' being compiled
35> with
35> [
35> Array1T=vtkDataArray,
35> Array2T=vtkDataArray
35> ]
```
Would it be possible to move back implicit arrays into their own `CommonImplicitArrays` component as it was before?
If that was impractical, could someone provide CMake flags that allow building VTK without implicit arrays?
@spyridon97 @ben.boeckel
---
### Author:  [@spyridon97](https://discourse.vtk.org/u/spyridon97)
#### Post date: [April 21, 2025, 4:34pm UTC](https://discourse.vtk.org/t/vtk-9-4-debug-build-fails-with-msvc-due-to-image-size-exceeds-maximum-allowable-size/15520/2 "2025-04-21T16:34:09Z")
By default, all the implicit arrays are not dispatched with the exception of vtkStructuredPointsArray which is used internally in vtkImageData, vtkRectilinearGrid.
They can’t be deactivated from compiling since they are part of common core.
We moved it into common core, because it created a lot of extra includes and spagheti code, if this does not exist, use the other, and such. Plus all arrays should belong to the same module. I tried to create a CommonArrays module, but it did not work because of internal cyclic dependencies with vtkVariant which in turn depends on vtkInformationKey (or something like that, it’s been 2 years since i worked on this).
I personally see 2 potential solutions.
1. Actually, implement the CommonArray module, but i don’t know if that will affect the kits compilation.
2. Understand why windows does not work and Linux does (i hope). Is there something that we can pass to the compiler to reduce the size, or something that linux passed which reduces the size?
---
### Author:  [@Paulo\_Carvalho](https://discourse.vtk.org/u/Paulo_Carvalho)
#### Post date: [April 21, 2025, 7:08pm UTC](https://discourse.vtk.org/t/vtk-9-4-debug-build-fails-with-msvc-due-to-image-size-exceeds-maximum-allowable-size/15520/3 "2025-04-21T19:08:10Z")
Hello,
Perhaps enabling some optimization in debug mode, by setting `CMAKE_CXX_FLAGS_DEBUG` to `/O2` when configuring the build with CMake. Reference: [/O options (Optimize code) | Microsoft Learn](https://learn.microsoft.com/en-us/cpp/build/reference/o-options-optimize-code?view=msvc-170). Try to find one that reduces the executable size to just under the limit while minimizing impact on debugging capabilities or profiling accuracy.
best,
PC
---
### Author:  [@spyridon97](https://discourse.vtk.org/u/spyridon97)
#### Post date: [April 21, 2025, 8:25pm UTC](https://discourse.vtk.org/t/vtk-9-4-debug-build-fails-with-msvc-due-to-image-size-exceeds-maximum-allowable-size/15520/4 "2025-04-21T20:25:32Z")
A quick way to test your idea is to try RelWithDebInfo.
---
### Author:  [@lassoan](https://discourse.vtk.org/u/lassoan)
#### Post date: [April 21, 2025, 10:30pm UTC](https://discourse.vtk.org/t/vtk-9-4-debug-build-fails-with-msvc-due-to-image-size-exceeds-maximum-allowable-size/15520/5 "2025-04-21T22:30:52Z")
`RelWithDebInfo` and other optimized builds are not replacements for a `Debug` build, as they severely limit debugging (methods are removed, lines are skipped, code is not executed in order, variables are inaccessible, etc.).
> By default, all the implicit arrays are not dispatched with the exception of vtkStructuredPointsArray which is used internally in vtkImageData, vtkRectilinearGrid.
I see that most of the `VTK_DISPATCH_..._ARRAYS` CMake variables are set to `OFF`, but I’m not sure if they are effective.
As I wrote above, when I built with default options, .obj files were created not just `vtkStructuredPointArray` (447MB of .obj files), but also for `vtkAffineArray` (413MB), `vtkCompositeArray` (692MB), `vtkConstantArray` (241MB), `vtkIndexedArray` (717MB), `vtkStdFunctionArray` (241MB), `vtkTypedDataArray` (233MB).
Considering their enormous size, would it be possible to add CMake options to remove instantiations of these rarely used types?
---
### Author:  [@spyridon97](https://discourse.vtk.org/u/spyridon97)
#### Post date: [April 22, 2025, 3:22pm UTC](https://discourse.vtk.org/t/vtk-9-4-debug-build-fails-with-msvc-due-to-image-size-exceeds-maximum-allowable-size/15520/6 "2025-04-22T15:22:02Z")
We will discuss how to resolve this issue internally, and let you know.
---
### Author:  [@ben.boeckel](https://discourse.vtk.org/u/ben.boeckel)
#### Post date: [April 22, 2025, 3:54pm UTC](https://discourse.vtk.org/t/vtk-9-4-debug-build-fails-with-msvc-due-to-image-size-exceeds-maximum-allowable-size/15520/7 "2025-04-22T15:54:01Z")
> [@lassoan](#):
>
> Debug build of VTK-9.4 fail on Windows if `VTK_ENABLE_KITS` is enabled, with this error
That limit smells of a 32bit build. It looks like it _should_ be, but could you please confirm that this is indeed a 64-bit build.
---
### Author:  [@lassoan](https://discourse.vtk.org/u/lassoan)
#### Post date: [April 22, 2025, 4:51pm UTC](https://discourse.vtk.org/t/vtk-9-4-debug-build-fails-with-msvc-due-to-image-size-exceeds-maximum-allowable-size/15520/8 "2025-04-22T16:51:31Z")
Yes, it is a 64-bit build. See the full build command in the first post.
---
### Author:  [@mwestphal](https://discourse.vtk.org/u/mwestphal)
#### Post date: [June 5, 2025, 3:16pm UTC](https://discourse.vtk.org/t/vtk-9-4-debug-build-fails-with-msvc-due-to-image-size-exceeds-maximum-allowable-size/15520/9 "2025-06-05T15:16:55Z")
Fixed in VTK master 🙂
[https://gitlab.kitware.com/vtk/vtk/-/merge\_requests/12133](https://gitlab.kitware.com/vtk/vtk/-/merge_requests/12133)
Thanks a lot @alexy.pellegrini !
---
### Author:  [@lassoan](https://discourse.vtk.org/u/lassoan)
#### Post date: [June 7, 2025, 2:14pm UTC](https://discourse.vtk.org/t/vtk-9-4-debug-build-fails-with-msvc-due-to-image-size-exceeds-maximum-allowable-size/15520/10 "2025-06-07T14:14:10Z")
Awesome, thank you very much for everyone’s work on this!