diff options
author | 2021-03-16 11:38:37 -0700 | |
---|---|---|
committer | 2021-03-16 11:38:37 -0700 | |
commit | 1bdaceebb8c8c244f68e1187ab03f46b9e763ff0 (patch) | |
tree | 83a06e47cd269902a8a5c30355b15850c7428f9e /Source/FieldSolver/FiniteDifferenceSolver | |
parent | 76ebee96eeabd7336c49c1250e255db59ec0d971 (diff) | |
download | WarpX-1bdaceebb8c8c244f68e1187ab03f46b9e763ff0.tar.gz WarpX-1bdaceebb8c8c244f68e1187ab03f46b9e763ff0.tar.zst WarpX-1bdaceebb8c8c244f68e1187ab03f46b9e763ff0.zip |
FFTW: CMakeConfig Support (#1765)
Modern FFTW versions support CMake as an install method, which
provides the legacy goodies (`.pc`) files and proper
`FFTW3(f)Config.cmake` files for dependency propagation.
Conda-forge uses the CMake-based method to deploy. Checking this,
I realized the `.pc` files add unconditionally `libm` to the linker,
which is wrong on Windows and fails the builds.
Thus, forward looking we would search first for CMake based installs
of FFTW and in case this search is not successful, we continue to
search for the old Autotools logic and `.pc` files, which are still
routinely generated by some package managers.
But, due to an issue in FFTW3 3.3.9 on Linux/macOS with Autotools
installs, we make `Config.cmake` file based search still opt-in for
now.
Diffstat (limited to 'Source/FieldSolver/FiniteDifferenceSolver')
0 files changed, 0 insertions, 0 deletions