On 7/1/24 5:23 PM, Stefano Zampini wrote:
This is unfortunate. I assume that patching the buildsystem or some other trickery will be necessary if what you're saying is true.I admit it is not so standard, but Satish always opposed this.No need to hack the buildsystem, just use COPTFLAGS, CXXOPTFLAGS and FOPTFLAGS
I will try using *OPTFLAGS, thanks!
I don't think you should use Makefile.user. That is there as a sort of template/placeholder. The extra variables are not included in a standard usage of pkgconfig, so I don't think this issue is "severe"
This is not a choice I get to make. The users of my package may choose to use PETSc however they want. And /usr/share/petsc/Makefile.user or /usr/share/petsc/CMakeLists.txt are officially supported ways of using PETSc, so deciding to ignore these use cases and leaving junk flags in /usr/lib/pkgconfig/petsc.pc is not tolerable for me.
OpenPGP_0x1A14CB3464CBE5BF.asc
Description: OpenPGP public key
OpenPGP_signature.asc
Description: OpenPGP digital signature
