2023-12-01 17:32:19 +00:00
|
|
|
# Copyright 2022 Google LLC. All rights reserved.
|
|
|
|
#
|
|
|
|
# Use of this source code is governed by a BSD-style
|
|
|
|
# license that can be found in the LICENSE file or at
|
|
|
|
# https://developers.google.com/open-source/licenses/bsd
|
|
|
|
|
|
|
|
# CMake build file to host CURL configuration.
|
|
|
|
|
|
|
|
# Don't build a shared libcurl.
|
|
|
|
set(BUILD_SHARED_LIBS OFF)
|
|
|
|
|
|
|
|
# Don't build with libdn, librtmp, libssh2, or zlib.
|
|
|
|
set(USE_LIBIDN2 OFF)
|
|
|
|
set(USE_LIBRTMP OFF)
|
|
|
|
set(CURL_USE_LIBSSH2 OFF)
|
|
|
|
set(CURL_ZLIB OFF CACHE STRING "Force curl not to search for system zlib")
|
feat: Portable, fully-static release executables on Linux (#1351)
This adds the option FULLY_STATIC to create fully-static executables.
To create portable, fully-static release executables on Linux, we need
to use musl instead of glibc. Static executables from glibc are not
portable.
The popular musl-gcc wrapper does not support C++, so instead we use a
full musl cross-compiler toolchain in the build workflow.
To build FULLY_STATIC, the user must point to the appropriate
cross-compiler, as we do in the workflow. On systems where musl is the
native libc (such as Alpine Linux), this is not necessary.
I have also read that musl's allocator is not very fast in
multi-threaded applications. So when FULLY_STATIC is enabled, we will
also enable mimalloc, a replacement allocator that is very fast.
I tested a very basic packaging command to compare speeds of dynamic
glibc, static musl, and static musl+mimalloc:
dynamic glibc:
runs: 2.527, 2.798, 2.703, 2.756, 2.959
avg = 2.749, std dev = 0.156s
static musl:
runs: 2.813, 2.920, 3.129, 3.003, 2.738
avg = 2.921s, std dev = 0.154s
static musl+mimalloc:
runs: 2.291, 2.034, 2.415, 2.303, 2.265
avg = 2.262s, std dev = 0.140s
The mimalloc build is 82% faster than musl default allocator, 77% faster
than glibc, and has more consistent runtime characteristics (lower
standard deviation).
2024-02-27 18:47:04 +00:00
|
|
|
set(BUILD_CURL_EXE OFF)
|
2023-12-01 17:32:19 +00:00
|
|
|
|
|
|
|
if(UNIX AND NOT APPLE)
|
|
|
|
# Use c-ares to fix static linking on Linux. Set USE_ARES directly, not the
|
|
|
|
# ENABLE_ARES option that triggers a search for c-ares on the system.
|
|
|
|
set(USE_ARES 1)
|
|
|
|
# This is necessary when we hack the c-ares search, because we break the
|
|
|
|
# export target. We didn't need it anyway.
|
|
|
|
set(CURL_ENABLE_EXPORT_TARGET OFF)
|
|
|
|
endif()
|
|
|
|
|
|
|
|
if(WIN32)
|
|
|
|
# Use native TLS on Windows. We could use mbedtls, but only if we also
|
|
|
|
# provide a path to CA certs.
|
|
|
|
set(CURL_USE_SCHANNEL ON)
|
|
|
|
else()
|
|
|
|
# Force libcurl to use our local mbedtls instead of searching for OpenSSL on
|
|
|
|
# the system.
|
|
|
|
set(CURL_USE_MBEDTLS ON)
|
|
|
|
set(MBEDTLS_INCLUDE_DIRS ../mbedtls/source/include)
|
|
|
|
set(MBEDTLS_LIBRARY mbedtls)
|
|
|
|
set(MBEDX509_LIBRARY mbedx509)
|
|
|
|
set(MBEDCRYPTO_LIBRARY mbedcrypto)
|
|
|
|
endif()
|
|
|
|
|
|
|
|
# With these set in scope of this folder, load the library's own CMakeLists.txt.
|
|
|
|
add_subdirectory(source)
|
|
|
|
|
|
|
|
# Our enabling of c-ares doesn't automatically set a dependency between libcurl
|
|
|
|
# and c-ares. Fix that now.
|
|
|
|
if(USE_ARES)
|
2024-10-24 20:53:39 +00:00
|
|
|
target_link_libraries(libcurl_static PUBLIC c-ares)
|
2023-12-01 17:32:19 +00:00
|
|
|
endif()
|