Thanks Jed.
I currently fix this problem defining the PETSc path as the
environment variable. I will try to use find_pacakge later.
Hom
On Mon, Mar 27, 2017 at 11:02 PM, Jed Brown wrote:
> Hom Nath Gharti writes:
>
>> Thanks, Jed! I will try. I see that
Hom Nath Gharti writes:
> Thanks, Jed! I will try. I see that FindPETSc.cmake has following lines:
>
> set(PETSC_VALID_COMPONENTS
> C
> CXX)
>
> Should we add FC or similar?
You could, but then you'd have to also add test code for that language
binding. (All this does is a
Thanks, Jed! I will try. I see that FindPETSc.cmake has following lines:
set(PETSC_VALID_COMPONENTS
C
CXX)
Should we add FC or similar?
Thanks,
Hom
On Wed, Mar 22, 2017 at 9:09 PM, Jed Brown wrote:
> Hom Nath Gharti writes:
>
>> Dear all,
>>
>> Does
Hom Nath Gharti writes:
> Dear all,
>
> Does FindPETSc.cmake (https://github.com/jedbrown/cmake-modules) work
> with Fortran as well?
It should, but you need to be sure to use a compatible Fortran compiler.
signature.asc
Description: PGP signature
Dear all,
Does FindPETSc.cmake (https://github.com/jedbrown/cmake-modules) work
with Fortran as well?
Thanks,
Hom