"Garth N. Wells" <[email protected]> writes: > We need this search for PETSc because we expose PETSc in the public > interface - users can call PETSc themselves. Most dependencies do not > appear in the public interface, in which case a user doesn't need to > to worry about them when building their own application.
Okay, fair enough. But presumably a user that does not intend to actually call PETSc directly wouldn't need to find_package(PETSc) in their own configure. Thanks for your help, Garth.
signature.asc
Description: PGP signature
