Erik Schnetter

The build script is contained in the file `build_tarballs.jl` at https://github.com/JuliaPackaging/Yggdrasil/tree/38a8c9dd73fae3b39ec76fee0bb96162a1b6f138/A/ADIOS2 in the string variable `script`. The patches we are applying are located in the directory `bundled/patches` in the same...

The toolchains are located as https://github.com/JuliaPackaging/Yggdrasil/tree/master/B/BaseCompilerShard/cmake_toolchains . The `gcc` one should be the default.

@vicentebolea We cross-build. The ADIOS2 build script is here https://github.com/JuliaPackaging/Yggdrasil/tree/master/A/ADIOS2 ; it's a Julia script setting things up and containing a shell script for the actual build for all platforms....

@vicentebolea I found the Dockerfile that defines the Windows image: https://github.com/JuliaCI/rootfs-images/blob/main/windows/package-x86_64/Dockerfile .

Ah, rats. That's what the `This file is automatically generated. Do not edit!` refers to!

Thanks for the feedback and the pointers so far. Current state: Trying to track down allocation errors ``` From worker 2: WARNING: Error while freeing DeviceMemory(128.000 KiB at 0x000000193e084800): From...

This is ready for a review. I understand that the changes are larger than expected. I essentially removed all (internal) support for the previous `cufftType`, which required explicit code paths...

CI fails because it times out before it reaches the CUFFT tests.

Thanks. The problem was that the input array was converted to the output type of the plan instead of the expected input type. (Those differ for real->complex transforms.)

@maleadt I scoured the documentation for cuFFT (https://docs.nvidia.com/cuda/cufft/index.html). I find these statements: - (2.7) "Every cuFFT plan may be associated with a CUDA stream." - (2.8.1) "In the single GPU...