Thanks, Joachim, for the report! This definitely sounds like an upstream bug. Would you mind reporting it on [1]? Together with the Trilinos devs, we'll be able to take it from there. That being said, at first glance the inclusion of the subpackage configs doesn't seem to override anything. I'd be interested to improve the cmake export config though.
Cheers, Nico [1] https://github.com/trilinos/trilinos/issues On Sun, Jul 23, 2017 at 1:36 PM Joachim Wuttke <j.wut...@fz-juelich.de> wrote: > Package: trilinos-dev > Version: 12.10.1-3 > > CMake's find_package takes an option COMPONENTS. > Usage with Trilinos seems to be documented nowhere, > but TrilinosConfig.cmake clearly is intended to > support e.g. > find_package(Trilinos REQUIRED COMPONENTS Epetra Belos Ifpack) > > However, at the bottom of TrilinosConfig.cmake there > is a long list that includes all Trilinos subproject > CMake files. This overwrites the component selection, > and makes it ineffective: the client application will > depend on _all_ of Trilinois, not just on the selected > components. > >
