Even Rouault

> Has this been tested locally? TBH no > (I don't expect it in CI) AFAICS we have postinstall checks in test/postinstall/c_app/CMakeLists.txt that do "find_package(${USE_PROJ_NAME} REQUIRED CONFIG)". But maybe https://github.com/curl/curl/blob/8dcbb0f19176da937ddb3c85509b8c84086348f1/lib/CMakeLists.txt#L98...

Proposed upstream change for curl: https://github.com/curl/curl/pull/9125

@dg0yt I've tested a cmake build (shared) of curl master (so that has the PUBLIC import of its dependencies), build PROJ master (shared) against it and run test/postinstall/test_cmake.sh on the...

> So I assumed it is all resolved. could we also remove find_dependency(CURL) for static builds?

I'm quite confused by the topic. I actually figured out that if PROJ is finding CURL through CMake config files, then the build doesn't work properly as CURL_INCLUDE_DIRS and CURL_LIBRARIES...

> You mean `find_package(CURL CONFIG)`? With cmake 3.21.3 or 3.23.0rc1, I don't have to explicitly specify CONFIG and it picks up the CMake config: 'Found CURL: /home/even/install-curl-cmake/lib/cmake/CURL/CURLConfig.cmake (found version "7.85.0-DEV")'

> i.e. `CURL_INCLUDE_DIRS` and `CURL_LIBRARIES` are still valid result variables for this scenario. well, not for me.... They are not defined. Adding traces to CMake provided FindCURL.cmake, I see I...

Those WKT strings aren't compliant with the http://portal.opengeospatial.org/files/?artifact_id=999 spec (nor any other WKT spec I'm aware of) - The first string has the following structure `COMPD_CS["bla", PROJCS[...] ], VERT_CS[...] ]`....

CC @hobu who has likely seen his share of crazy LAS WKT...

OGRSpatialReference::importFromWkt() leverages proj_create_from_wkt() which has options to get warnings and errors.