| 0b119762 | 08-Oct-2019 |
Satish Balay <balay@mcs.anl.gov> |
build: fix usage of preprocessor flags across languages - consistently set flags CPP_FLAGS, FPP_FLAGS, CXXPP_FLAGS, PCPP_FLAGS - add PPPFLAGS, PFLAGS to map user-make-flags CFLAGS/CXXFLAGS or CPPFL
build: fix usage of preprocessor flags across languages - consistently set flags CPP_FLAGS, FPP_FLAGS, CXXPP_FLAGS, PCPP_FLAGS - add PPPFLAGS, PFLAGS to map user-make-flags CFLAGS/CXXFLAGS or CPPFLAGS/CXXPPFLAGS correctly to the PCC compile targets - use PCPP_FLAGS with PCC targets and CXXPP_FLAGS with CXX targets
Notes - CFLAGS/CPPFLAGS [API] for makefile does not override the the same variables specified to configure. [CFLAGS/CPPFAGS to configure are saved in CC_FLAGS, CPP_FLAGS] - For some reason CPPFLAGS gets added to both CC_FLAGS [via self.setCompilers.getCompilerFlags()] and CPP_FLAGS. Its not clear if one can be remoted - We do not have a clean C compile target like we have for Cxx - due to --with-clanguage [hence PCC etc intertwined with PETSC_COMPILE..]
show more ...
|