StarMirror/sandboxed-api
1
0
Fork 0
mirror of https://github.com/google/sandboxed-api.git synced 2024-03-22 13:11:30 +08:00
Code Issues Projects Releases Wiki Activity
02d770adcc
sandboxed-api/contrib/c-blosc/CMakeLists.txt

83 lines
2.2 KiB
CMake
Raw Normal View History

Sandbox c-blosc
2022-01-31 18:02:14 +08:00
# Copyright 2022 Google LLC
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# https://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
CMake: Update policy settings to 3.26 This avoids a warning in newer CMake versions. For `CMP0083`, we still need to explicitly select `NEW` behavior. `check_pie_supported()` will error if it is unset even on later CMake versions. PiperOrigin-RevId: 531200735 Change-Id: Icb17a00cac087bd6888f8a9b9f8dd837358a6090
2023-05-11 22:50:03 +08:00
cmake_minimum_required(VERSION 3.13..3.26)
Sandbox c-blosc
2022-01-31 18:02:14 +08:00
project(sapi_blosc CXX)
cmake: Include `CTest` in all projects, honor `BUILD_TESTING` setting Including the `CTest` modules ensures that the `BUILD_TESTING` option is defined and automatically calls `enable_testing()` if needed. It does not change the default or introduce any dependencies on its own. This follows what Abseil already does in their top-level `CMakeLists.txt`. PiperOrigin-RevId: 443305646 Change-Id: If067c17470f497437c7748aab4aab5227c26e84f
2022-04-21 16:14:48 +08:00
include(CTest)
Add c-blosc and hunspell and their tests to CI - Minor reformatting in `CMakeLists.txt` - Update c-blosc to latest revision PiperOrigin-RevId: 454148849 Change-Id: I7a659c0786b1dc35d94059a518a0ec2859055432
2022-06-10 21:15:03 +08:00
include(GoogleTest)
Sandbox c-blosc
2022-01-31 18:02:14 +08:00
set(CMAKE_CXX_STANDARD 17)
set(CMAKE_CXX_STANDARD_REQUIRED True)
if(NOT TARGET sapi::sapi)
set(SAPI_ROOT "../.." CACHE PATH "Path to the Sandboxed API source tree")
Add c-blosc and hunspell and their tests to CI - Minor reformatting in `CMakeLists.txt` - Update c-blosc to latest revision PiperOrigin-RevId: 454148849 Change-Id: I7a659c0786b1dc35d94059a518a0ec2859055432
2022-06-10 21:15:03 +08:00
add_subdirectory("${SAPI_ROOT}"
"${CMAKE_BINARY_DIR}/sandboxed-api-build"
EXCLUDE_FROM_ALL)
Sandbox c-blosc
2022-01-31 18:02:14 +08:00
endif()
Add c-blosc and hunspell and their tests to CI - Minor reformatting in `CMakeLists.txt` - Update c-blosc to latest revision PiperOrigin-RevId: 454148849 Change-Id: I7a659c0786b1dc35d94059a518a0ec2859055432
2022-06-10 21:15:03 +08:00
FetchContent_Declare(libblosc
GIT_REPOSITORY https://github.com/Blosc/c-blosc.git
GIT_TAG ad6361f0151f830efb5ae113211c3559ab969886 # 2022-05-31
)
c-blosc: Enforce option to make symbols visible
2022-03-04 08:07:45 +08:00
set(HIDE_SYMBOLS OFF CACHE BOOL "" FORCE)
Introduce a transitional logging utility library Instead of calling `google::InitGoogleLogging()` directly, introduce an indirection via a new utility library. After this change, Sandboxed API should consistently use `sapi::InitLogging()` everywhere. For now, `sapi::InitLogging()` simply calls its glog equivalent. However, this enables us to migrate away from the gflags dependency and use Abseil flags. Once a follow-up change lands, `sapi::InitLogging()` will instead initialize the google logging library with flags defined from Aseil. Later still, once Abseil releases logging, we can then drop the glog dependency entirely. PiperOrigin-RevId: 445363592 Change-Id: Ia23a7dc88b8ffe65a422ea4d5233bba7bdd1303a
2022-04-29 17:13:32 +08:00
set(BUILD_BENCHMARKS OFF CACHE BOOL "" FORCE)
set(BUILD_FUZZERS OFF CACHE BOOL "" FORCE)
set(BUILD_TESTS OFF CACHE BOOL "" FORCE)
Sandbox c-blosc
2022-01-31 18:02:14 +08:00
FetchContent_MakeAvailable(libblosc)
Introduce a transitional logging utility library Instead of calling `google::InitGoogleLogging()` directly, introduce an indirection via a new utility library. After this change, Sandboxed API should consistently use `sapi::InitLogging()` everywhere. For now, `sapi::InitLogging()` simply calls its glog equivalent. However, this enables us to migrate away from the gflags dependency and use Abseil flags. Once a follow-up change lands, `sapi::InitLogging()` will instead initialize the google logging library with flags defined from Aseil. Later still, once Abseil releases logging, we can then drop the glog dependency entirely. PiperOrigin-RevId: 445363592 Change-Id: Ia23a7dc88b8ffe65a422ea4d5233bba7bdd1303a
2022-04-29 17:13:32 +08:00
add_sapi_library(sapi_blosc
FUNCTIONS blosc_init
blosc_destroy
Sandbox c-blosc
2022-01-31 18:02:14 +08:00
Introduce a transitional logging utility library Instead of calling `google::InitGoogleLogging()` directly, introduce an indirection via a new utility library. After this change, Sandboxed API should consistently use `sapi::InitLogging()` everywhere. For now, `sapi::InitLogging()` simply calls its glog equivalent. However, this enables us to migrate away from the gflags dependency and use Abseil flags. Once a follow-up change lands, `sapi::InitLogging()` will instead initialize the google logging library with flags defined from Aseil. Later still, once Abseil releases logging, we can then drop the glog dependency entirely. PiperOrigin-RevId: 445363592 Change-Id: Ia23a7dc88b8ffe65a422ea4d5233bba7bdd1303a
2022-04-29 17:13:32 +08:00
blosc_compress
blosc_decompress
Sandbox c-blosc
2022-01-31 18:02:14 +08:00
Introduce a transitional logging utility library Instead of calling `google::InitGoogleLogging()` directly, introduce an indirection via a new utility library. After this change, Sandboxed API should consistently use `sapi::InitLogging()` everywhere. For now, `sapi::InitLogging()` simply calls its glog equivalent. However, this enables us to migrate away from the gflags dependency and use Abseil flags. Once a follow-up change lands, `sapi::InitLogging()` will instead initialize the google logging library with flags defined from Aseil. Later still, once Abseil releases logging, we can then drop the glog dependency entirely. PiperOrigin-RevId: 445363592 Change-Id: Ia23a7dc88b8ffe65a422ea4d5233bba7bdd1303a
2022-04-29 17:13:32 +08:00
blosc_get_nthreads
blosc_set_nthreads
Sandbox c-blosc
2022-01-31 18:02:14 +08:00
Introduce a transitional logging utility library Instead of calling `google::InitGoogleLogging()` directly, introduce an indirection via a new utility library. After this change, Sandboxed API should consistently use `sapi::InitLogging()` everywhere. For now, `sapi::InitLogging()` simply calls its glog equivalent. However, this enables us to migrate away from the gflags dependency and use Abseil flags. Once a follow-up change lands, `sapi::InitLogging()` will instead initialize the google logging library with flags defined from Aseil. Later still, once Abseil releases logging, we can then drop the glog dependency entirely. PiperOrigin-RevId: 445363592 Change-Id: Ia23a7dc88b8ffe65a422ea4d5233bba7bdd1303a
2022-04-29 17:13:32 +08:00
blosc_get_compressor
blosc_set_compressor
Sandbox c-blosc
2022-01-31 18:02:14 +08:00
Introduce a transitional logging utility library Instead of calling `google::InitGoogleLogging()` directly, introduce an indirection via a new utility library. After this change, Sandboxed API should consistently use `sapi::InitLogging()` everywhere. For now, `sapi::InitLogging()` simply calls its glog equivalent. However, this enables us to migrate away from the gflags dependency and use Abseil flags. Once a follow-up change lands, `sapi::InitLogging()` will instead initialize the google logging library with flags defined from Aseil. Later still, once Abseil releases logging, we can then drop the glog dependency entirely. PiperOrigin-RevId: 445363592 Change-Id: Ia23a7dc88b8ffe65a422ea4d5233bba7bdd1303a
2022-04-29 17:13:32 +08:00
blosc_list_compressors
Sandbox c-blosc
2022-01-31 18:02:14 +08:00
Introduce a transitional logging utility library Instead of calling `google::InitGoogleLogging()` directly, introduce an indirection via a new utility library. After this change, Sandboxed API should consistently use `sapi::InitLogging()` everywhere. For now, `sapi::InitLogging()` simply calls its glog equivalent. However, this enables us to migrate away from the gflags dependency and use Abseil flags. Once a follow-up change lands, `sapi::InitLogging()` will instead initialize the google logging library with flags defined from Aseil. Later still, once Abseil releases logging, we can then drop the glog dependency entirely. PiperOrigin-RevId: 445363592 Change-Id: Ia23a7dc88b8ffe65a422ea4d5233bba7bdd1303a
2022-04-29 17:13:32 +08:00
blosc_get_version_string
Sandbox c-blosc
2022-01-31 18:02:14 +08:00
Introduce a transitional logging utility library Instead of calling `google::InitGoogleLogging()` directly, introduce an indirection via a new utility library. After this change, Sandboxed API should consistently use `sapi::InitLogging()` everywhere. For now, `sapi::InitLogging()` simply calls its glog equivalent. However, this enables us to migrate away from the gflags dependency and use Abseil flags. Once a follow-up change lands, `sapi::InitLogging()` will instead initialize the google logging library with flags defined from Aseil. Later still, once Abseil releases logging, we can then drop the glog dependency entirely. PiperOrigin-RevId: 445363592 Change-Id: Ia23a7dc88b8ffe65a422ea4d5233bba7bdd1303a
2022-04-29 17:13:32 +08:00
blosc_get_blocksize
blosc_set_blocksize
Sandbox c-blosc
2022-01-31 18:02:14 +08:00
Introduce a transitional logging utility library Instead of calling `google::InitGoogleLogging()` directly, introduce an indirection via a new utility library. After this change, Sandboxed API should consistently use `sapi::InitLogging()` everywhere. For now, `sapi::InitLogging()` simply calls its glog equivalent. However, this enables us to migrate away from the gflags dependency and use Abseil flags. Once a follow-up change lands, `sapi::InitLogging()` will instead initialize the google logging library with flags defined from Aseil. Later still, once Abseil releases logging, we can then drop the glog dependency entirely. PiperOrigin-RevId: 445363592 Change-Id: Ia23a7dc88b8ffe65a422ea4d5233bba7bdd1303a
2022-04-29 17:13:32 +08:00
blosc_set_splitmode
Sandbox c-blosc
2022-01-31 18:02:14 +08:00
Introduce a transitional logging utility library Instead of calling `google::InitGoogleLogging()` directly, introduce an indirection via a new utility library. After this change, Sandboxed API should consistently use `sapi::InitLogging()` everywhere. For now, `sapi::InitLogging()` simply calls its glog equivalent. However, this enables us to migrate away from the gflags dependency and use Abseil flags. Once a follow-up change lands, `sapi::InitLogging()` will instead initialize the google logging library with flags defined from Aseil. Later still, once Abseil releases logging, we can then drop the glog dependency entirely. PiperOrigin-RevId: 445363592 Change-Id: Ia23a7dc88b8ffe65a422ea4d5233bba7bdd1303a
2022-04-29 17:13:32 +08:00
blosc_cbuffer_sizes
blosc_cbuffer_validate
blosc_cbuffer_versions
INPUTS "${libblosc_SOURCE_DIR}/blosc/blosc.h"
Sandbox c-blosc
2022-01-31 18:02:14 +08:00
LIBRARY blosc_static
LIBRARY_NAME Cblosc
NAMESPACE ""
)
add_library(sapi_contrib::blosc ALIAS sapi_blosc)
target_include_directories(sapi_blosc INTERFACE
"${PROJECT_BINARY_DIR}"
)
cmake: Rename build options to follow Abseil naming `BUILD_TESTING` is a CMake provided option and we should use similar naming, just like how Abseil does it. - `SAPI_ENABLE_TESTS` -> `SAPI_BUILD_TESTING` - `SAPI_ENABLE_CONTRIB_TESTS` -> `SAPI_CONTRIB_BUILD_TESTING` - `SAPI_ENABLE_EXAMPLES` -> `SAPI_BUILD_EXAMPLES` Drive-by: - Fix option name in GitHub action PiperOrigin-RevId: 443305932 Change-Id: Ice2b42be1229a0f9ae7c2ceda9ce87187baf22c4
2022-04-21 16:17:08 +08:00
if (SAPI_BUILD_EXAMPLES)
Sandbox c-blosc
2022-01-31 18:02:14 +08:00
add_subdirectory(example)
endif()
cmake: Rename build options to follow Abseil naming `BUILD_TESTING` is a CMake provided option and we should use similar naming, just like how Abseil does it. - `SAPI_ENABLE_TESTS` -> `SAPI_BUILD_TESTING` - `SAPI_ENABLE_CONTRIB_TESTS` -> `SAPI_CONTRIB_BUILD_TESTING` - `SAPI_ENABLE_EXAMPLES` -> `SAPI_BUILD_EXAMPLES` Drive-by: - Fix option name in GitHub action PiperOrigin-RevId: 443305932 Change-Id: Ice2b42be1229a0f9ae7c2ceda9ce87187baf22c4
2022-04-21 16:17:08 +08:00
if (BUILD_TESTING AND SAPI_BUILD_TESTING)
Sandbox c-blosc
2022-01-31 18:02:14 +08:00
add_subdirectory(test)
endif()
Reference in New Issue Copy Permalink