libproj: fix `STRICT` conflict for MinGW as well

Using upstream's fix.

added area:build area:third-party labels

requested review from @mwestphal

Warnings:

• please consider adding a changelog entry in a file ending with .md in Documentation/release/dev.

The warnings do not need to be fixed, but it is recommended to do so.

should that be _MSC_VER ?

That's exactly what didn't work before for MinGW. Upstream used this solution and it seems more useful (in that "we don't care where STRICT comes from, it just can't be active if util.hpp is included").

ok, the ifdef seems unseless to me then, #undef STRICT by itself should work as well. In any case, that upstream code.

for reference: https://stackoverflow.com/questions/9090536/when-do-we-need-ifdef-before-undef

Take it up with upstream; I'd rather use their patch than diverge.

sure.

+2

resolved all threads

Do: merge

mentioned in commit 576c39dc

merged

mentioned in commit spiros.tsalikis/paraview@1de33340

mentioned in commit spiros.tsalikis/paraview@8e43db21

mentioned in commit spiros.tsalikis/paraview@32792465

mentioned in commit spiros.tsalikis/paraview@a82dce59

mentioned in commit spiros.tsalikis/paraview@750e7028

mentioned in commit christos.tsolakis/async-paraview@be68cf54

mentioned in commit christos.tsolakis/async-paraview@bafb8b2f