This is not a change request, I'm just curious as to how "transparent" these changes are: Do the changes in this PR require that we do this for all downstream consumers? Could we leave find_package(suitesparse CONFIG REQUIRED) and do the find_package updates in a follow-up PR? Sign ...
Could not find a package configuration file provided by "LAPACK" with any of the following names: LAPACKConfig.cmake lapack-config.cmake set the CMake variable LAPACK_DIR to SP_ROOT/lapack_windows/x64/ (or x32 for 32bit builds). 4. Why did you create this project? Porting SuiteSparse...
Could not find a package configuration file provided by "LAPACK" with any of the following names: LAPACKConfig.cmake lapack-config.cmake set the CMake variableLAPACK_DIRtoSP_ROOT/lapack_windows/x64/(orx32for 32bit builds). 4. Why did you create this project?
Or, since the tests are not required for proper functioning of the library, it could be ignored. I've just pushed a fix for this on mac and linux by adding the appropriate rpath to the build arguments. Note that on Mac this won't completely take effect until you've rebuilt all of de...
I didn't check the dependency structure, but maybe openmp or cuda choices could be controlled by a single "early" port? suitesparse-config would be a good place for it, I agree. Enabling OpenMP there does not transitively enable it for all other components depending on it, though. It only...
message(STATUS "Could not find librt, but found SuiteSparse_config, " "assuming that SuiteSparse was compiled without timing.") endif () endif (CMAKE_SYSTEM_NAME MATCHES "Linux" OR UNIX AND NOT APPLE) else() # Failed to find SuiteSparse_config (>= v4 installs), instead look for # UF...