I'm glad you have it working now! Thanks for the update!
Satish
On Thu, 20 Feb 2025, Steven Dargaville wrote:
> My apologies, that does seem to have fixed the problem, the build rules in
> my tests were overriding the new variables.
>
> Thanks for your help in sorting that out!
> Steven
>
> On
My apologies, that does seem to have fixed the problem, the build rules in
my tests were overriding the new variables.
Thanks for your help in sorting that out!
Steven
On Thu, 20 Feb 2025 at 11:36, Steven Dargaville
wrote:
> Thanks for the reply! I've tried that and again it doesn't seem to wor
Thanks for the reply! I've tried that and again it doesn't seem to work for
the kokkos files. I went a bit overboard and set every variable I could
find but it doesn't seem to change the kokkos compilation, despite some of
those flags definitely being present in the kokkos compile targets.
CPPFLAG
Try setting CPPFLAGS, FPPFLAGS, CXXPPFLAGS [and not via PETSC_FC_INCLUDES].
I think kokkos compile targets [for *.kokkos.cxx sources] should pick up one
of them.
for ex:
>>>
CPPFLAGS = -Wall
FPPFLAGS = -Wall
CXXPPFLAGS = -Wall
include ${PETSC_DIR}/lib/petsc/conf/variables
include ${PETSC_DIR
Hi
I'm trying to build my application code (which includes C and Fortran
files) with a Makefile based off $PETSC_DIR/share/petsc/Makefile.basic.user
by using the variables and rules defined in
${PETSC_DIR}/lib/petsc/conf/variables. My application uses petsc as well as
another library, and hence I
