From 072540688a90017f57730dbabf4198cb7ea310f2 Mon Sep 17 00:00:00 2001 From: Sergey Sharybin Date: Mon, 27 Aug 2018 18:09:30 +0200 Subject: Build environment: Enable SSL for Python on Linux This involved getting SSL compiled from sources first, ensuring it is a static library placement independent code. Configuration is based on what Debian is using. CFlags required to have own configuration file, which i didn't find a better place that next to the corresponding CMake file. It is OpenSSL btw. It is set to Python via --with-openssl= configuration argument. This works fine in a clean chroot, but having libssl-dev installed might make Python to prefer system wide library, This was worked around by using libssl_pic.a name for the library and modifying setup.py. Would be cool to ensure system wide libraries are not a problem, but official release builder is safe against this, since it will catch possible non-static dependencies. There is also a new map file which shadows bunch of Python symbols. Without this Python's shared libraries might bring conflicting symbols to Blender namespace at runtime. Hopefully this doesn't break other platforms. --- build_files/build_environment/CMakeLists.txt | 4 ++++ 1 file changed, 4 insertions(+) (limited to 'build_files/build_environment/CMakeLists.txt') diff --git a/build_files/build_environment/CMakeLists.txt b/build_files/build_environment/CMakeLists.txt index 81810e3e457..a334adc34ff 100644 --- a/build_files/build_environment/CMakeLists.txt +++ b/build_files/build_environment/CMakeLists.txt @@ -137,4 +137,8 @@ if(NOT WIN32 OR ENABLE_MINGW64) endif() endif() +if(UNIX AND NOT APPLE) + include(cmake/ssl.cmake) +endif() + include(cmake/harvest.cmake) -- cgit v1.2.3