When cross-compiling on a cluster I noticed the following: If I want to select a specific SuiteSparse installation and I set SuiteSparse_ROOT this path is not propagated to the suite sparse components. If there are suitesparse components available in some system path then find_package(SuiteSparse) will find those first before the components that belong to the selected suitesparse installation. I think we should make sure to only look in the same folder as suitesparseconfig as otherwise we cannot guarantee that component libraries and suitesparse are compatible.
