aboutsummaryrefslogtreecommitdiff
path: root/src
diff options
context:
space:
mode:
authorEven Rouault <even.rouault@spatialys.com>2018-11-28 15:47:03 +0100
committerEven Rouault <even.rouault@spatialys.com>2018-11-29 00:39:01 +0100
commit492763fec2bb4fa9c0c52b906feda0a2a96d866c (patch)
tree60e3e7dfd4547a3b814ed8c69bfb14e1e8b9a644 /src
parent47cada7c3a0d55bcc071f124e3bc0ea403cfff64 (diff)
downloadPROJ-492763fec2bb4fa9c0c52b906feda0a2a96d866c.tar.gz
PROJ-492763fec2bb4fa9c0c52b906feda0a2a96d866c.zip
Build: change back link-time-optimization default to off
I've found that if building PROJ with lto, but GDAL without lto, exceptions thrown in PROJ are not properly captured by try {} blocks in PROJ C API, and unexpectedly go back up to GDAL. Might be a defect of the particular compiler I use (gcc 5.4 Ubuntu 16.04)
Diffstat (limited to 'src')
-rw-r--r--src/lib_proj.cmake2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/lib_proj.cmake b/src/lib_proj.cmake
index 6fe84944..bb45db44 100644
--- a/src/lib_proj.cmake
+++ b/src/lib_proj.cmake
@@ -32,7 +32,7 @@ elseif(USE_THREAD AND NOT Threads_FOUND)
message(FATAL_ERROR "No thread library found and thread/mutex support is required by USE_THREAD option")
endif()
-option(ENABLE_LTO "Build library with LTO optimization (if available)." ON)
+option(ENABLE_LTO "Build library with LTO optimization (if available)." OFF)
if(ENABLE_LTO)
if("${CMAKE_C_COMPILER_ID}" MATCHES "Clang")
include (CheckCXXSourceCompiles)