Skip to content

WIP: Force FFTWF-only build on Pixi-Cxx CI (do not merge)#6331

Closed
hjmjohnson wants to merge 1 commit into
wip/fftwf-only-ci-buildfrom
wip/fftwf-only-ci-trigger
Closed

WIP: Force FFTWF-only build on Pixi-Cxx CI (do not merge)#6331
hjmjohnson wants to merge 1 commit into
wip/fftwf-only-ci-buildfrom
wip/fftwf-only-ci-trigger

Conversation

@hjmjohnson
Copy link
Copy Markdown
Member

WIP — do not merge. CI-only validation, stacked on #6330. This branch adds a single commit forcing the Pixi-Cxx CI leg to build single-precision FFTW only (ITK_USE_FFTWF=ON, ITK_USE_FFTWD=OFF, ITK_USE_SYSTEM_FFTW=OFF), exercising the FFTWF-only build path that #6330 fixes and the default dual-precision matrix never covers.

Base branch is wip/fftwf-only-ci-build (#6330's branch), so this PR's diff is exactly the WIP configure-ci change. Once the path is shown green, abandon this PR — it must never merge.

…FFTW

Set ITK_USE_FFTWF=ON, ITK_USE_FFTWD=OFF, ITK_USE_SYSTEM_FFTW=OFF in the
configure-ci task so the Pixi-Cxx CI leg builds the staged single-precision
FFTW and compiles ITKFFT against it. This exercises the FFTWF-only code paths
fixed by the two preceding commits, which the default dual-precision build
masks. Not for merge.
@hjmjohnson
Copy link
Copy Markdown
Member Author

Consolidated into #6330, which now carries the CI-validation commit directly (and the real compile fix it surfaced). Closing this stacked PR.

@hjmjohnson hjmjohnson closed this May 22, 2026
@hjmjohnson hjmjohnson deleted the wip/fftwf-only-ci-trigger branch May 22, 2026 18:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant