On 09/05/2013 06:21 PM, Jed Brown wrote:
>>  #
>> -#  Usage:
>> -#  find_package(PETSc COMPONENTS CXX)  - required if build --with-clanguage=C++ --with-c-support=0
>> -#  find_package(PETSc COMPONENTS C)    - standard behavior of checking build using a C compiler
>> -#  find_package(PETSc)                 - same as above
>> +# MPIFC_SHOW, MPICXX_SHOW,MPICC_SHOW, PCC,  CC_FLAGS, PCC_FLAGS, FC_FLAGS, CPP_FLAGS
>> +# METIS_INCLUDE, BLASLAPACK_INCLUDE, PARMETIS_INCLUDE, MUMPS_INCLUDE
>> +# MPI_LIB, MUMPS_LIB,  METIS_LIB, PARMETIS_LIB, BLASLAPACK_LIB, SCALAPACK_LIB 
> 
> Why do you need these variables?  (It's not wrong, but we hope that these configuration variables are not needed by a caller. Whether an external package is available -- from petscconf.h -- sounds more useful to me.)

I have made an install script for the BDDCML library due to Jakub Sistek
and I needed also lib and include dirs to configure BDDCML through
make.inc and compile. Would it be better to accept a variable with list
of make variables to export?


> 
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/jedbrown/cmake-modules/pull/3/files#r6186141
> 

-- 
------------------------
Mgr. Jan Brezina, Ph. D.
Technical University in Liberec, New technologies institute
http://www.nti.tul.cz/cz/WikiUser:Jan.Brezina