| Age | Commit message (Collapse) | Author |
|---|
|
https://github.com/OSGeo/PROJ/pull/1839#pullrequestreview-345535380
|
|
|
|
|
|
|
|
|
|
PROJ_NETWORK_ENDPOINT or proj_context_set_url_endpoint()
|
|
|
|
|
|
Remove (most) needs to fiddle with CMAKE_C_FLAGS / CMAKE_CXX_FLAGS
|
|
HAVE_STRERROR is defined in proj_config.h.
|
|
|
|
GTest provides a configuration file, so we can disable the module
mode. If the GTest package cannot be found, this shall be reported
right here. (Note that while we specify a version, we do not require
an EXACT match.)
|
|
GTest::gtest is the imported target supplied by find_package(GTest).
For the internal build of GTest, this target is created as an alias
for now: find_package cannot be used because the interal build does
not get installed, and so a package config file is not available.
|
|
PROJ requires CMake >= 3.5.
|
|
This fixes issues with MinGW when threads are used.
|
|
|
|
proj_context_set_search_paths() (refs #1150)
|
|
With this commit we make sure that proj_angular_input() and
proj_angular_output return the correct result for any given pipeline.
|
|
|
|
|
|
This work mostly consists of:
- a C++ implementation of the ISO-19111:2018 / OGC Topic 2
"Referencing by coordinates" classes to represent Datums,
Coordinate systems, CRSs (Coordinate Reference Systems) and
Coordinate Operations.
- methods to convert between this C++ modeling and WKT1, WKT2
and PROJ string representations of those objects
- management and query of a SQLite3 database of CRS and Coordinate Operation definition
- a C API binding part of those capabilities
This is all-in-one squashed commit of the work of
https://github.com/OSGeo/proj.4/pull/1040
|
|
|
|
Nigrated from:
schwehr/gdal-autotest2:cpp/third_party/proj/pj_phi2_test.cc@master
License intentionally changed from Apache 2 to match PROJ.
|
|
For CMake builds, latest googletest 1.8.0 is downloaded.
Following officially recommended integration for CMake-enabled projects
https://github.com/google/googletest/blob/master/googletest/README.md
"Use CMake to download GoogleTest as part of the build's configure step.
This is just a little more complex, but doesn't have the limitations
of the other methods."
Since, our copy of test/googletest
- is a very minimalist copy of googletest
- does not include any official CMake scripts
- would require copying parts of googletest CMakeLists.txt, compilater/linker flags (e.g. -lpthreads)
for reliable multi-platform builds, it is reasoanable to rely on download
All pros and cons advantages are discussed in teh README.md linked above.
Closes #1033
|
|
builds only (CMake integration to be done)
|
|
|
|
|
