Morph MORPH
SIGN IN SIGN UP
apache / arrow UNCLAIMED

Apache Arrow is the universal columnar format and multi-language toolbox for fast data interchange and in-memory analytics

0 0 1 C++
Normal View History Raw
ARROW-14714: [C++][Doc] Rework CMake presets and add documentation Try to define CMake presets that correspond to common use cases. Switch to version 3 of the format so that `binaryDir` isn't mandatory anymore. Also add display names so that the command line can be more informative. Document the use of CMake presets. Summary of available presets: ``` $ cmake --list-presets Available configure presets: "ninja-debug-minimal" - Debug build without anything enabled "ninja-debug-basic" - Debug build with tests and reduced dependencies "ninja-debug" - Debug build with tests and more optional components "ninja-debug-cuda" - Debug build with tests and CUDA integration "ninja-debug-filesystems" - Debug build with tests and filesystems "ninja-debug-flight" - Debug build with tests and Flight "ninja-debug-gandiva" - Debug build with tests and Gandiva "ninja-debug-python" - Debug build with tests and Python support "ninja-debug-maximal" - Debug build with everything enabled (except benchmarks and CUDA) "ninja-release-minimal" - Release build without anything enabled "ninja-release-basic" - Release build with reduced dependencies "ninja-release" - Release build with more optional components "ninja-release-cuda" - Release build with CUDA integration "ninja-release-flight" - Release build with Flight "ninja-release-gandiva" - Release build with Gandiva "ninja-release-python" - Release build with Python support "ninja-release-maximal" - Release build with everything enabled (except benchmarks and CUDA) "ninja-benchmarks-basic" - Benchmarking build with reduced dependencies "ninja-benchmarks" - Benchmarking build with more optional components ``` Closes #11778 from pitrou/ARROW-14714-cmake-presets Authored-by: Antoine Pitrou <antoine@python.org> Signed-off-by: Krisztián Szűcs <szucs.krisztian@gmail.com>
2021-12-01 20:33:23 +01:00
{
"version": 3,
"cmakeMinimumRequired": {
"major": 3,
"minor": 21,
"patch": 0
},
"configurePresets": [
{
"name": "base",
"hidden": true,
"generator": "Ninja",
"cacheVariables": {
GH-36124: [C++] Export compile_commands.json by default (#37426) `CMakePresets.json` does not export `compile_commands.json` by default, which is used by all clang tooling. Adding it as a default ensures that new developers (or any others who forget to specifically specify the option) will still be able to use their language servers without regenerating the cmake build dir. The relevant option is `"CMAKE_EXPORT_COMPILE_COMMANDS": "ON"`, and causes generation of a ~1MB file at build time. * Closes: #36124 Authored-by: Benjamin Kietzman <bengilgit@gmail.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2023-08-28 19:44:25 -04:00
"ARROW_BUILD_STATIC": "OFF",
"CMAKE_EXPORT_COMPILE_COMMANDS": "ON"
ARROW-14714: [C++][Doc] Rework CMake presets and add documentation Try to define CMake presets that correspond to common use cases. Switch to version 3 of the format so that `binaryDir` isn't mandatory anymore. Also add display names so that the command line can be more informative. Document the use of CMake presets. Summary of available presets: ``` $ cmake --list-presets Available configure presets: "ninja-debug-minimal" - Debug build without anything enabled "ninja-debug-basic" - Debug build with tests and reduced dependencies "ninja-debug" - Debug build with tests and more optional components "ninja-debug-cuda" - Debug build with tests and CUDA integration "ninja-debug-filesystems" - Debug build with tests and filesystems "ninja-debug-flight" - Debug build with tests and Flight "ninja-debug-gandiva" - Debug build with tests and Gandiva "ninja-debug-python" - Debug build with tests and Python support "ninja-debug-maximal" - Debug build with everything enabled (except benchmarks and CUDA) "ninja-release-minimal" - Release build without anything enabled "ninja-release-basic" - Release build with reduced dependencies "ninja-release" - Release build with more optional components "ninja-release-cuda" - Release build with CUDA integration "ninja-release-flight" - Release build with Flight "ninja-release-gandiva" - Release build with Gandiva "ninja-release-python" - Release build with Python support "ninja-release-maximal" - Release build with everything enabled (except benchmarks and CUDA) "ninja-benchmarks-basic" - Benchmarking build with reduced dependencies "ninja-benchmarks" - Benchmarking build with more optional components ``` Closes #11778 from pitrou/ARROW-14714-cmake-presets Authored-by: Antoine Pitrou <antoine@python.org> Signed-off-by: Krisztián Szűcs <szucs.krisztian@gmail.com>
2021-12-01 20:33:23 +01:00
}
},
{
"name": "base-debug",
"inherits": "base",
"hidden": true,
"cacheVariables": {
"ARROW_BUILD_INTEGRATION": "ON",
"ARROW_BUILD_TESTS": "ON",
"ARROW_EXTRA_ERROR_CONTEXT": "ON",
"CMAKE_BUILD_TYPE": "Debug"
}
},
{
"name": "base-release",
"inherits": "base",
"hidden": true,
"cacheVariables": {
"CMAKE_BUILD_TYPE": "Release"
}
},
{
"name": "base-benchmarks",
"inherits": "base",
"hidden": true,
"cacheVariables": {
"ARROW_BUILD_BENCHMARKS": "ON",
"ARROW_BUILD_BENCHMARKS_REFERENCE": "ON",
ARROW-14479: [C++] Hash Join Microbenchmarks Added microbenchmarks for Hash Join (using OpenMP for parallelism for now). Also added a python script that analyzes the benchmark file and makes a lot of pretty graphs! Closes #11876 from save-buffer/sasha_benchmark Authored-by: Sasha Krassovsky <krassovskysasha@gmail.com> Signed-off-by: Weston Pace <weston.pace@gmail.com>
2022-01-12 16:35:33 -10:00
"ARROW_BUILD_DETAILED_BENCHMARKS": "OFF",
ARROW-14714: [C++][Doc] Rework CMake presets and add documentation Try to define CMake presets that correspond to common use cases. Switch to version 3 of the format so that `binaryDir` isn't mandatory anymore. Also add display names so that the command line can be more informative. Document the use of CMake presets. Summary of available presets: ``` $ cmake --list-presets Available configure presets: "ninja-debug-minimal" - Debug build without anything enabled "ninja-debug-basic" - Debug build with tests and reduced dependencies "ninja-debug" - Debug build with tests and more optional components "ninja-debug-cuda" - Debug build with tests and CUDA integration "ninja-debug-filesystems" - Debug build with tests and filesystems "ninja-debug-flight" - Debug build with tests and Flight "ninja-debug-gandiva" - Debug build with tests and Gandiva "ninja-debug-python" - Debug build with tests and Python support "ninja-debug-maximal" - Debug build with everything enabled (except benchmarks and CUDA) "ninja-release-minimal" - Release build without anything enabled "ninja-release-basic" - Release build with reduced dependencies "ninja-release" - Release build with more optional components "ninja-release-cuda" - Release build with CUDA integration "ninja-release-flight" - Release build with Flight "ninja-release-gandiva" - Release build with Gandiva "ninja-release-python" - Release build with Python support "ninja-release-maximal" - Release build with everything enabled (except benchmarks and CUDA) "ninja-benchmarks-basic" - Benchmarking build with reduced dependencies "ninja-benchmarks" - Benchmarking build with more optional components ``` Closes #11778 from pitrou/ARROW-14714-cmake-presets Authored-by: Antoine Pitrou <antoine@python.org> Signed-off-by: Krisztián Szűcs <szucs.krisztian@gmail.com>
2021-12-01 20:33:23 +01:00
"CMAKE_BUILD_TYPE": "RelWithDebInfo"
}
},
{
"name": "features-minimal",
"hidden": true,
"cacheVariables": {
GH-44976: [C++] Enable mimalloc by default, disable jemalloc by default and more (#44951) ### What changes are included in this PR? 1) Disable jemalloc by default 2) Enable mimalloc by default 3) Some files in `arrow/compute` are only required when ARROW_COMPUTE is enabled, so we needn't compile them by default ### Are these changes tested? Yes, by existing CI tests. ### Are there any user-facing changes? Yes, but nothing compatibility-breaking. * GitHub Issue: #44976 Authored-by: Antoine Pitrou <pitrou@free.fr> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2024-12-10 02:39:22 +01:00
"ARROW_MIMALLOC": "OFF",
ARROW-14714: [C++][Doc] Rework CMake presets and add documentation Try to define CMake presets that correspond to common use cases. Switch to version 3 of the format so that `binaryDir` isn't mandatory anymore. Also add display names so that the command line can be more informative. Document the use of CMake presets. Summary of available presets: ``` $ cmake --list-presets Available configure presets: "ninja-debug-minimal" - Debug build without anything enabled "ninja-debug-basic" - Debug build with tests and reduced dependencies "ninja-debug" - Debug build with tests and more optional components "ninja-debug-cuda" - Debug build with tests and CUDA integration "ninja-debug-filesystems" - Debug build with tests and filesystems "ninja-debug-flight" - Debug build with tests and Flight "ninja-debug-gandiva" - Debug build with tests and Gandiva "ninja-debug-python" - Debug build with tests and Python support "ninja-debug-maximal" - Debug build with everything enabled (except benchmarks and CUDA) "ninja-release-minimal" - Release build without anything enabled "ninja-release-basic" - Release build with reduced dependencies "ninja-release" - Release build with more optional components "ninja-release-cuda" - Release build with CUDA integration "ninja-release-flight" - Release build with Flight "ninja-release-gandiva" - Release build with Gandiva "ninja-release-python" - Release build with Python support "ninja-release-maximal" - Release build with everything enabled (except benchmarks and CUDA) "ninja-benchmarks-basic" - Benchmarking build with reduced dependencies "ninja-benchmarks" - Benchmarking build with more optional components ``` Closes #11778 from pitrou/ARROW-14714-cmake-presets Authored-by: Antoine Pitrou <antoine@python.org> Signed-off-by: Krisztián Szűcs <szucs.krisztian@gmail.com>
2021-12-01 20:33:23 +01:00
"ARROW_WITH_RE2": "OFF",
"ARROW_WITH_UTF8PROC": "OFF"
}
},
{
"name": "features-basic",
GH-45209: [C++][CMake] Fix the issue that allocator not disabled for sanitizer cmake presets (#45210) ### Rationale for this change I gave the reason in #45209 ### What changes are included in this PR? Adjust the inheritance list order and make a lot of simplification/regrouping/reordering for existing presets the way I see fit. Also introduce a soft rule to order inheritance list: `sanitizer` comes before `features` comes before `base`. Though we can't really mandate such a rule (thus it's "soft") or make it clear in comments (our current cmake dosn't support comment in json), we hope people will notice this pattern and follow it when editing this file. ### Are these changes tested? Manually tested. ### Are there any user-facing changes? None. * GitHub Issue: #45209 Lead-authored-by: Rossi Sun <zanmato1984@gmail.com> Co-authored-by: Sutou Kouhei <kou@cozmixng.org> Signed-off-by: Rossi Sun <zanmato1984@gmail.com>
2025-01-10 23:14:20 +08:00
"inherits": [
"features-minimal"
],
ARROW-14714: [C++][Doc] Rework CMake presets and add documentation Try to define CMake presets that correspond to common use cases. Switch to version 3 of the format so that `binaryDir` isn't mandatory anymore. Also add display names so that the command line can be more informative. Document the use of CMake presets. Summary of available presets: ``` $ cmake --list-presets Available configure presets: "ninja-debug-minimal" - Debug build without anything enabled "ninja-debug-basic" - Debug build with tests and reduced dependencies "ninja-debug" - Debug build with tests and more optional components "ninja-debug-cuda" - Debug build with tests and CUDA integration "ninja-debug-filesystems" - Debug build with tests and filesystems "ninja-debug-flight" - Debug build with tests and Flight "ninja-debug-gandiva" - Debug build with tests and Gandiva "ninja-debug-python" - Debug build with tests and Python support "ninja-debug-maximal" - Debug build with everything enabled (except benchmarks and CUDA) "ninja-release-minimal" - Release build without anything enabled "ninja-release-basic" - Release build with reduced dependencies "ninja-release" - Release build with more optional components "ninja-release-cuda" - Release build with CUDA integration "ninja-release-flight" - Release build with Flight "ninja-release-gandiva" - Release build with Gandiva "ninja-release-python" - Release build with Python support "ninja-release-maximal" - Release build with everything enabled (except benchmarks and CUDA) "ninja-benchmarks-basic" - Benchmarking build with reduced dependencies "ninja-benchmarks" - Benchmarking build with more optional components ``` Closes #11778 from pitrou/ARROW-14714-cmake-presets Authored-by: Antoine Pitrou <antoine@python.org> Signed-off-by: Krisztián Szűcs <szucs.krisztian@gmail.com>
2021-12-01 20:33:23 +01:00
"hidden": true,
"cacheVariables": {
"ARROW_COMPUTE": "ON",
"ARROW_CSV": "ON",
"ARROW_DATASET": "ON",
"ARROW_FILESYSTEM": "ON",
GH-44976: [C++] Enable mimalloc by default, disable jemalloc by default and more (#44951) ### What changes are included in this PR? 1) Disable jemalloc by default 2) Enable mimalloc by default 3) Some files in `arrow/compute` are only required when ARROW_COMPUTE is enabled, so we needn't compile them by default ### Are these changes tested? Yes, by existing CI tests. ### Are there any user-facing changes? Yes, but nothing compatibility-breaking. * GitHub Issue: #44976 Authored-by: Antoine Pitrou <pitrou@free.fr> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2024-12-10 02:39:22 +01:00
"ARROW_JSON": "ON",
"ARROW_MIMALLOC": "ON"
ARROW-14714: [C++][Doc] Rework CMake presets and add documentation Try to define CMake presets that correspond to common use cases. Switch to version 3 of the format so that `binaryDir` isn't mandatory anymore. Also add display names so that the command line can be more informative. Document the use of CMake presets. Summary of available presets: ``` $ cmake --list-presets Available configure presets: "ninja-debug-minimal" - Debug build without anything enabled "ninja-debug-basic" - Debug build with tests and reduced dependencies "ninja-debug" - Debug build with tests and more optional components "ninja-debug-cuda" - Debug build with tests and CUDA integration "ninja-debug-filesystems" - Debug build with tests and filesystems "ninja-debug-flight" - Debug build with tests and Flight "ninja-debug-gandiva" - Debug build with tests and Gandiva "ninja-debug-python" - Debug build with tests and Python support "ninja-debug-maximal" - Debug build with everything enabled (except benchmarks and CUDA) "ninja-release-minimal" - Release build without anything enabled "ninja-release-basic" - Release build with reduced dependencies "ninja-release" - Release build with more optional components "ninja-release-cuda" - Release build with CUDA integration "ninja-release-flight" - Release build with Flight "ninja-release-gandiva" - Release build with Gandiva "ninja-release-python" - Release build with Python support "ninja-release-maximal" - Release build with everything enabled (except benchmarks and CUDA) "ninja-benchmarks-basic" - Benchmarking build with reduced dependencies "ninja-benchmarks" - Benchmarking build with more optional components ``` Closes #11778 from pitrou/ARROW-14714-cmake-presets Authored-by: Antoine Pitrou <antoine@python.org> Signed-off-by: Krisztián Szűcs <szucs.krisztian@gmail.com>
2021-12-01 20:33:23 +01:00
}
},
{
"name": "features-main",
"inherits": "features-basic",
"hidden": true,
"cacheVariables": {
ARROW-16158: [C++][R] Rename ARROW_ENGINE to ARROW_SUBSTRAIT At the moment there is not enough non-Substrait functionality to justify a dedicated engine module. In the future there likely will be and so I have some of the general structure around in the C++ (e.g. `ARROW_ENGINE_EXPORT`) but removed any external facing references. Closes #12915 from westonpace/feature/ARROW-16158--rename-engine-to-substrait Lead-authored-by: Weston Pace <weston.pace@gmail.com> Co-authored-by: Neal Richardson <neal.p.richardson@gmail.com> Signed-off-by: Krisztián Szűcs <szucs.krisztian@gmail.com>
2022-04-24 18:15:41 +02:00
"ARROW_SUBSTRAIT": "ON",
GH-15280: [C++][Python][GLib] add libarrow_acero containing everything previously in compute/exec (#34711) ### Rationale for this change See the linked issue ### What changes are included in this PR? C++: * remove all compute/exec/* from libarrow * rename compute/exec -> acero and make libarrow_acero * add new ARROW_ACERO option, required if ARROW_DATASET is on * libarrow_dataset now depends on libarrow_acero c_glib: add the new libarrow_acero dependency - we disallow building glib without it python: added PYARROW_BUILD_ACERO, set to on if DATASETS are built ### Are these changes tested? All the standard tests do work properly. I manually compiled C++ with: * no ARROW_ACERO * ARROW_ACERO and no ARROW_DATASET * ARROW_ACERO and ARROW_DATASET and no ARROW_SUBSTRAIT I manually compiled python without ACERO & DATASET and with ACERO and without DATASET ### Are there any user-facing changes? If users include compute/exec files directly then they'll have to update their code. * Closes: #15280 Lead-authored-by: Davide Pasetto <dpasetto69@gmail.com> Co-authored-by: Li Jin <ice.xelloss@gmail.com> Co-authored-by: Weston Pace <weston.pace@gmail.com> Signed-off-by: Li Jin <ice.xelloss@gmail.com>
2023-04-01 06:47:16 -04:00
"ARROW_ACERO": "ON",
ARROW-14714: [C++][Doc] Rework CMake presets and add documentation Try to define CMake presets that correspond to common use cases. Switch to version 3 of the format so that `binaryDir` isn't mandatory anymore. Also add display names so that the command line can be more informative. Document the use of CMake presets. Summary of available presets: ``` $ cmake --list-presets Available configure presets: "ninja-debug-minimal" - Debug build without anything enabled "ninja-debug-basic" - Debug build with tests and reduced dependencies "ninja-debug" - Debug build with tests and more optional components "ninja-debug-cuda" - Debug build with tests and CUDA integration "ninja-debug-filesystems" - Debug build with tests and filesystems "ninja-debug-flight" - Debug build with tests and Flight "ninja-debug-gandiva" - Debug build with tests and Gandiva "ninja-debug-python" - Debug build with tests and Python support "ninja-debug-maximal" - Debug build with everything enabled (except benchmarks and CUDA) "ninja-release-minimal" - Release build without anything enabled "ninja-release-basic" - Release build with reduced dependencies "ninja-release" - Release build with more optional components "ninja-release-cuda" - Release build with CUDA integration "ninja-release-flight" - Release build with Flight "ninja-release-gandiva" - Release build with Gandiva "ninja-release-python" - Release build with Python support "ninja-release-maximal" - Release build with everything enabled (except benchmarks and CUDA) "ninja-benchmarks-basic" - Benchmarking build with reduced dependencies "ninja-benchmarks" - Benchmarking build with more optional components ``` Closes #11778 from pitrou/ARROW-14714-cmake-presets Authored-by: Antoine Pitrou <antoine@python.org> Signed-off-by: Krisztián Szűcs <szucs.krisztian@gmail.com>
2021-12-01 20:33:23 +01:00
"ARROW_PARQUET": "ON",
"ARROW_WITH_BROTLI": "ON",
"ARROW_WITH_BZ2": "ON",
"ARROW_WITH_LZ4": "ON",
"ARROW_WITH_RE2": "ON",
"ARROW_WITH_SNAPPY": "ON",
"ARROW_WITH_UTF8PROC": "ON",
"ARROW_WITH_ZLIB": "ON",
"ARROW_WITH_ZSTD": "ON"
}
},
{
"name": "features-cuda",
"inherits": "features-basic",
"hidden": true,
"cacheVariables": {
"ARROW_CUDA": "ON"
}
},
{
"name": "features-filesystems",
"inherits": "features-basic",
"hidden": true,
"cacheVariables": {
GH-35903: [C++] Skeleton for Azure Blob Storage filesystem implementation (#35701) ### What changes are included in this PR? This PR splits out the overall skeleton of #12914 in order to make merging of the overall Azure Filesystem easier to do. ### Are these changes tested? Yes. ### Are there any user-facing changes? Yes. * Closes: #35903 Authored-by: Srinivas Lade <srinulade1@gmail.com> Signed-off-by: Antoine Pitrou <antoine@python.org>
2023-07-12 12:53:59 -04:00
"ARROW_AZURE": "ON",
ARROW-14714: [C++][Doc] Rework CMake presets and add documentation Try to define CMake presets that correspond to common use cases. Switch to version 3 of the format so that `binaryDir` isn't mandatory anymore. Also add display names so that the command line can be more informative. Document the use of CMake presets. Summary of available presets: ``` $ cmake --list-presets Available configure presets: "ninja-debug-minimal" - Debug build without anything enabled "ninja-debug-basic" - Debug build with tests and reduced dependencies "ninja-debug" - Debug build with tests and more optional components "ninja-debug-cuda" - Debug build with tests and CUDA integration "ninja-debug-filesystems" - Debug build with tests and filesystems "ninja-debug-flight" - Debug build with tests and Flight "ninja-debug-gandiva" - Debug build with tests and Gandiva "ninja-debug-python" - Debug build with tests and Python support "ninja-debug-maximal" - Debug build with everything enabled (except benchmarks and CUDA) "ninja-release-minimal" - Release build without anything enabled "ninja-release-basic" - Release build with reduced dependencies "ninja-release" - Release build with more optional components "ninja-release-cuda" - Release build with CUDA integration "ninja-release-flight" - Release build with Flight "ninja-release-gandiva" - Release build with Gandiva "ninja-release-python" - Release build with Python support "ninja-release-maximal" - Release build with everything enabled (except benchmarks and CUDA) "ninja-benchmarks-basic" - Benchmarking build with reduced dependencies "ninja-benchmarks" - Benchmarking build with more optional components ``` Closes #11778 from pitrou/ARROW-14714-cmake-presets Authored-by: Antoine Pitrou <antoine@python.org> Signed-off-by: Krisztián Szűcs <szucs.krisztian@gmail.com>
2021-12-01 20:33:23 +01:00
"ARROW_GCS": "ON",
"ARROW_HDFS": "ON",
"ARROW_S3": "ON"
}
},
{
"name": "features-flight",
"inherits": "features-basic",
"hidden": true,
"cacheVariables": {
GH-48064: [C++] Set ARROW_BUILD_STATIC=ON when features-flight are enabled on CMake presets (#48065) ### Rationale for this change We require static build when we are building flight. The current preset fails. ### What changes are included in this PR? Set `"ARROW_BUILD_STATIC": "ON",` when using `features-flight` ### Are these changes tested? I've tested locally, the build following our build guidelines does not fail anymore. ### Are there any user-facing changes? No * GitHub Issue: #48064 Authored-by: Raúl Cumplido <raulcumplido@gmail.com> Signed-off-by: Raúl Cumplido <raulcumplido@gmail.com>
2025-11-07 11:11:07 +01:00
"ARROW_BUILD_STATIC": "ON",
ARROW-14714: [C++][Doc] Rework CMake presets and add documentation Try to define CMake presets that correspond to common use cases. Switch to version 3 of the format so that `binaryDir` isn't mandatory anymore. Also add display names so that the command line can be more informative. Document the use of CMake presets. Summary of available presets: ``` $ cmake --list-presets Available configure presets: "ninja-debug-minimal" - Debug build without anything enabled "ninja-debug-basic" - Debug build with tests and reduced dependencies "ninja-debug" - Debug build with tests and more optional components "ninja-debug-cuda" - Debug build with tests and CUDA integration "ninja-debug-filesystems" - Debug build with tests and filesystems "ninja-debug-flight" - Debug build with tests and Flight "ninja-debug-gandiva" - Debug build with tests and Gandiva "ninja-debug-python" - Debug build with tests and Python support "ninja-debug-maximal" - Debug build with everything enabled (except benchmarks and CUDA) "ninja-release-minimal" - Release build without anything enabled "ninja-release-basic" - Release build with reduced dependencies "ninja-release" - Release build with more optional components "ninja-release-cuda" - Release build with CUDA integration "ninja-release-flight" - Release build with Flight "ninja-release-gandiva" - Release build with Gandiva "ninja-release-python" - Release build with Python support "ninja-release-maximal" - Release build with everything enabled (except benchmarks and CUDA) "ninja-benchmarks-basic" - Benchmarking build with reduced dependencies "ninja-benchmarks" - Benchmarking build with more optional components ``` Closes #11778 from pitrou/ARROW-14714-cmake-presets Authored-by: Antoine Pitrou <antoine@python.org> Signed-off-by: Krisztián Szűcs <szucs.krisztian@gmail.com>
2021-12-01 20:33:23 +01:00
"ARROW_FLIGHT": "ON"
}
},
GH-35315: [C++][CMake] Add presets for Flight SQL (#35317) ### Rationale for this change The `ninja-release-maximal` preset doesn't enable Flight SQL. ### What changes are included in this PR? Add Flight SQL related presets. ### Are these changes tested? Yes. ### Are there any user-facing changes? Yes. * Closes: #35315 Authored-by: Sutou Kouhei <kou@clear-code.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2023-04-26 09:23:58 +09:00
{
"name": "features-flight-sql",
"inherits": "features-flight",
"hidden": true,
"cacheVariables": {
"ARROW_FLIGHT_SQL": "ON"
}
},
ARROW-14714: [C++][Doc] Rework CMake presets and add documentation Try to define CMake presets that correspond to common use cases. Switch to version 3 of the format so that `binaryDir` isn't mandatory anymore. Also add display names so that the command line can be more informative. Document the use of CMake presets. Summary of available presets: ``` $ cmake --list-presets Available configure presets: "ninja-debug-minimal" - Debug build without anything enabled "ninja-debug-basic" - Debug build with tests and reduced dependencies "ninja-debug" - Debug build with tests and more optional components "ninja-debug-cuda" - Debug build with tests and CUDA integration "ninja-debug-filesystems" - Debug build with tests and filesystems "ninja-debug-flight" - Debug build with tests and Flight "ninja-debug-gandiva" - Debug build with tests and Gandiva "ninja-debug-python" - Debug build with tests and Python support "ninja-debug-maximal" - Debug build with everything enabled (except benchmarks and CUDA) "ninja-release-minimal" - Release build without anything enabled "ninja-release-basic" - Release build with reduced dependencies "ninja-release" - Release build with more optional components "ninja-release-cuda" - Release build with CUDA integration "ninja-release-flight" - Release build with Flight "ninja-release-gandiva" - Release build with Gandiva "ninja-release-python" - Release build with Python support "ninja-release-maximal" - Release build with everything enabled (except benchmarks and CUDA) "ninja-benchmarks-basic" - Benchmarking build with reduced dependencies "ninja-benchmarks" - Benchmarking build with more optional components ``` Closes #11778 from pitrou/ARROW-14714-cmake-presets Authored-by: Antoine Pitrou <antoine@python.org> Signed-off-by: Krisztián Szűcs <szucs.krisztian@gmail.com>
2021-12-01 20:33:23 +01:00
{
"name": "features-gandiva",
"inherits": "features-basic",
"hidden": true,
"cacheVariables": {
"ARROW_GANDIVA": "ON"
}
},
GH-49493: [C++][Python] Add OpenTelemetry to our CMakePresets when bulding python-maximal (#49494) ### Rationale for this change OpenTelemetry can be enabled when building Python. It is currently missing from the `CMakePresets.json` ### What changes are included in this PR? Add a `features-opentelemetry` which is added as part of `features-python-maximal`. This one is used for `ninja-debug-maximal` or other maximal features. ### Are these changes tested? I tested locally with `ninja-debug-maximal` and validated that OpenTelemetry was enabled. I don't think we test our presets on CI (at least I haven't been able to find any `--preset ` presence) ### Are there any user-facing changes? If a user is building using presets, now OpenTelemetry will be built, as expected. * GitHub Issue: #49493 Authored-by: Raúl Cumplido <raulcumplido@gmail.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2026-03-12 07:18:38 +01:00
{
"name": "features-opentelemetry",
"inherits": "features-basic",
"hidden": true,
"cacheVariables": {
"ARROW_WITH_OPENTELEMETRY": "ON"
}
},
ARROW-17868: [C++][Python] Restore the ARROW_PYTHON CMake option (#14273) Restore it but it's marked as a deprecated option. Because the Python component in Apache Arrow C++ was moved to PyArrow by ARROW-16340. It' removed in a feature release. Users should use CMake presets instead of ARROW_PYTHON but CMake presets requires CMake 3.19 or later. Lead-authored-by: Sutou Kouhei <kou@clear-code.com> Co-authored-by: Sutou Kouhei <kou@cozmixng.org> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2022-10-01 20:46:17 +09:00
{
"name": "features-python-minimal",
"inherits": [
GH-34004: [C++] Add a benchmarks-maximal CMake preset (#34005) ### Rationale for this change Add a benchmarks-maximal CMake preset to benchmark all components or to test the compilation of all benchmark files. ### What changes are included in this PR? Along with the new preset, also 1. Fixed indentation of the json file. 2. The "maximal" presets actually include CUDA, so I fixed their display names. ### Are these changes tested? The preset works locally on my machine. ### Are there any user-facing changes? No. * Closes: #34004 Authored-by: Jin Shang <shangjin1997@gmail.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2023-02-03 04:03:59 +08:00
"features-minimal"
ARROW-17868: [C++][Python] Restore the ARROW_PYTHON CMake option (#14273) Restore it but it's marked as a deprecated option. Because the Python component in Apache Arrow C++ was moved to PyArrow by ARROW-16340. It' removed in a feature release. Users should use CMake presets instead of ARROW_PYTHON but CMake presets requires CMake 3.19 or later. Lead-authored-by: Sutou Kouhei <kou@clear-code.com> Co-authored-by: Sutou Kouhei <kou@cozmixng.org> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2022-10-01 20:46:17 +09:00
],
"hidden": true,
"cacheVariables": {
"ARROW_COMPUTE": "ON",
"ARROW_CSV": "ON",
"ARROW_FILESYSTEM": "ON",
"ARROW_JSON": "ON"
}
},
{
"name": "features-python",
"inherits": [
GH-45209: [C++][CMake] Fix the issue that allocator not disabled for sanitizer cmake presets (#45210) ### Rationale for this change I gave the reason in #45209 ### What changes are included in this PR? Adjust the inheritance list order and make a lot of simplification/regrouping/reordering for existing presets the way I see fit. Also introduce a soft rule to order inheritance list: `sanitizer` comes before `features` comes before `base`. Though we can't really mandate such a rule (thus it's "soft") or make it clear in comments (our current cmake dosn't support comment in json), we hope people will notice this pattern and follow it when editing this file. ### Are these changes tested? Manually tested. ### Are there any user-facing changes? None. * GitHub Issue: #45209 Lead-authored-by: Rossi Sun <zanmato1984@gmail.com> Co-authored-by: Sutou Kouhei <kou@cozmixng.org> Signed-off-by: Rossi Sun <zanmato1984@gmail.com>
2025-01-10 23:14:20 +08:00
"features-main",
"features-python-minimal"
ARROW-17868: [C++][Python] Restore the ARROW_PYTHON CMake option (#14273) Restore it but it's marked as a deprecated option. Because the Python component in Apache Arrow C++ was moved to PyArrow by ARROW-16340. It' removed in a feature release. Users should use CMake presets instead of ARROW_PYTHON but CMake presets requires CMake 3.19 or later. Lead-authored-by: Sutou Kouhei <kou@clear-code.com> Co-authored-by: Sutou Kouhei <kou@cozmixng.org> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2022-10-01 20:46:17 +09:00
],
"hidden": true,
"cacheVariables": {
"ARROW_ORC": "ON"
}
},
{
"name": "features-python-maximal",
"inherits": [
GH-34004: [C++] Add a benchmarks-maximal CMake preset (#34005) ### Rationale for this change Add a benchmarks-maximal CMake preset to benchmark all components or to test the compilation of all benchmark files. ### What changes are included in this PR? Along with the new preset, also 1. Fixed indentation of the json file. 2. The "maximal" presets actually include CUDA, so I fixed their display names. ### Are these changes tested? The preset works locally on my machine. ### Are there any user-facing changes? No. * Closes: #34004 Authored-by: Jin Shang <shangjin1997@gmail.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2023-02-03 04:03:59 +08:00
"features-cuda",
"features-filesystems",
GH-35315: [C++][CMake] Add presets for Flight SQL (#35317) ### Rationale for this change The `ninja-release-maximal` preset doesn't enable Flight SQL. ### What changes are included in this PR? Add Flight SQL related presets. ### Are these changes tested? Yes. ### Are there any user-facing changes? Yes. * Closes: #35315 Authored-by: Sutou Kouhei <kou@clear-code.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2023-04-26 09:23:58 +09:00
"features-flight-sql",
GH-34004: [C++] Add a benchmarks-maximal CMake preset (#34005) ### Rationale for this change Add a benchmarks-maximal CMake preset to benchmark all components or to test the compilation of all benchmark files. ### What changes are included in this PR? Along with the new preset, also 1. Fixed indentation of the json file. 2. The "maximal" presets actually include CUDA, so I fixed their display names. ### Are these changes tested? The preset works locally on my machine. ### Are there any user-facing changes? No. * Closes: #34004 Authored-by: Jin Shang <shangjin1997@gmail.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2023-02-03 04:03:59 +08:00
"features-gandiva",
GH-49493: [C++][Python] Add OpenTelemetry to our CMakePresets when bulding python-maximal (#49494) ### Rationale for this change OpenTelemetry can be enabled when building Python. It is currently missing from the `CMakePresets.json` ### What changes are included in this PR? Add a `features-opentelemetry` which is added as part of `features-python-maximal`. This one is used for `ninja-debug-maximal` or other maximal features. ### Are these changes tested? I tested locally with `ninja-debug-maximal` and validated that OpenTelemetry was enabled. I don't think we test our presets on CI (at least I haven't been able to find any `--preset ` presence) ### Are there any user-facing changes? If a user is building using presets, now OpenTelemetry will be built, as expected. * GitHub Issue: #49493 Authored-by: Raúl Cumplido <raulcumplido@gmail.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2026-03-12 07:18:38 +01:00
"features-opentelemetry",
GH-45209: [C++][CMake] Fix the issue that allocator not disabled for sanitizer cmake presets (#45210) ### Rationale for this change I gave the reason in #45209 ### What changes are included in this PR? Adjust the inheritance list order and make a lot of simplification/regrouping/reordering for existing presets the way I see fit. Also introduce a soft rule to order inheritance list: `sanitizer` comes before `features` comes before `base`. Though we can't really mandate such a rule (thus it's "soft") or make it clear in comments (our current cmake dosn't support comment in json), we hope people will notice this pattern and follow it when editing this file. ### Are these changes tested? Manually tested. ### Are there any user-facing changes? None. * GitHub Issue: #45209 Lead-authored-by: Rossi Sun <zanmato1984@gmail.com> Co-authored-by: Sutou Kouhei <kou@cozmixng.org> Signed-off-by: Rossi Sun <zanmato1984@gmail.com>
2025-01-10 23:14:20 +08:00
"features-python"
ARROW-17868: [C++][Python] Restore the ARROW_PYTHON CMake option (#14273) Restore it but it's marked as a deprecated option. Because the Python component in Apache Arrow C++ was moved to PyArrow by ARROW-16340. It' removed in a feature release. Users should use CMake presets instead of ARROW_PYTHON but CMake presets requires CMake 3.19 or later. Lead-authored-by: Sutou Kouhei <kou@clear-code.com> Co-authored-by: Sutou Kouhei <kou@cozmixng.org> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2022-10-01 20:46:17 +09:00
],
"hidden": true,
"cacheVariables": {
"PARQUET_REQUIRE_ENCRYPTION": "ON"
}
},
ARROW-14714: [C++][Doc] Rework CMake presets and add documentation Try to define CMake presets that correspond to common use cases. Switch to version 3 of the format so that `binaryDir` isn't mandatory anymore. Also add display names so that the command line can be more informative. Document the use of CMake presets. Summary of available presets: ``` $ cmake --list-presets Available configure presets: "ninja-debug-minimal" - Debug build without anything enabled "ninja-debug-basic" - Debug build with tests and reduced dependencies "ninja-debug" - Debug build with tests and more optional components "ninja-debug-cuda" - Debug build with tests and CUDA integration "ninja-debug-filesystems" - Debug build with tests and filesystems "ninja-debug-flight" - Debug build with tests and Flight "ninja-debug-gandiva" - Debug build with tests and Gandiva "ninja-debug-python" - Debug build with tests and Python support "ninja-debug-maximal" - Debug build with everything enabled (except benchmarks and CUDA) "ninja-release-minimal" - Release build without anything enabled "ninja-release-basic" - Release build with reduced dependencies "ninja-release" - Release build with more optional components "ninja-release-cuda" - Release build with CUDA integration "ninja-release-flight" - Release build with Flight "ninja-release-gandiva" - Release build with Gandiva "ninja-release-python" - Release build with Python support "ninja-release-maximal" - Release build with everything enabled (except benchmarks and CUDA) "ninja-benchmarks-basic" - Benchmarking build with reduced dependencies "ninja-benchmarks" - Benchmarking build with more optional components ``` Closes #11778 from pitrou/ARROW-14714-cmake-presets Authored-by: Antoine Pitrou <antoine@python.org> Signed-off-by: Krisztián Szűcs <szucs.krisztian@gmail.com>
2021-12-01 20:33:23 +01:00
{
"name": "features-maximal",
ARROW-16158: [C++][R] Rename ARROW_ENGINE to ARROW_SUBSTRAIT At the moment there is not enough non-Substrait functionality to justify a dedicated engine module. In the future there likely will be and so I have some of the general structure around in the C++ (e.g. `ARROW_ENGINE_EXPORT`) but removed any external facing references. Closes #12915 from westonpace/feature/ARROW-16158--rename-engine-to-substrait Lead-authored-by: Weston Pace <weston.pace@gmail.com> Co-authored-by: Neal Richardson <neal.p.richardson@gmail.com> Signed-off-by: Krisztián Szűcs <szucs.krisztian@gmail.com>
2022-04-24 18:15:41 +02:00
"inherits": [
"features-main",
ARROW-17868: [C++][Python] Restore the ARROW_PYTHON CMake option (#14273) Restore it but it's marked as a deprecated option. Because the Python component in Apache Arrow C++ was moved to PyArrow by ARROW-16340. It' removed in a feature release. Users should use CMake presets instead of ARROW_PYTHON but CMake presets requires CMake 3.19 or later. Lead-authored-by: Sutou Kouhei <kou@clear-code.com> Co-authored-by: Sutou Kouhei <kou@cozmixng.org> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2022-10-01 20:46:17 +09:00
"features-python-maximal"
ARROW-16158: [C++][R] Rename ARROW_ENGINE to ARROW_SUBSTRAIT At the moment there is not enough non-Substrait functionality to justify a dedicated engine module. In the future there likely will be and so I have some of the general structure around in the C++ (e.g. `ARROW_ENGINE_EXPORT`) but removed any external facing references. Closes #12915 from westonpace/feature/ARROW-16158--rename-engine-to-substrait Lead-authored-by: Weston Pace <weston.pace@gmail.com> Co-authored-by: Neal Richardson <neal.p.richardson@gmail.com> Signed-off-by: Krisztián Szűcs <szucs.krisztian@gmail.com>
2022-04-24 18:15:41 +02:00
],
ARROW-14714: [C++][Doc] Rework CMake presets and add documentation Try to define CMake presets that correspond to common use cases. Switch to version 3 of the format so that `binaryDir` isn't mandatory anymore. Also add display names so that the command line can be more informative. Document the use of CMake presets. Summary of available presets: ``` $ cmake --list-presets Available configure presets: "ninja-debug-minimal" - Debug build without anything enabled "ninja-debug-basic" - Debug build with tests and reduced dependencies "ninja-debug" - Debug build with tests and more optional components "ninja-debug-cuda" - Debug build with tests and CUDA integration "ninja-debug-filesystems" - Debug build with tests and filesystems "ninja-debug-flight" - Debug build with tests and Flight "ninja-debug-gandiva" - Debug build with tests and Gandiva "ninja-debug-python" - Debug build with tests and Python support "ninja-debug-maximal" - Debug build with everything enabled (except benchmarks and CUDA) "ninja-release-minimal" - Release build without anything enabled "ninja-release-basic" - Release build with reduced dependencies "ninja-release" - Release build with more optional components "ninja-release-cuda" - Release build with CUDA integration "ninja-release-flight" - Release build with Flight "ninja-release-gandiva" - Release build with Gandiva "ninja-release-python" - Release build with Python support "ninja-release-maximal" - Release build with everything enabled (except benchmarks and CUDA) "ninja-benchmarks-basic" - Benchmarking build with reduced dependencies "ninja-benchmarks" - Benchmarking build with more optional components ``` Closes #11778 from pitrou/ARROW-14714-cmake-presets Authored-by: Antoine Pitrou <antoine@python.org> Signed-off-by: Krisztián Szűcs <szucs.krisztian@gmail.com>
2021-12-01 20:33:23 +01:00
"hidden": true,
"cacheVariables": {
"ARROW_BUILD_EXAMPLES": "ON",
"ARROW_BUILD_UTILITIES": "ON",
GH-46522: [C++][FlightRPC] Add Arrow Flight SQL ODBC driver (#40939) ### Rationale for this change An ODBC driver uses the Open Database Connectivity (ODBC) interface that allow applications to access data in DBMS like environment using SQL. As Arrow Flight provides JDBC and ADBC drivers, similarly Arrow Flight can provide ODBC driver. ### What changes are included in this PR? This PR adds an ODBC driver implementation. ### Are these changes tested? This ODBC driver is coming from a production system (SGA) that is tested/ran for a while. ### Are there any user-facing changes? No change, but new user option to use Arrow Flight. * GitHub Issue: #46522 Lead-authored-by: JB Onofré <jbonofre@apache.org> Co-authored-by: Alina (Xi) Li <alina.li@improving.com> Co-authored-by: rscales <robscales@icloud.com> Co-authored-by: Alina (Xi) Li <96995091+alinaliBQ@users.noreply.github.com> Signed-off-by: David Li <li.davidm96@gmail.com>
2025-05-21 03:08:06 +02:00
"ARROW_FLIGHT_SQL_ODBC": "ON",
GH-47787: [C++][FlightRPC] ODBC `msi` Windows installer (#48054) ### Rationale for this change Implement ODBC installer code for Windows. The primary platform for ODBC is MSVC Windows. The version is set to 1.0.0. ### What changes are included in this PR? - ODBC msi installer - Added components to other parts of Arrow, so we can select ODBC component for cpack ### Are these changes tested? Tested locally on MSVC Windows ### Are there any user-facing changes? N/A * GitHub Issue: #47787 Authored-by: Alina (Xi) Li <alina.li@improving.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2026-01-07 18:20:46 -08:00
"ARROW_FLIGHT_SQL_ODBC_INSTALLER": "ON",
ARROW-14714: [C++][Doc] Rework CMake presets and add documentation Try to define CMake presets that correspond to common use cases. Switch to version 3 of the format so that `binaryDir` isn't mandatory anymore. Also add display names so that the command line can be more informative. Document the use of CMake presets. Summary of available presets: ``` $ cmake --list-presets Available configure presets: "ninja-debug-minimal" - Debug build without anything enabled "ninja-debug-basic" - Debug build with tests and reduced dependencies "ninja-debug" - Debug build with tests and more optional components "ninja-debug-cuda" - Debug build with tests and CUDA integration "ninja-debug-filesystems" - Debug build with tests and filesystems "ninja-debug-flight" - Debug build with tests and Flight "ninja-debug-gandiva" - Debug build with tests and Gandiva "ninja-debug-python" - Debug build with tests and Python support "ninja-debug-maximal" - Debug build with everything enabled (except benchmarks and CUDA) "ninja-release-minimal" - Release build without anything enabled "ninja-release-basic" - Release build with reduced dependencies "ninja-release" - Release build with more optional components "ninja-release-cuda" - Release build with CUDA integration "ninja-release-flight" - Release build with Flight "ninja-release-gandiva" - Release build with Gandiva "ninja-release-python" - Release build with Python support "ninja-release-maximal" - Release build with everything enabled (except benchmarks and CUDA) "ninja-benchmarks-basic" - Benchmarking build with reduced dependencies "ninja-benchmarks" - Benchmarking build with more optional components ``` Closes #11778 from pitrou/ARROW-14714-cmake-presets Authored-by: Antoine Pitrou <antoine@python.org> Signed-off-by: Krisztián Szűcs <szucs.krisztian@gmail.com>
2021-12-01 20:33:23 +01:00
"ARROW_TENSORFLOW": "ON",
"PARQUET_BUILD_EXAMPLES": "ON",
GH-45209: [C++][CMake] Fix the issue that allocator not disabled for sanitizer cmake presets (#45210) ### Rationale for this change I gave the reason in #45209 ### What changes are included in this PR? Adjust the inheritance list order and make a lot of simplification/regrouping/reordering for existing presets the way I see fit. Also introduce a soft rule to order inheritance list: `sanitizer` comes before `features` comes before `base`. Though we can't really mandate such a rule (thus it's "soft") or make it clear in comments (our current cmake dosn't support comment in json), we hope people will notice this pattern and follow it when editing this file. ### Are these changes tested? Manually tested. ### Are there any user-facing changes? None. * GitHub Issue: #45209 Lead-authored-by: Rossi Sun <zanmato1984@gmail.com> Co-authored-by: Sutou Kouhei <kou@cozmixng.org> Signed-off-by: Rossi Sun <zanmato1984@gmail.com>
2025-01-10 23:14:20 +08:00
"PARQUET_BUILD_EXECUTABLES": "ON"
}
},
{
"name": "features-emscripten",
"hidden": true,
"cacheVariables": {
"ARROW_ACERO": "ON",
"ARROW_BUILD_SHARED": "OFF",
"ARROW_BUILD_STATIC": "ON",
"ARROW_CSV": "ON",
"ARROW_CUDA": "OFF",
"ARROW_DEPENDENCY_SOURCE": "BUNDLED",
"ARROW_DEPENDENCY_USE_SHARED": "OFF",
"ARROW_ENABLE_THREADING": "OFF",
"ARROW_FLIGHT": "OFF",
"ARROW_IPC": "ON",
"ARROW_JEMALLOC": "OFF",
"ARROW_JSON": "ON",
"ARROW_MIMALLOC": "OFF",
"ARROW_ORC": "ON",
"ARROW_RUNTIME_SIMD_LEVEL": "NONE",
"ARROW_S3": "OFF",
"ARROW_SIMD_LEVEL": "NONE",
"ARROW_SUBSTRAIT": "ON",
"ARROW_WITH_BROTLI": "ON",
"ARROW_WITH_OPENTELEMETRY": "OFF",
"ARROW_WITH_SNAPPY": "ON",
"CMAKE_C_BYTE_ORDER": "LITTLE_ENDIAN"
ARROW-14714: [C++][Doc] Rework CMake presets and add documentation Try to define CMake presets that correspond to common use cases. Switch to version 3 of the format so that `binaryDir` isn't mandatory anymore. Also add display names so that the command line can be more informative. Document the use of CMake presets. Summary of available presets: ``` $ cmake --list-presets Available configure presets: "ninja-debug-minimal" - Debug build without anything enabled "ninja-debug-basic" - Debug build with tests and reduced dependencies "ninja-debug" - Debug build with tests and more optional components "ninja-debug-cuda" - Debug build with tests and CUDA integration "ninja-debug-filesystems" - Debug build with tests and filesystems "ninja-debug-flight" - Debug build with tests and Flight "ninja-debug-gandiva" - Debug build with tests and Gandiva "ninja-debug-python" - Debug build with tests and Python support "ninja-debug-maximal" - Debug build with everything enabled (except benchmarks and CUDA) "ninja-release-minimal" - Release build without anything enabled "ninja-release-basic" - Release build with reduced dependencies "ninja-release" - Release build with more optional components "ninja-release-cuda" - Release build with CUDA integration "ninja-release-flight" - Release build with Flight "ninja-release-gandiva" - Release build with Gandiva "ninja-release-python" - Release build with Python support "ninja-release-maximal" - Release build with everything enabled (except benchmarks and CUDA) "ninja-benchmarks-basic" - Benchmarking build with reduced dependencies "ninja-benchmarks" - Benchmarking build with more optional components ``` Closes #11778 from pitrou/ARROW-14714-cmake-presets Authored-by: Antoine Pitrou <antoine@python.org> Signed-off-by: Krisztián Szűcs <szucs.krisztian@gmail.com>
2021-12-01 20:33:23 +01:00
}
},
GH-42109: [C++][CMake] Add preset for Valgrind (#42110) ### Rationale for this change If we want to use Valgrind for our tests, we need to specify at least the following CMake options: * `ARROW_RUNTIME_SIMD_LEVEL=AVX2` * `ARROW_TEST_MEMCHECK=ON` If we have a CMake preset for Valgrind, we don't need to remember them. ### What changes are included in this PR? Add `features-valgrind` and `ninja-debug-valgrind` preset. `features-valgrind` is a hidden preset. ### Are these changes tested? Yes. I used this to reproduce #42107 on local. ### Are there any user-facing changes? No. * GitHub Issue: #42109 Authored-by: Sutou Kouhei <kou@clear-code.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2024-06-13 18:04:31 +09:00
{
"name": "features-valgrind",
"hidden": true,
"cacheVariables": {
"ARROW_RUNTIME_SIMD_LEVEL": "AVX2",
"ARROW_TEST_MEMCHECK": "ON"
}
},
GH-45206: [C++][CMake] Add sanitizer presets (#45207) ### Rationale for this change See #45206 ### What changes are included in this PR? Add base presets for ASAN/TSAN/UBSAN. And cross product such base presets by `ninja-debug` which is, IMO, the config just enough necessary and likely to need sanitizers' aid. ### Are these changes tested? No need. ### Are there any user-facing changes? None. * GitHub Issue: #45206 Authored-by: Rossi Sun <zanmato1984@gmail.com> Signed-off-by: Rossi Sun <zanmato1984@gmail.com>
2025-01-09 14:01:35 +08:00
{
"name": "sanitizer-asan",
"hidden": true,
"cacheVariables": {
"ARROW_JEMALLOC": "OFF",
GH-45209: [C++][CMake] Fix the issue that allocator not disabled for sanitizer cmake presets (#45210) ### Rationale for this change I gave the reason in #45209 ### What changes are included in this PR? Adjust the inheritance list order and make a lot of simplification/regrouping/reordering for existing presets the way I see fit. Also introduce a soft rule to order inheritance list: `sanitizer` comes before `features` comes before `base`. Though we can't really mandate such a rule (thus it's "soft") or make it clear in comments (our current cmake dosn't support comment in json), we hope people will notice this pattern and follow it when editing this file. ### Are these changes tested? Manually tested. ### Are there any user-facing changes? None. * GitHub Issue: #45209 Lead-authored-by: Rossi Sun <zanmato1984@gmail.com> Co-authored-by: Sutou Kouhei <kou@cozmixng.org> Signed-off-by: Rossi Sun <zanmato1984@gmail.com>
2025-01-10 23:14:20 +08:00
"ARROW_MIMALLOC": "OFF",
"ARROW_USE_ASAN": "ON"
GH-45206: [C++][CMake] Add sanitizer presets (#45207) ### Rationale for this change See #45206 ### What changes are included in this PR? Add base presets for ASAN/TSAN/UBSAN. And cross product such base presets by `ninja-debug` which is, IMO, the config just enough necessary and likely to need sanitizers' aid. ### Are these changes tested? No need. ### Are there any user-facing changes? None. * GitHub Issue: #45206 Authored-by: Rossi Sun <zanmato1984@gmail.com> Signed-off-by: Rossi Sun <zanmato1984@gmail.com>
2025-01-09 14:01:35 +08:00
}
},
{
"name": "sanitizer-tsan",
"hidden": true,
"cacheVariables": {
"ARROW_JEMALLOC": "OFF",
GH-45209: [C++][CMake] Fix the issue that allocator not disabled for sanitizer cmake presets (#45210) ### Rationale for this change I gave the reason in #45209 ### What changes are included in this PR? Adjust the inheritance list order and make a lot of simplification/regrouping/reordering for existing presets the way I see fit. Also introduce a soft rule to order inheritance list: `sanitizer` comes before `features` comes before `base`. Though we can't really mandate such a rule (thus it's "soft") or make it clear in comments (our current cmake dosn't support comment in json), we hope people will notice this pattern and follow it when editing this file. ### Are these changes tested? Manually tested. ### Are there any user-facing changes? None. * GitHub Issue: #45209 Lead-authored-by: Rossi Sun <zanmato1984@gmail.com> Co-authored-by: Sutou Kouhei <kou@cozmixng.org> Signed-off-by: Rossi Sun <zanmato1984@gmail.com>
2025-01-10 23:14:20 +08:00
"ARROW_MIMALLOC": "OFF",
"ARROW_USE_TSAN": "ON"
GH-45206: [C++][CMake] Add sanitizer presets (#45207) ### Rationale for this change See #45206 ### What changes are included in this PR? Add base presets for ASAN/TSAN/UBSAN. And cross product such base presets by `ninja-debug` which is, IMO, the config just enough necessary and likely to need sanitizers' aid. ### Are these changes tested? No need. ### Are there any user-facing changes? None. * GitHub Issue: #45206 Authored-by: Rossi Sun <zanmato1984@gmail.com> Signed-off-by: Rossi Sun <zanmato1984@gmail.com>
2025-01-09 14:01:35 +08:00
}
},
{
"name": "sanitizer-ubsan",
"hidden": true,
"cacheVariables": {
"ARROW_JEMALLOC": "OFF",
GH-45209: [C++][CMake] Fix the issue that allocator not disabled for sanitizer cmake presets (#45210) ### Rationale for this change I gave the reason in #45209 ### What changes are included in this PR? Adjust the inheritance list order and make a lot of simplification/regrouping/reordering for existing presets the way I see fit. Also introduce a soft rule to order inheritance list: `sanitizer` comes before `features` comes before `base`. Though we can't really mandate such a rule (thus it's "soft") or make it clear in comments (our current cmake dosn't support comment in json), we hope people will notice this pattern and follow it when editing this file. ### Are these changes tested? Manually tested. ### Are there any user-facing changes? None. * GitHub Issue: #45209 Lead-authored-by: Rossi Sun <zanmato1984@gmail.com> Co-authored-by: Sutou Kouhei <kou@cozmixng.org> Signed-off-by: Rossi Sun <zanmato1984@gmail.com>
2025-01-10 23:14:20 +08:00
"ARROW_MIMALLOC": "OFF",
"ARROW_USE_UBSAN": "ON"
GH-45206: [C++][CMake] Add sanitizer presets (#45207) ### Rationale for this change See #45206 ### What changes are included in this PR? Add base presets for ASAN/TSAN/UBSAN. And cross product such base presets by `ninja-debug` which is, IMO, the config just enough necessary and likely to need sanitizers' aid. ### Are these changes tested? No need. ### Are there any user-facing changes? None. * GitHub Issue: #45206 Authored-by: Rossi Sun <zanmato1984@gmail.com> Signed-off-by: Rossi Sun <zanmato1984@gmail.com>
2025-01-09 14:01:35 +08:00
}
},
ARROW-14714: [C++][Doc] Rework CMake presets and add documentation Try to define CMake presets that correspond to common use cases. Switch to version 3 of the format so that `binaryDir` isn't mandatory anymore. Also add display names so that the command line can be more informative. Document the use of CMake presets. Summary of available presets: ``` $ cmake --list-presets Available configure presets: "ninja-debug-minimal" - Debug build without anything enabled "ninja-debug-basic" - Debug build with tests and reduced dependencies "ninja-debug" - Debug build with tests and more optional components "ninja-debug-cuda" - Debug build with tests and CUDA integration "ninja-debug-filesystems" - Debug build with tests and filesystems "ninja-debug-flight" - Debug build with tests and Flight "ninja-debug-gandiva" - Debug build with tests and Gandiva "ninja-debug-python" - Debug build with tests and Python support "ninja-debug-maximal" - Debug build with everything enabled (except benchmarks and CUDA) "ninja-release-minimal" - Release build without anything enabled "ninja-release-basic" - Release build with reduced dependencies "ninja-release" - Release build with more optional components "ninja-release-cuda" - Release build with CUDA integration "ninja-release-flight" - Release build with Flight "ninja-release-gandiva" - Release build with Gandiva "ninja-release-python" - Release build with Python support "ninja-release-maximal" - Release build with everything enabled (except benchmarks and CUDA) "ninja-benchmarks-basic" - Benchmarking build with reduced dependencies "ninja-benchmarks" - Benchmarking build with more optional components ``` Closes #11778 from pitrou/ARROW-14714-cmake-presets Authored-by: Antoine Pitrou <antoine@python.org> Signed-off-by: Krisztián Szűcs <szucs.krisztian@gmail.com>
2021-12-01 20:33:23 +01:00
{
"name": "ninja-debug-minimal",
GH-34004: [C++] Add a benchmarks-maximal CMake preset (#34005) ### Rationale for this change Add a benchmarks-maximal CMake preset to benchmark all components or to test the compilation of all benchmark files. ### What changes are included in this PR? Along with the new preset, also 1. Fixed indentation of the json file. 2. The "maximal" presets actually include CUDA, so I fixed their display names. ### Are these changes tested? The preset works locally on my machine. ### Are there any user-facing changes? No. * Closes: #34004 Authored-by: Jin Shang <shangjin1997@gmail.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2023-02-03 04:03:59 +08:00
"inherits": [
GH-45209: [C++][CMake] Fix the issue that allocator not disabled for sanitizer cmake presets (#45210) ### Rationale for this change I gave the reason in #45209 ### What changes are included in this PR? Adjust the inheritance list order and make a lot of simplification/regrouping/reordering for existing presets the way I see fit. Also introduce a soft rule to order inheritance list: `sanitizer` comes before `features` comes before `base`. Though we can't really mandate such a rule (thus it's "soft") or make it clear in comments (our current cmake dosn't support comment in json), we hope people will notice this pattern and follow it when editing this file. ### Are these changes tested? Manually tested. ### Are there any user-facing changes? None. * GitHub Issue: #45209 Lead-authored-by: Rossi Sun <zanmato1984@gmail.com> Co-authored-by: Sutou Kouhei <kou@cozmixng.org> Signed-off-by: Rossi Sun <zanmato1984@gmail.com>
2025-01-10 23:14:20 +08:00
"features-minimal",
"base-debug"
GH-34004: [C++] Add a benchmarks-maximal CMake preset (#34005) ### Rationale for this change Add a benchmarks-maximal CMake preset to benchmark all components or to test the compilation of all benchmark files. ### What changes are included in this PR? Along with the new preset, also 1. Fixed indentation of the json file. 2. The "maximal" presets actually include CUDA, so I fixed their display names. ### Are these changes tested? The preset works locally on my machine. ### Are there any user-facing changes? No. * Closes: #34004 Authored-by: Jin Shang <shangjin1997@gmail.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2023-02-03 04:03:59 +08:00
],
ARROW-14714: [C++][Doc] Rework CMake presets and add documentation Try to define CMake presets that correspond to common use cases. Switch to version 3 of the format so that `binaryDir` isn't mandatory anymore. Also add display names so that the command line can be more informative. Document the use of CMake presets. Summary of available presets: ``` $ cmake --list-presets Available configure presets: "ninja-debug-minimal" - Debug build without anything enabled "ninja-debug-basic" - Debug build with tests and reduced dependencies "ninja-debug" - Debug build with tests and more optional components "ninja-debug-cuda" - Debug build with tests and CUDA integration "ninja-debug-filesystems" - Debug build with tests and filesystems "ninja-debug-flight" - Debug build with tests and Flight "ninja-debug-gandiva" - Debug build with tests and Gandiva "ninja-debug-python" - Debug build with tests and Python support "ninja-debug-maximal" - Debug build with everything enabled (except benchmarks and CUDA) "ninja-release-minimal" - Release build without anything enabled "ninja-release-basic" - Release build with reduced dependencies "ninja-release" - Release build with more optional components "ninja-release-cuda" - Release build with CUDA integration "ninja-release-flight" - Release build with Flight "ninja-release-gandiva" - Release build with Gandiva "ninja-release-python" - Release build with Python support "ninja-release-maximal" - Release build with everything enabled (except benchmarks and CUDA) "ninja-benchmarks-basic" - Benchmarking build with reduced dependencies "ninja-benchmarks" - Benchmarking build with more optional components ``` Closes #11778 from pitrou/ARROW-14714-cmake-presets Authored-by: Antoine Pitrou <antoine@python.org> Signed-off-by: Krisztián Szűcs <szucs.krisztian@gmail.com>
2021-12-01 20:33:23 +01:00
"displayName": "Debug build without anything enabled",
"cacheVariables": {
"ARROW_BUILD_INTEGRATION": "OFF",
"ARROW_BUILD_TESTS": "OFF"
}
},
{
"name": "ninja-debug-basic",
GH-34004: [C++] Add a benchmarks-maximal CMake preset (#34005) ### Rationale for this change Add a benchmarks-maximal CMake preset to benchmark all components or to test the compilation of all benchmark files. ### What changes are included in this PR? Along with the new preset, also 1. Fixed indentation of the json file. 2. The "maximal" presets actually include CUDA, so I fixed their display names. ### Are these changes tested? The preset works locally on my machine. ### Are there any user-facing changes? No. * Closes: #34004 Authored-by: Jin Shang <shangjin1997@gmail.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2023-02-03 04:03:59 +08:00
"inherits": [
GH-45209: [C++][CMake] Fix the issue that allocator not disabled for sanitizer cmake presets (#45210) ### Rationale for this change I gave the reason in #45209 ### What changes are included in this PR? Adjust the inheritance list order and make a lot of simplification/regrouping/reordering for existing presets the way I see fit. Also introduce a soft rule to order inheritance list: `sanitizer` comes before `features` comes before `base`. Though we can't really mandate such a rule (thus it's "soft") or make it clear in comments (our current cmake dosn't support comment in json), we hope people will notice this pattern and follow it when editing this file. ### Are these changes tested? Manually tested. ### Are there any user-facing changes? None. * GitHub Issue: #45209 Lead-authored-by: Rossi Sun <zanmato1984@gmail.com> Co-authored-by: Sutou Kouhei <kou@cozmixng.org> Signed-off-by: Rossi Sun <zanmato1984@gmail.com>
2025-01-10 23:14:20 +08:00
"features-basic",
"base-debug"
GH-34004: [C++] Add a benchmarks-maximal CMake preset (#34005) ### Rationale for this change Add a benchmarks-maximal CMake preset to benchmark all components or to test the compilation of all benchmark files. ### What changes are included in this PR? Along with the new preset, also 1. Fixed indentation of the json file. 2. The "maximal" presets actually include CUDA, so I fixed their display names. ### Are these changes tested? The preset works locally on my machine. ### Are there any user-facing changes? No. * Closes: #34004 Authored-by: Jin Shang <shangjin1997@gmail.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2023-02-03 04:03:59 +08:00
],
ARROW-14714: [C++][Doc] Rework CMake presets and add documentation Try to define CMake presets that correspond to common use cases. Switch to version 3 of the format so that `binaryDir` isn't mandatory anymore. Also add display names so that the command line can be more informative. Document the use of CMake presets. Summary of available presets: ``` $ cmake --list-presets Available configure presets: "ninja-debug-minimal" - Debug build without anything enabled "ninja-debug-basic" - Debug build with tests and reduced dependencies "ninja-debug" - Debug build with tests and more optional components "ninja-debug-cuda" - Debug build with tests and CUDA integration "ninja-debug-filesystems" - Debug build with tests and filesystems "ninja-debug-flight" - Debug build with tests and Flight "ninja-debug-gandiva" - Debug build with tests and Gandiva "ninja-debug-python" - Debug build with tests and Python support "ninja-debug-maximal" - Debug build with everything enabled (except benchmarks and CUDA) "ninja-release-minimal" - Release build without anything enabled "ninja-release-basic" - Release build with reduced dependencies "ninja-release" - Release build with more optional components "ninja-release-cuda" - Release build with CUDA integration "ninja-release-flight" - Release build with Flight "ninja-release-gandiva" - Release build with Gandiva "ninja-release-python" - Release build with Python support "ninja-release-maximal" - Release build with everything enabled (except benchmarks and CUDA) "ninja-benchmarks-basic" - Benchmarking build with reduced dependencies "ninja-benchmarks" - Benchmarking build with more optional components ``` Closes #11778 from pitrou/ARROW-14714-cmake-presets Authored-by: Antoine Pitrou <antoine@python.org> Signed-off-by: Krisztián Szűcs <szucs.krisztian@gmail.com>
2021-12-01 20:33:23 +01:00
"displayName": "Debug build with tests and reduced dependencies",
"cacheVariables": {}
},
{
"name": "ninja-debug",
GH-34004: [C++] Add a benchmarks-maximal CMake preset (#34005) ### Rationale for this change Add a benchmarks-maximal CMake preset to benchmark all components or to test the compilation of all benchmark files. ### What changes are included in this PR? Along with the new preset, also 1. Fixed indentation of the json file. 2. The "maximal" presets actually include CUDA, so I fixed their display names. ### Are these changes tested? The preset works locally on my machine. ### Are there any user-facing changes? No. * Closes: #34004 Authored-by: Jin Shang <shangjin1997@gmail.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2023-02-03 04:03:59 +08:00
"inherits": [
GH-45209: [C++][CMake] Fix the issue that allocator not disabled for sanitizer cmake presets (#45210) ### Rationale for this change I gave the reason in #45209 ### What changes are included in this PR? Adjust the inheritance list order and make a lot of simplification/regrouping/reordering for existing presets the way I see fit. Also introduce a soft rule to order inheritance list: `sanitizer` comes before `features` comes before `base`. Though we can't really mandate such a rule (thus it's "soft") or make it clear in comments (our current cmake dosn't support comment in json), we hope people will notice this pattern and follow it when editing this file. ### Are these changes tested? Manually tested. ### Are there any user-facing changes? None. * GitHub Issue: #45209 Lead-authored-by: Rossi Sun <zanmato1984@gmail.com> Co-authored-by: Sutou Kouhei <kou@cozmixng.org> Signed-off-by: Rossi Sun <zanmato1984@gmail.com>
2025-01-10 23:14:20 +08:00
"features-main",
"base-debug"
GH-34004: [C++] Add a benchmarks-maximal CMake preset (#34005) ### Rationale for this change Add a benchmarks-maximal CMake preset to benchmark all components or to test the compilation of all benchmark files. ### What changes are included in this PR? Along with the new preset, also 1. Fixed indentation of the json file. 2. The "maximal" presets actually include CUDA, so I fixed their display names. ### Are these changes tested? The preset works locally on my machine. ### Are there any user-facing changes? No. * Closes: #34004 Authored-by: Jin Shang <shangjin1997@gmail.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2023-02-03 04:03:59 +08:00
],
ARROW-14714: [C++][Doc] Rework CMake presets and add documentation Try to define CMake presets that correspond to common use cases. Switch to version 3 of the format so that `binaryDir` isn't mandatory anymore. Also add display names so that the command line can be more informative. Document the use of CMake presets. Summary of available presets: ``` $ cmake --list-presets Available configure presets: "ninja-debug-minimal" - Debug build without anything enabled "ninja-debug-basic" - Debug build with tests and reduced dependencies "ninja-debug" - Debug build with tests and more optional components "ninja-debug-cuda" - Debug build with tests and CUDA integration "ninja-debug-filesystems" - Debug build with tests and filesystems "ninja-debug-flight" - Debug build with tests and Flight "ninja-debug-gandiva" - Debug build with tests and Gandiva "ninja-debug-python" - Debug build with tests and Python support "ninja-debug-maximal" - Debug build with everything enabled (except benchmarks and CUDA) "ninja-release-minimal" - Release build without anything enabled "ninja-release-basic" - Release build with reduced dependencies "ninja-release" - Release build with more optional components "ninja-release-cuda" - Release build with CUDA integration "ninja-release-flight" - Release build with Flight "ninja-release-gandiva" - Release build with Gandiva "ninja-release-python" - Release build with Python support "ninja-release-maximal" - Release build with everything enabled (except benchmarks and CUDA) "ninja-benchmarks-basic" - Benchmarking build with reduced dependencies "ninja-benchmarks" - Benchmarking build with more optional components ``` Closes #11778 from pitrou/ARROW-14714-cmake-presets Authored-by: Antoine Pitrou <antoine@python.org> Signed-off-by: Krisztián Szűcs <szucs.krisztian@gmail.com>
2021-12-01 20:33:23 +01:00
"displayName": "Debug build with tests and more optional components",
"cacheVariables": {}
},
{
"name": "ninja-debug-cuda",
GH-34004: [C++] Add a benchmarks-maximal CMake preset (#34005) ### Rationale for this change Add a benchmarks-maximal CMake preset to benchmark all components or to test the compilation of all benchmark files. ### What changes are included in this PR? Along with the new preset, also 1. Fixed indentation of the json file. 2. The "maximal" presets actually include CUDA, so I fixed their display names. ### Are these changes tested? The preset works locally on my machine. ### Are there any user-facing changes? No. * Closes: #34004 Authored-by: Jin Shang <shangjin1997@gmail.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2023-02-03 04:03:59 +08:00
"inherits": [
GH-45209: [C++][CMake] Fix the issue that allocator not disabled for sanitizer cmake presets (#45210) ### Rationale for this change I gave the reason in #45209 ### What changes are included in this PR? Adjust the inheritance list order and make a lot of simplification/regrouping/reordering for existing presets the way I see fit. Also introduce a soft rule to order inheritance list: `sanitizer` comes before `features` comes before `base`. Though we can't really mandate such a rule (thus it's "soft") or make it clear in comments (our current cmake dosn't support comment in json), we hope people will notice this pattern and follow it when editing this file. ### Are these changes tested? Manually tested. ### Are there any user-facing changes? None. * GitHub Issue: #45209 Lead-authored-by: Rossi Sun <zanmato1984@gmail.com> Co-authored-by: Sutou Kouhei <kou@cozmixng.org> Signed-off-by: Rossi Sun <zanmato1984@gmail.com>
2025-01-10 23:14:20 +08:00
"features-cuda",
"base-debug"
GH-34004: [C++] Add a benchmarks-maximal CMake preset (#34005) ### Rationale for this change Add a benchmarks-maximal CMake preset to benchmark all components or to test the compilation of all benchmark files. ### What changes are included in this PR? Along with the new preset, also 1. Fixed indentation of the json file. 2. The "maximal" presets actually include CUDA, so I fixed their display names. ### Are these changes tested? The preset works locally on my machine. ### Are there any user-facing changes? No. * Closes: #34004 Authored-by: Jin Shang <shangjin1997@gmail.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2023-02-03 04:03:59 +08:00
],
ARROW-14714: [C++][Doc] Rework CMake presets and add documentation Try to define CMake presets that correspond to common use cases. Switch to version 3 of the format so that `binaryDir` isn't mandatory anymore. Also add display names so that the command line can be more informative. Document the use of CMake presets. Summary of available presets: ``` $ cmake --list-presets Available configure presets: "ninja-debug-minimal" - Debug build without anything enabled "ninja-debug-basic" - Debug build with tests and reduced dependencies "ninja-debug" - Debug build with tests and more optional components "ninja-debug-cuda" - Debug build with tests and CUDA integration "ninja-debug-filesystems" - Debug build with tests and filesystems "ninja-debug-flight" - Debug build with tests and Flight "ninja-debug-gandiva" - Debug build with tests and Gandiva "ninja-debug-python" - Debug build with tests and Python support "ninja-debug-maximal" - Debug build with everything enabled (except benchmarks and CUDA) "ninja-release-minimal" - Release build without anything enabled "ninja-release-basic" - Release build with reduced dependencies "ninja-release" - Release build with more optional components "ninja-release-cuda" - Release build with CUDA integration "ninja-release-flight" - Release build with Flight "ninja-release-gandiva" - Release build with Gandiva "ninja-release-python" - Release build with Python support "ninja-release-maximal" - Release build with everything enabled (except benchmarks and CUDA) "ninja-benchmarks-basic" - Benchmarking build with reduced dependencies "ninja-benchmarks" - Benchmarking build with more optional components ``` Closes #11778 from pitrou/ARROW-14714-cmake-presets Authored-by: Antoine Pitrou <antoine@python.org> Signed-off-by: Krisztián Szűcs <szucs.krisztian@gmail.com>
2021-12-01 20:33:23 +01:00
"displayName": "Debug build with tests and CUDA integration",
"cacheVariables": {}
},
{
"name": "ninja-debug-filesystems",
GH-34004: [C++] Add a benchmarks-maximal CMake preset (#34005) ### Rationale for this change Add a benchmarks-maximal CMake preset to benchmark all components or to test the compilation of all benchmark files. ### What changes are included in this PR? Along with the new preset, also 1. Fixed indentation of the json file. 2. The "maximal" presets actually include CUDA, so I fixed their display names. ### Are these changes tested? The preset works locally on my machine. ### Are there any user-facing changes? No. * Closes: #34004 Authored-by: Jin Shang <shangjin1997@gmail.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2023-02-03 04:03:59 +08:00
"inherits": [
GH-45209: [C++][CMake] Fix the issue that allocator not disabled for sanitizer cmake presets (#45210) ### Rationale for this change I gave the reason in #45209 ### What changes are included in this PR? Adjust the inheritance list order and make a lot of simplification/regrouping/reordering for existing presets the way I see fit. Also introduce a soft rule to order inheritance list: `sanitizer` comes before `features` comes before `base`. Though we can't really mandate such a rule (thus it's "soft") or make it clear in comments (our current cmake dosn't support comment in json), we hope people will notice this pattern and follow it when editing this file. ### Are these changes tested? Manually tested. ### Are there any user-facing changes? None. * GitHub Issue: #45209 Lead-authored-by: Rossi Sun <zanmato1984@gmail.com> Co-authored-by: Sutou Kouhei <kou@cozmixng.org> Signed-off-by: Rossi Sun <zanmato1984@gmail.com>
2025-01-10 23:14:20 +08:00
"features-filesystems",
"base-debug"
GH-34004: [C++] Add a benchmarks-maximal CMake preset (#34005) ### Rationale for this change Add a benchmarks-maximal CMake preset to benchmark all components or to test the compilation of all benchmark files. ### What changes are included in this PR? Along with the new preset, also 1. Fixed indentation of the json file. 2. The "maximal" presets actually include CUDA, so I fixed their display names. ### Are these changes tested? The preset works locally on my machine. ### Are there any user-facing changes? No. * Closes: #34004 Authored-by: Jin Shang <shangjin1997@gmail.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2023-02-03 04:03:59 +08:00
],
ARROW-14714: [C++][Doc] Rework CMake presets and add documentation Try to define CMake presets that correspond to common use cases. Switch to version 3 of the format so that `binaryDir` isn't mandatory anymore. Also add display names so that the command line can be more informative. Document the use of CMake presets. Summary of available presets: ``` $ cmake --list-presets Available configure presets: "ninja-debug-minimal" - Debug build without anything enabled "ninja-debug-basic" - Debug build with tests and reduced dependencies "ninja-debug" - Debug build with tests and more optional components "ninja-debug-cuda" - Debug build with tests and CUDA integration "ninja-debug-filesystems" - Debug build with tests and filesystems "ninja-debug-flight" - Debug build with tests and Flight "ninja-debug-gandiva" - Debug build with tests and Gandiva "ninja-debug-python" - Debug build with tests and Python support "ninja-debug-maximal" - Debug build with everything enabled (except benchmarks and CUDA) "ninja-release-minimal" - Release build without anything enabled "ninja-release-basic" - Release build with reduced dependencies "ninja-release" - Release build with more optional components "ninja-release-cuda" - Release build with CUDA integration "ninja-release-flight" - Release build with Flight "ninja-release-gandiva" - Release build with Gandiva "ninja-release-python" - Release build with Python support "ninja-release-maximal" - Release build with everything enabled (except benchmarks and CUDA) "ninja-benchmarks-basic" - Benchmarking build with reduced dependencies "ninja-benchmarks" - Benchmarking build with more optional components ``` Closes #11778 from pitrou/ARROW-14714-cmake-presets Authored-by: Antoine Pitrou <antoine@python.org> Signed-off-by: Krisztián Szűcs <szucs.krisztian@gmail.com>
2021-12-01 20:33:23 +01:00
"displayName": "Debug build with tests and filesystems",
"cacheVariables": {}
},
{
"name": "ninja-debug-flight",
GH-34004: [C++] Add a benchmarks-maximal CMake preset (#34005) ### Rationale for this change Add a benchmarks-maximal CMake preset to benchmark all components or to test the compilation of all benchmark files. ### What changes are included in this PR? Along with the new preset, also 1. Fixed indentation of the json file. 2. The "maximal" presets actually include CUDA, so I fixed their display names. ### Are these changes tested? The preset works locally on my machine. ### Are there any user-facing changes? No. * Closes: #34004 Authored-by: Jin Shang <shangjin1997@gmail.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2023-02-03 04:03:59 +08:00
"inherits": [
GH-45209: [C++][CMake] Fix the issue that allocator not disabled for sanitizer cmake presets (#45210) ### Rationale for this change I gave the reason in #45209 ### What changes are included in this PR? Adjust the inheritance list order and make a lot of simplification/regrouping/reordering for existing presets the way I see fit. Also introduce a soft rule to order inheritance list: `sanitizer` comes before `features` comes before `base`. Though we can't really mandate such a rule (thus it's "soft") or make it clear in comments (our current cmake dosn't support comment in json), we hope people will notice this pattern and follow it when editing this file. ### Are these changes tested? Manually tested. ### Are there any user-facing changes? None. * GitHub Issue: #45209 Lead-authored-by: Rossi Sun <zanmato1984@gmail.com> Co-authored-by: Sutou Kouhei <kou@cozmixng.org> Signed-off-by: Rossi Sun <zanmato1984@gmail.com>
2025-01-10 23:14:20 +08:00
"features-flight",
"base-debug"
GH-34004: [C++] Add a benchmarks-maximal CMake preset (#34005) ### Rationale for this change Add a benchmarks-maximal CMake preset to benchmark all components or to test the compilation of all benchmark files. ### What changes are included in this PR? Along with the new preset, also 1. Fixed indentation of the json file. 2. The "maximal" presets actually include CUDA, so I fixed their display names. ### Are these changes tested? The preset works locally on my machine. ### Are there any user-facing changes? No. * Closes: #34004 Authored-by: Jin Shang <shangjin1997@gmail.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2023-02-03 04:03:59 +08:00
],
ARROW-14714: [C++][Doc] Rework CMake presets and add documentation Try to define CMake presets that correspond to common use cases. Switch to version 3 of the format so that `binaryDir` isn't mandatory anymore. Also add display names so that the command line can be more informative. Document the use of CMake presets. Summary of available presets: ``` $ cmake --list-presets Available configure presets: "ninja-debug-minimal" - Debug build without anything enabled "ninja-debug-basic" - Debug build with tests and reduced dependencies "ninja-debug" - Debug build with tests and more optional components "ninja-debug-cuda" - Debug build with tests and CUDA integration "ninja-debug-filesystems" - Debug build with tests and filesystems "ninja-debug-flight" - Debug build with tests and Flight "ninja-debug-gandiva" - Debug build with tests and Gandiva "ninja-debug-python" - Debug build with tests and Python support "ninja-debug-maximal" - Debug build with everything enabled (except benchmarks and CUDA) "ninja-release-minimal" - Release build without anything enabled "ninja-release-basic" - Release build with reduced dependencies "ninja-release" - Release build with more optional components "ninja-release-cuda" - Release build with CUDA integration "ninja-release-flight" - Release build with Flight "ninja-release-gandiva" - Release build with Gandiva "ninja-release-python" - Release build with Python support "ninja-release-maximal" - Release build with everything enabled (except benchmarks and CUDA) "ninja-benchmarks-basic" - Benchmarking build with reduced dependencies "ninja-benchmarks" - Benchmarking build with more optional components ``` Closes #11778 from pitrou/ARROW-14714-cmake-presets Authored-by: Antoine Pitrou <antoine@python.org> Signed-off-by: Krisztián Szűcs <szucs.krisztian@gmail.com>
2021-12-01 20:33:23 +01:00
"displayName": "Debug build with tests and Flight",
"cacheVariables": {}
},
GH-35315: [C++][CMake] Add presets for Flight SQL (#35317) ### Rationale for this change The `ninja-release-maximal` preset doesn't enable Flight SQL. ### What changes are included in this PR? Add Flight SQL related presets. ### Are these changes tested? Yes. ### Are there any user-facing changes? Yes. * Closes: #35315 Authored-by: Sutou Kouhei <kou@clear-code.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2023-04-26 09:23:58 +09:00
{
"name": "ninja-debug-flight-sql",
"inherits": [
GH-45209: [C++][CMake] Fix the issue that allocator not disabled for sanitizer cmake presets (#45210) ### Rationale for this change I gave the reason in #45209 ### What changes are included in this PR? Adjust the inheritance list order and make a lot of simplification/regrouping/reordering for existing presets the way I see fit. Also introduce a soft rule to order inheritance list: `sanitizer` comes before `features` comes before `base`. Though we can't really mandate such a rule (thus it's "soft") or make it clear in comments (our current cmake dosn't support comment in json), we hope people will notice this pattern and follow it when editing this file. ### Are these changes tested? Manually tested. ### Are there any user-facing changes? None. * GitHub Issue: #45209 Lead-authored-by: Rossi Sun <zanmato1984@gmail.com> Co-authored-by: Sutou Kouhei <kou@cozmixng.org> Signed-off-by: Rossi Sun <zanmato1984@gmail.com>
2025-01-10 23:14:20 +08:00
"features-flight-sql",
"base-debug"
GH-35315: [C++][CMake] Add presets for Flight SQL (#35317) ### Rationale for this change The `ninja-release-maximal` preset doesn't enable Flight SQL. ### What changes are included in this PR? Add Flight SQL related presets. ### Are these changes tested? Yes. ### Are there any user-facing changes? Yes. * Closes: #35315 Authored-by: Sutou Kouhei <kou@clear-code.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2023-04-26 09:23:58 +09:00
],
"displayName": "Debug build with tests and Flight SQL",
"cacheVariables": {}
},
GH-48575: [C++][FlightRPC] Standalone ODBC macOS CI (#48577) ### Rationale for this change #48575 ### What changes are included in this PR? - Add new ODBC workflow for macOS Intel 15 and 14 arm64. - Added ODBC build fixes to enable build on macOS CI. ### Are these changes tested? Tested in CI and local macOS Intel and M1 environments. ### Are there any user-facing changes? N/A * GitHub Issue: #48575 Lead-authored-by: Alina (Xi) Li <alina.li@improving.com> Co-authored-by: justing-bq <62349012+justing-bq@users.noreply.github.com> Co-authored-by: Victor Tsang <victor.tsang@improving.com> Co-authored-by: Alina (Xi) Li <alinal@bitquilltech.com> Co-authored-by: vic-tsang <victor.tsang@improving.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2026-02-07 03:54:25 -08:00
{
"name": "ninja-debug-flight-sql-odbc",
"inherits": [
"features-flight-sql",
"base-debug"
],
"displayName": "Debug build with tests and Flight SQL ODBC",
"cacheVariables": {
"ARROW_FLIGHT_SQL_ODBC": "ON"
}
},
ARROW-14714: [C++][Doc] Rework CMake presets and add documentation Try to define CMake presets that correspond to common use cases. Switch to version 3 of the format so that `binaryDir` isn't mandatory anymore. Also add display names so that the command line can be more informative. Document the use of CMake presets. Summary of available presets: ``` $ cmake --list-presets Available configure presets: "ninja-debug-minimal" - Debug build without anything enabled "ninja-debug-basic" - Debug build with tests and reduced dependencies "ninja-debug" - Debug build with tests and more optional components "ninja-debug-cuda" - Debug build with tests and CUDA integration "ninja-debug-filesystems" - Debug build with tests and filesystems "ninja-debug-flight" - Debug build with tests and Flight "ninja-debug-gandiva" - Debug build with tests and Gandiva "ninja-debug-python" - Debug build with tests and Python support "ninja-debug-maximal" - Debug build with everything enabled (except benchmarks and CUDA) "ninja-release-minimal" - Release build without anything enabled "ninja-release-basic" - Release build with reduced dependencies "ninja-release" - Release build with more optional components "ninja-release-cuda" - Release build with CUDA integration "ninja-release-flight" - Release build with Flight "ninja-release-gandiva" - Release build with Gandiva "ninja-release-python" - Release build with Python support "ninja-release-maximal" - Release build with everything enabled (except benchmarks and CUDA) "ninja-benchmarks-basic" - Benchmarking build with reduced dependencies "ninja-benchmarks" - Benchmarking build with more optional components ``` Closes #11778 from pitrou/ARROW-14714-cmake-presets Authored-by: Antoine Pitrou <antoine@python.org> Signed-off-by: Krisztián Szűcs <szucs.krisztian@gmail.com>
2021-12-01 20:33:23 +01:00
{
"name": "ninja-debug-gandiva",
GH-34004: [C++] Add a benchmarks-maximal CMake preset (#34005) ### Rationale for this change Add a benchmarks-maximal CMake preset to benchmark all components or to test the compilation of all benchmark files. ### What changes are included in this PR? Along with the new preset, also 1. Fixed indentation of the json file. 2. The "maximal" presets actually include CUDA, so I fixed their display names. ### Are these changes tested? The preset works locally on my machine. ### Are there any user-facing changes? No. * Closes: #34004 Authored-by: Jin Shang <shangjin1997@gmail.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2023-02-03 04:03:59 +08:00
"inherits": [
GH-45209: [C++][CMake] Fix the issue that allocator not disabled for sanitizer cmake presets (#45210) ### Rationale for this change I gave the reason in #45209 ### What changes are included in this PR? Adjust the inheritance list order and make a lot of simplification/regrouping/reordering for existing presets the way I see fit. Also introduce a soft rule to order inheritance list: `sanitizer` comes before `features` comes before `base`. Though we can't really mandate such a rule (thus it's "soft") or make it clear in comments (our current cmake dosn't support comment in json), we hope people will notice this pattern and follow it when editing this file. ### Are these changes tested? Manually tested. ### Are there any user-facing changes? None. * GitHub Issue: #45209 Lead-authored-by: Rossi Sun <zanmato1984@gmail.com> Co-authored-by: Sutou Kouhei <kou@cozmixng.org> Signed-off-by: Rossi Sun <zanmato1984@gmail.com>
2025-01-10 23:14:20 +08:00
"features-gandiva",
"base-debug"
GH-34004: [C++] Add a benchmarks-maximal CMake preset (#34005) ### Rationale for this change Add a benchmarks-maximal CMake preset to benchmark all components or to test the compilation of all benchmark files. ### What changes are included in this PR? Along with the new preset, also 1. Fixed indentation of the json file. 2. The "maximal" presets actually include CUDA, so I fixed their display names. ### Are these changes tested? The preset works locally on my machine. ### Are there any user-facing changes? No. * Closes: #34004 Authored-by: Jin Shang <shangjin1997@gmail.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2023-02-03 04:03:59 +08:00
],
ARROW-14714: [C++][Doc] Rework CMake presets and add documentation Try to define CMake presets that correspond to common use cases. Switch to version 3 of the format so that `binaryDir` isn't mandatory anymore. Also add display names so that the command line can be more informative. Document the use of CMake presets. Summary of available presets: ``` $ cmake --list-presets Available configure presets: "ninja-debug-minimal" - Debug build without anything enabled "ninja-debug-basic" - Debug build with tests and reduced dependencies "ninja-debug" - Debug build with tests and more optional components "ninja-debug-cuda" - Debug build with tests and CUDA integration "ninja-debug-filesystems" - Debug build with tests and filesystems "ninja-debug-flight" - Debug build with tests and Flight "ninja-debug-gandiva" - Debug build with tests and Gandiva "ninja-debug-python" - Debug build with tests and Python support "ninja-debug-maximal" - Debug build with everything enabled (except benchmarks and CUDA) "ninja-release-minimal" - Release build without anything enabled "ninja-release-basic" - Release build with reduced dependencies "ninja-release" - Release build with more optional components "ninja-release-cuda" - Release build with CUDA integration "ninja-release-flight" - Release build with Flight "ninja-release-gandiva" - Release build with Gandiva "ninja-release-python" - Release build with Python support "ninja-release-maximal" - Release build with everything enabled (except benchmarks and CUDA) "ninja-benchmarks-basic" - Benchmarking build with reduced dependencies "ninja-benchmarks" - Benchmarking build with more optional components ``` Closes #11778 from pitrou/ARROW-14714-cmake-presets Authored-by: Antoine Pitrou <antoine@python.org> Signed-off-by: Krisztián Szűcs <szucs.krisztian@gmail.com>
2021-12-01 20:33:23 +01:00
"displayName": "Debug build with tests and Gandiva",
"cacheVariables": {}
},
ARROW-17868: [C++][Python] Restore the ARROW_PYTHON CMake option (#14273) Restore it but it's marked as a deprecated option. Because the Python component in Apache Arrow C++ was moved to PyArrow by ARROW-16340. It' removed in a feature release. Users should use CMake presets instead of ARROW_PYTHON but CMake presets requires CMake 3.19 or later. Lead-authored-by: Sutou Kouhei <kou@clear-code.com> Co-authored-by: Sutou Kouhei <kou@cozmixng.org> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2022-10-01 20:46:17 +09:00
{
"name": "ninja-debug-python-minimal",
GH-34004: [C++] Add a benchmarks-maximal CMake preset (#34005) ### Rationale for this change Add a benchmarks-maximal CMake preset to benchmark all components or to test the compilation of all benchmark files. ### What changes are included in this PR? Along with the new preset, also 1. Fixed indentation of the json file. 2. The "maximal" presets actually include CUDA, so I fixed their display names. ### Are these changes tested? The preset works locally on my machine. ### Are there any user-facing changes? No. * Closes: #34004 Authored-by: Jin Shang <shangjin1997@gmail.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2023-02-03 04:03:59 +08:00
"inherits": [
GH-45209: [C++][CMake] Fix the issue that allocator not disabled for sanitizer cmake presets (#45210) ### Rationale for this change I gave the reason in #45209 ### What changes are included in this PR? Adjust the inheritance list order and make a lot of simplification/regrouping/reordering for existing presets the way I see fit. Also introduce a soft rule to order inheritance list: `sanitizer` comes before `features` comes before `base`. Though we can't really mandate such a rule (thus it's "soft") or make it clear in comments (our current cmake dosn't support comment in json), we hope people will notice this pattern and follow it when editing this file. ### Are these changes tested? Manually tested. ### Are there any user-facing changes? None. * GitHub Issue: #45209 Lead-authored-by: Rossi Sun <zanmato1984@gmail.com> Co-authored-by: Sutou Kouhei <kou@cozmixng.org> Signed-off-by: Rossi Sun <zanmato1984@gmail.com>
2025-01-10 23:14:20 +08:00
"features-python-minimal",
"base-debug"
GH-34004: [C++] Add a benchmarks-maximal CMake preset (#34005) ### Rationale for this change Add a benchmarks-maximal CMake preset to benchmark all components or to test the compilation of all benchmark files. ### What changes are included in this PR? Along with the new preset, also 1. Fixed indentation of the json file. 2. The "maximal" presets actually include CUDA, so I fixed their display names. ### Are these changes tested? The preset works locally on my machine. ### Are there any user-facing changes? No. * Closes: #34004 Authored-by: Jin Shang <shangjin1997@gmail.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2023-02-03 04:03:59 +08:00
],
ARROW-17868: [C++][Python] Restore the ARROW_PYTHON CMake option (#14273) Restore it but it's marked as a deprecated option. Because the Python component in Apache Arrow C++ was moved to PyArrow by ARROW-16340. It' removed in a feature release. Users should use CMake presets instead of ARROW_PYTHON but CMake presets requires CMake 3.19 or later. Lead-authored-by: Sutou Kouhei <kou@clear-code.com> Co-authored-by: Sutou Kouhei <kou@cozmixng.org> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2022-10-01 20:46:17 +09:00
"displayName": "Debug build for PyArrow with minimal features",
"cacheVariables": {}
},
{
"name": "ninja-debug-python",
GH-34004: [C++] Add a benchmarks-maximal CMake preset (#34005) ### Rationale for this change Add a benchmarks-maximal CMake preset to benchmark all components or to test the compilation of all benchmark files. ### What changes are included in this PR? Along with the new preset, also 1. Fixed indentation of the json file. 2. The "maximal" presets actually include CUDA, so I fixed their display names. ### Are these changes tested? The preset works locally on my machine. ### Are there any user-facing changes? No. * Closes: #34004 Authored-by: Jin Shang <shangjin1997@gmail.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2023-02-03 04:03:59 +08:00
"inherits": [
GH-45209: [C++][CMake] Fix the issue that allocator not disabled for sanitizer cmake presets (#45210) ### Rationale for this change I gave the reason in #45209 ### What changes are included in this PR? Adjust the inheritance list order and make a lot of simplification/regrouping/reordering for existing presets the way I see fit. Also introduce a soft rule to order inheritance list: `sanitizer` comes before `features` comes before `base`. Though we can't really mandate such a rule (thus it's "soft") or make it clear in comments (our current cmake dosn't support comment in json), we hope people will notice this pattern and follow it when editing this file. ### Are these changes tested? Manually tested. ### Are there any user-facing changes? None. * GitHub Issue: #45209 Lead-authored-by: Rossi Sun <zanmato1984@gmail.com> Co-authored-by: Sutou Kouhei <kou@cozmixng.org> Signed-off-by: Rossi Sun <zanmato1984@gmail.com>
2025-01-10 23:14:20 +08:00
"features-python",
"base-debug"
GH-34004: [C++] Add a benchmarks-maximal CMake preset (#34005) ### Rationale for this change Add a benchmarks-maximal CMake preset to benchmark all components or to test the compilation of all benchmark files. ### What changes are included in this PR? Along with the new preset, also 1. Fixed indentation of the json file. 2. The "maximal" presets actually include CUDA, so I fixed their display names. ### Are these changes tested? The preset works locally on my machine. ### Are there any user-facing changes? No. * Closes: #34004 Authored-by: Jin Shang <shangjin1997@gmail.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2023-02-03 04:03:59 +08:00
],
ARROW-17868: [C++][Python] Restore the ARROW_PYTHON CMake option (#14273) Restore it but it's marked as a deprecated option. Because the Python component in Apache Arrow C++ was moved to PyArrow by ARROW-16340. It' removed in a feature release. Users should use CMake presets instead of ARROW_PYTHON but CMake presets requires CMake 3.19 or later. Lead-authored-by: Sutou Kouhei <kou@clear-code.com> Co-authored-by: Sutou Kouhei <kou@cozmixng.org> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2022-10-01 20:46:17 +09:00
"displayName": "Debug build for PyArrow with common features (for backward compatibility)",
"cacheVariables": {}
},
{
"name": "ninja-debug-python-maximal",
GH-34004: [C++] Add a benchmarks-maximal CMake preset (#34005) ### Rationale for this change Add a benchmarks-maximal CMake preset to benchmark all components or to test the compilation of all benchmark files. ### What changes are included in this PR? Along with the new preset, also 1. Fixed indentation of the json file. 2. The "maximal" presets actually include CUDA, so I fixed their display names. ### Are these changes tested? The preset works locally on my machine. ### Are there any user-facing changes? No. * Closes: #34004 Authored-by: Jin Shang <shangjin1997@gmail.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2023-02-03 04:03:59 +08:00
"inherits": [
GH-45209: [C++][CMake] Fix the issue that allocator not disabled for sanitizer cmake presets (#45210) ### Rationale for this change I gave the reason in #45209 ### What changes are included in this PR? Adjust the inheritance list order and make a lot of simplification/regrouping/reordering for existing presets the way I see fit. Also introduce a soft rule to order inheritance list: `sanitizer` comes before `features` comes before `base`. Though we can't really mandate such a rule (thus it's "soft") or make it clear in comments (our current cmake dosn't support comment in json), we hope people will notice this pattern and follow it when editing this file. ### Are these changes tested? Manually tested. ### Are there any user-facing changes? None. * GitHub Issue: #45209 Lead-authored-by: Rossi Sun <zanmato1984@gmail.com> Co-authored-by: Sutou Kouhei <kou@cozmixng.org> Signed-off-by: Rossi Sun <zanmato1984@gmail.com>
2025-01-10 23:14:20 +08:00
"features-python-maximal",
"base-debug"
GH-34004: [C++] Add a benchmarks-maximal CMake preset (#34005) ### Rationale for this change Add a benchmarks-maximal CMake preset to benchmark all components or to test the compilation of all benchmark files. ### What changes are included in this PR? Along with the new preset, also 1. Fixed indentation of the json file. 2. The "maximal" presets actually include CUDA, so I fixed their display names. ### Are these changes tested? The preset works locally on my machine. ### Are there any user-facing changes? No. * Closes: #34004 Authored-by: Jin Shang <shangjin1997@gmail.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2023-02-03 04:03:59 +08:00
],
"displayName": "Debug build for PyArrow with everything enabled",
ARROW-17868: [C++][Python] Restore the ARROW_PYTHON CMake option (#14273) Restore it but it's marked as a deprecated option. Because the Python component in Apache Arrow C++ was moved to PyArrow by ARROW-16340. It' removed in a feature release. Users should use CMake presets instead of ARROW_PYTHON but CMake presets requires CMake 3.19 or later. Lead-authored-by: Sutou Kouhei <kou@clear-code.com> Co-authored-by: Sutou Kouhei <kou@cozmixng.org> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2022-10-01 20:46:17 +09:00
"cacheVariables": {}
},
ARROW-14714: [C++][Doc] Rework CMake presets and add documentation Try to define CMake presets that correspond to common use cases. Switch to version 3 of the format so that `binaryDir` isn't mandatory anymore. Also add display names so that the command line can be more informative. Document the use of CMake presets. Summary of available presets: ``` $ cmake --list-presets Available configure presets: "ninja-debug-minimal" - Debug build without anything enabled "ninja-debug-basic" - Debug build with tests and reduced dependencies "ninja-debug" - Debug build with tests and more optional components "ninja-debug-cuda" - Debug build with tests and CUDA integration "ninja-debug-filesystems" - Debug build with tests and filesystems "ninja-debug-flight" - Debug build with tests and Flight "ninja-debug-gandiva" - Debug build with tests and Gandiva "ninja-debug-python" - Debug build with tests and Python support "ninja-debug-maximal" - Debug build with everything enabled (except benchmarks and CUDA) "ninja-release-minimal" - Release build without anything enabled "ninja-release-basic" - Release build with reduced dependencies "ninja-release" - Release build with more optional components "ninja-release-cuda" - Release build with CUDA integration "ninja-release-flight" - Release build with Flight "ninja-release-gandiva" - Release build with Gandiva "ninja-release-python" - Release build with Python support "ninja-release-maximal" - Release build with everything enabled (except benchmarks and CUDA) "ninja-benchmarks-basic" - Benchmarking build with reduced dependencies "ninja-benchmarks" - Benchmarking build with more optional components ``` Closes #11778 from pitrou/ARROW-14714-cmake-presets Authored-by: Antoine Pitrou <antoine@python.org> Signed-off-by: Krisztián Szűcs <szucs.krisztian@gmail.com>
2021-12-01 20:33:23 +01:00
{
"name": "ninja-debug-maximal",
GH-34004: [C++] Add a benchmarks-maximal CMake preset (#34005) ### Rationale for this change Add a benchmarks-maximal CMake preset to benchmark all components or to test the compilation of all benchmark files. ### What changes are included in this PR? Along with the new preset, also 1. Fixed indentation of the json file. 2. The "maximal" presets actually include CUDA, so I fixed their display names. ### Are these changes tested? The preset works locally on my machine. ### Are there any user-facing changes? No. * Closes: #34004 Authored-by: Jin Shang <shangjin1997@gmail.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2023-02-03 04:03:59 +08:00
"inherits": [
GH-45209: [C++][CMake] Fix the issue that allocator not disabled for sanitizer cmake presets (#45210) ### Rationale for this change I gave the reason in #45209 ### What changes are included in this PR? Adjust the inheritance list order and make a lot of simplification/regrouping/reordering for existing presets the way I see fit. Also introduce a soft rule to order inheritance list: `sanitizer` comes before `features` comes before `base`. Though we can't really mandate such a rule (thus it's "soft") or make it clear in comments (our current cmake dosn't support comment in json), we hope people will notice this pattern and follow it when editing this file. ### Are these changes tested? Manually tested. ### Are there any user-facing changes? None. * GitHub Issue: #45209 Lead-authored-by: Rossi Sun <zanmato1984@gmail.com> Co-authored-by: Sutou Kouhei <kou@cozmixng.org> Signed-off-by: Rossi Sun <zanmato1984@gmail.com>
2025-01-10 23:14:20 +08:00
"features-maximal",
"base-debug"
GH-34004: [C++] Add a benchmarks-maximal CMake preset (#34005) ### Rationale for this change Add a benchmarks-maximal CMake preset to benchmark all components or to test the compilation of all benchmark files. ### What changes are included in this PR? Along with the new preset, also 1. Fixed indentation of the json file. 2. The "maximal" presets actually include CUDA, so I fixed their display names. ### Are these changes tested? The preset works locally on my machine. ### Are there any user-facing changes? No. * Closes: #34004 Authored-by: Jin Shang <shangjin1997@gmail.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2023-02-03 04:03:59 +08:00
],
"displayName": "Debug build with everything enabled (except benchmarks)",
ARROW-14714: [C++][Doc] Rework CMake presets and add documentation Try to define CMake presets that correspond to common use cases. Switch to version 3 of the format so that `binaryDir` isn't mandatory anymore. Also add display names so that the command line can be more informative. Document the use of CMake presets. Summary of available presets: ``` $ cmake --list-presets Available configure presets: "ninja-debug-minimal" - Debug build without anything enabled "ninja-debug-basic" - Debug build with tests and reduced dependencies "ninja-debug" - Debug build with tests and more optional components "ninja-debug-cuda" - Debug build with tests and CUDA integration "ninja-debug-filesystems" - Debug build with tests and filesystems "ninja-debug-flight" - Debug build with tests and Flight "ninja-debug-gandiva" - Debug build with tests and Gandiva "ninja-debug-python" - Debug build with tests and Python support "ninja-debug-maximal" - Debug build with everything enabled (except benchmarks and CUDA) "ninja-release-minimal" - Release build without anything enabled "ninja-release-basic" - Release build with reduced dependencies "ninja-release" - Release build with more optional components "ninja-release-cuda" - Release build with CUDA integration "ninja-release-flight" - Release build with Flight "ninja-release-gandiva" - Release build with Gandiva "ninja-release-python" - Release build with Python support "ninja-release-maximal" - Release build with everything enabled (except benchmarks and CUDA) "ninja-benchmarks-basic" - Benchmarking build with reduced dependencies "ninja-benchmarks" - Benchmarking build with more optional components ``` Closes #11778 from pitrou/ARROW-14714-cmake-presets Authored-by: Antoine Pitrou <antoine@python.org> Signed-off-by: Krisztián Szűcs <szucs.krisztian@gmail.com>
2021-12-01 20:33:23 +01:00
"cacheVariables": {}
},
GH-45209: [C++][CMake] Fix the issue that allocator not disabled for sanitizer cmake presets (#45210) ### Rationale for this change I gave the reason in #45209 ### What changes are included in this PR? Adjust the inheritance list order and make a lot of simplification/regrouping/reordering for existing presets the way I see fit. Also introduce a soft rule to order inheritance list: `sanitizer` comes before `features` comes before `base`. Though we can't really mandate such a rule (thus it's "soft") or make it clear in comments (our current cmake dosn't support comment in json), we hope people will notice this pattern and follow it when editing this file. ### Are these changes tested? Manually tested. ### Are there any user-facing changes? None. * GitHub Issue: #45209 Lead-authored-by: Rossi Sun <zanmato1984@gmail.com> Co-authored-by: Sutou Kouhei <kou@cozmixng.org> Signed-off-by: Rossi Sun <zanmato1984@gmail.com>
2025-01-10 23:14:20 +08:00
{
"name": "ninja-debug-emscripten",
"inherits": [
"features-emscripten",
"base-debug"
],
"displayName": "Debug build which builds an Emscripten library",
"cacheVariables": {}
},
{
"name": "ninja-debug-valgrind-minimal",
"inherits": [
"features-valgrind",
"ninja-debug-minimal"
],
"displayName": "Debug build for Valgrind without anything enabled",
"cacheVariables": {}
},
GH-42109: [C++][CMake] Add preset for Valgrind (#42110) ### Rationale for this change If we want to use Valgrind for our tests, we need to specify at least the following CMake options: * `ARROW_RUNTIME_SIMD_LEVEL=AVX2` * `ARROW_TEST_MEMCHECK=ON` If we have a CMake preset for Valgrind, we don't need to remember them. ### What changes are included in this PR? Add `features-valgrind` and `ninja-debug-valgrind` preset. `features-valgrind` is a hidden preset. ### Are these changes tested? Yes. I used this to reproduce #42107 on local. ### Are there any user-facing changes? No. * GitHub Issue: #42109 Authored-by: Sutou Kouhei <kou@clear-code.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2024-06-13 18:04:31 +09:00
{
"name": "ninja-debug-valgrind-basic",
"inherits": [
GH-45209: [C++][CMake] Fix the issue that allocator not disabled for sanitizer cmake presets (#45210) ### Rationale for this change I gave the reason in #45209 ### What changes are included in this PR? Adjust the inheritance list order and make a lot of simplification/regrouping/reordering for existing presets the way I see fit. Also introduce a soft rule to order inheritance list: `sanitizer` comes before `features` comes before `base`. Though we can't really mandate such a rule (thus it's "soft") or make it clear in comments (our current cmake dosn't support comment in json), we hope people will notice this pattern and follow it when editing this file. ### Are these changes tested? Manually tested. ### Are there any user-facing changes? None. * GitHub Issue: #45209 Lead-authored-by: Rossi Sun <zanmato1984@gmail.com> Co-authored-by: Sutou Kouhei <kou@cozmixng.org> Signed-off-by: Rossi Sun <zanmato1984@gmail.com>
2025-01-10 23:14:20 +08:00
"features-valgrind",
"ninja-debug-basic"
GH-42109: [C++][CMake] Add preset for Valgrind (#42110) ### Rationale for this change If we want to use Valgrind for our tests, we need to specify at least the following CMake options: * `ARROW_RUNTIME_SIMD_LEVEL=AVX2` * `ARROW_TEST_MEMCHECK=ON` If we have a CMake preset for Valgrind, we don't need to remember them. ### What changes are included in this PR? Add `features-valgrind` and `ninja-debug-valgrind` preset. `features-valgrind` is a hidden preset. ### Are these changes tested? Yes. I used this to reproduce #42107 on local. ### Are there any user-facing changes? No. * GitHub Issue: #42109 Authored-by: Sutou Kouhei <kou@clear-code.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2024-06-13 18:04:31 +09:00
],
GH-45209: [C++][CMake] Fix the issue that allocator not disabled for sanitizer cmake presets (#45210) ### Rationale for this change I gave the reason in #45209 ### What changes are included in this PR? Adjust the inheritance list order and make a lot of simplification/regrouping/reordering for existing presets the way I see fit. Also introduce a soft rule to order inheritance list: `sanitizer` comes before `features` comes before `base`. Though we can't really mandate such a rule (thus it's "soft") or make it clear in comments (our current cmake dosn't support comment in json), we hope people will notice this pattern and follow it when editing this file. ### Are these changes tested? Manually tested. ### Are there any user-facing changes? None. * GitHub Issue: #45209 Lead-authored-by: Rossi Sun <zanmato1984@gmail.com> Co-authored-by: Sutou Kouhei <kou@cozmixng.org> Signed-off-by: Rossi Sun <zanmato1984@gmail.com>
2025-01-10 23:14:20 +08:00
"displayName": "Debug build for Valgrind with tests and reduced dependencies",
GH-42109: [C++][CMake] Add preset for Valgrind (#42110) ### Rationale for this change If we want to use Valgrind for our tests, we need to specify at least the following CMake options: * `ARROW_RUNTIME_SIMD_LEVEL=AVX2` * `ARROW_TEST_MEMCHECK=ON` If we have a CMake preset for Valgrind, we don't need to remember them. ### What changes are included in this PR? Add `features-valgrind` and `ninja-debug-valgrind` preset. `features-valgrind` is a hidden preset. ### Are these changes tested? Yes. I used this to reproduce #42107 on local. ### Are there any user-facing changes? No. * GitHub Issue: #42109 Authored-by: Sutou Kouhei <kou@clear-code.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2024-06-13 18:04:31 +09:00
"cacheVariables": {}
},
{
"name": "ninja-debug-valgrind",
"inherits": [
GH-45209: [C++][CMake] Fix the issue that allocator not disabled for sanitizer cmake presets (#45210) ### Rationale for this change I gave the reason in #45209 ### What changes are included in this PR? Adjust the inheritance list order and make a lot of simplification/regrouping/reordering for existing presets the way I see fit. Also introduce a soft rule to order inheritance list: `sanitizer` comes before `features` comes before `base`. Though we can't really mandate such a rule (thus it's "soft") or make it clear in comments (our current cmake dosn't support comment in json), we hope people will notice this pattern and follow it when editing this file. ### Are these changes tested? Manually tested. ### Are there any user-facing changes? None. * GitHub Issue: #45209 Lead-authored-by: Rossi Sun <zanmato1984@gmail.com> Co-authored-by: Sutou Kouhei <kou@cozmixng.org> Signed-off-by: Rossi Sun <zanmato1984@gmail.com>
2025-01-10 23:14:20 +08:00
"features-valgrind",
"ninja-debug"
GH-42109: [C++][CMake] Add preset for Valgrind (#42110) ### Rationale for this change If we want to use Valgrind for our tests, we need to specify at least the following CMake options: * `ARROW_RUNTIME_SIMD_LEVEL=AVX2` * `ARROW_TEST_MEMCHECK=ON` If we have a CMake preset for Valgrind, we don't need to remember them. ### What changes are included in this PR? Add `features-valgrind` and `ninja-debug-valgrind` preset. `features-valgrind` is a hidden preset. ### Are these changes tested? Yes. I used this to reproduce #42107 on local. ### Are there any user-facing changes? No. * GitHub Issue: #42109 Authored-by: Sutou Kouhei <kou@clear-code.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2024-06-13 18:04:31 +09:00
],
GH-45209: [C++][CMake] Fix the issue that allocator not disabled for sanitizer cmake presets (#45210) ### Rationale for this change I gave the reason in #45209 ### What changes are included in this PR? Adjust the inheritance list order and make a lot of simplification/regrouping/reordering for existing presets the way I see fit. Also introduce a soft rule to order inheritance list: `sanitizer` comes before `features` comes before `base`. Though we can't really mandate such a rule (thus it's "soft") or make it clear in comments (our current cmake dosn't support comment in json), we hope people will notice this pattern and follow it when editing this file. ### Are these changes tested? Manually tested. ### Are there any user-facing changes? None. * GitHub Issue: #45209 Lead-authored-by: Rossi Sun <zanmato1984@gmail.com> Co-authored-by: Sutou Kouhei <kou@cozmixng.org> Signed-off-by: Rossi Sun <zanmato1984@gmail.com>
2025-01-10 23:14:20 +08:00
"displayName": "Debug build for Valgrind with tests and more optional components",
GH-42109: [C++][CMake] Add preset for Valgrind (#42110) ### Rationale for this change If we want to use Valgrind for our tests, we need to specify at least the following CMake options: * `ARROW_RUNTIME_SIMD_LEVEL=AVX2` * `ARROW_TEST_MEMCHECK=ON` If we have a CMake preset for Valgrind, we don't need to remember them. ### What changes are included in this PR? Add `features-valgrind` and `ninja-debug-valgrind` preset. `features-valgrind` is a hidden preset. ### Are these changes tested? Yes. I used this to reproduce #42107 on local. ### Are there any user-facing changes? No. * GitHub Issue: #42109 Authored-by: Sutou Kouhei <kou@clear-code.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2024-06-13 18:04:31 +09:00
"cacheVariables": {}
},
{
GH-45209: [C++][CMake] Fix the issue that allocator not disabled for sanitizer cmake presets (#45210) ### Rationale for this change I gave the reason in #45209 ### What changes are included in this PR? Adjust the inheritance list order and make a lot of simplification/regrouping/reordering for existing presets the way I see fit. Also introduce a soft rule to order inheritance list: `sanitizer` comes before `features` comes before `base`. Though we can't really mandate such a rule (thus it's "soft") or make it clear in comments (our current cmake dosn't support comment in json), we hope people will notice this pattern and follow it when editing this file. ### Are these changes tested? Manually tested. ### Are there any user-facing changes? None. * GitHub Issue: #45209 Lead-authored-by: Rossi Sun <zanmato1984@gmail.com> Co-authored-by: Sutou Kouhei <kou@cozmixng.org> Signed-off-by: Rossi Sun <zanmato1984@gmail.com>
2025-01-10 23:14:20 +08:00
"name": "ninja-debug-valgrind-maximal",
GH-42109: [C++][CMake] Add preset for Valgrind (#42110) ### Rationale for this change If we want to use Valgrind for our tests, we need to specify at least the following CMake options: * `ARROW_RUNTIME_SIMD_LEVEL=AVX2` * `ARROW_TEST_MEMCHECK=ON` If we have a CMake preset for Valgrind, we don't need to remember them. ### What changes are included in this PR? Add `features-valgrind` and `ninja-debug-valgrind` preset. `features-valgrind` is a hidden preset. ### Are these changes tested? Yes. I used this to reproduce #42107 on local. ### Are there any user-facing changes? No. * GitHub Issue: #42109 Authored-by: Sutou Kouhei <kou@clear-code.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2024-06-13 18:04:31 +09:00
"inherits": [
GH-45209: [C++][CMake] Fix the issue that allocator not disabled for sanitizer cmake presets (#45210) ### Rationale for this change I gave the reason in #45209 ### What changes are included in this PR? Adjust the inheritance list order and make a lot of simplification/regrouping/reordering for existing presets the way I see fit. Also introduce a soft rule to order inheritance list: `sanitizer` comes before `features` comes before `base`. Though we can't really mandate such a rule (thus it's "soft") or make it clear in comments (our current cmake dosn't support comment in json), we hope people will notice this pattern and follow it when editing this file. ### Are these changes tested? Manually tested. ### Are there any user-facing changes? None. * GitHub Issue: #45209 Lead-authored-by: Rossi Sun <zanmato1984@gmail.com> Co-authored-by: Sutou Kouhei <kou@cozmixng.org> Signed-off-by: Rossi Sun <zanmato1984@gmail.com>
2025-01-10 23:14:20 +08:00
"features-valgrind",
"ninja-debug-maximal"
GH-42109: [C++][CMake] Add preset for Valgrind (#42110) ### Rationale for this change If we want to use Valgrind for our tests, we need to specify at least the following CMake options: * `ARROW_RUNTIME_SIMD_LEVEL=AVX2` * `ARROW_TEST_MEMCHECK=ON` If we have a CMake preset for Valgrind, we don't need to remember them. ### What changes are included in this PR? Add `features-valgrind` and `ninja-debug-valgrind` preset. `features-valgrind` is a hidden preset. ### Are these changes tested? Yes. I used this to reproduce #42107 on local. ### Are there any user-facing changes? No. * GitHub Issue: #42109 Authored-by: Sutou Kouhei <kou@clear-code.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2024-06-13 18:04:31 +09:00
],
GH-45209: [C++][CMake] Fix the issue that allocator not disabled for sanitizer cmake presets (#45210) ### Rationale for this change I gave the reason in #45209 ### What changes are included in this PR? Adjust the inheritance list order and make a lot of simplification/regrouping/reordering for existing presets the way I see fit. Also introduce a soft rule to order inheritance list: `sanitizer` comes before `features` comes before `base`. Though we can't really mandate such a rule (thus it's "soft") or make it clear in comments (our current cmake dosn't support comment in json), we hope people will notice this pattern and follow it when editing this file. ### Are these changes tested? Manually tested. ### Are there any user-facing changes? None. * GitHub Issue: #45209 Lead-authored-by: Rossi Sun <zanmato1984@gmail.com> Co-authored-by: Sutou Kouhei <kou@cozmixng.org> Signed-off-by: Rossi Sun <zanmato1984@gmail.com>
2025-01-10 23:14:20 +08:00
"displayName": "Debug build for Valgrind with tests and everything enabled",
GH-42109: [C++][CMake] Add preset for Valgrind (#42110) ### Rationale for this change If we want to use Valgrind for our tests, we need to specify at least the following CMake options: * `ARROW_RUNTIME_SIMD_LEVEL=AVX2` * `ARROW_TEST_MEMCHECK=ON` If we have a CMake preset for Valgrind, we don't need to remember them. ### What changes are included in this PR? Add `features-valgrind` and `ninja-debug-valgrind` preset. `features-valgrind` is a hidden preset. ### Are these changes tested? Yes. I used this to reproduce #42107 on local. ### Are there any user-facing changes? No. * GitHub Issue: #42109 Authored-by: Sutou Kouhei <kou@clear-code.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2024-06-13 18:04:31 +09:00
"cacheVariables": {}
},
{
GH-45209: [C++][CMake] Fix the issue that allocator not disabled for sanitizer cmake presets (#45210) ### Rationale for this change I gave the reason in #45209 ### What changes are included in this PR? Adjust the inheritance list order and make a lot of simplification/regrouping/reordering for existing presets the way I see fit. Also introduce a soft rule to order inheritance list: `sanitizer` comes before `features` comes before `base`. Though we can't really mandate such a rule (thus it's "soft") or make it clear in comments (our current cmake dosn't support comment in json), we hope people will notice this pattern and follow it when editing this file. ### Are these changes tested? Manually tested. ### Are there any user-facing changes? None. * GitHub Issue: #45209 Lead-authored-by: Rossi Sun <zanmato1984@gmail.com> Co-authored-by: Sutou Kouhei <kou@cozmixng.org> Signed-off-by: Rossi Sun <zanmato1984@gmail.com>
2025-01-10 23:14:20 +08:00
"name": "ninja-debug-asan",
GH-42109: [C++][CMake] Add preset for Valgrind (#42110) ### Rationale for this change If we want to use Valgrind for our tests, we need to specify at least the following CMake options: * `ARROW_RUNTIME_SIMD_LEVEL=AVX2` * `ARROW_TEST_MEMCHECK=ON` If we have a CMake preset for Valgrind, we don't need to remember them. ### What changes are included in this PR? Add `features-valgrind` and `ninja-debug-valgrind` preset. `features-valgrind` is a hidden preset. ### Are these changes tested? Yes. I used this to reproduce #42107 on local. ### Are there any user-facing changes? No. * GitHub Issue: #42109 Authored-by: Sutou Kouhei <kou@clear-code.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2024-06-13 18:04:31 +09:00
"inherits": [
GH-45209: [C++][CMake] Fix the issue that allocator not disabled for sanitizer cmake presets (#45210) ### Rationale for this change I gave the reason in #45209 ### What changes are included in this PR? Adjust the inheritance list order and make a lot of simplification/regrouping/reordering for existing presets the way I see fit. Also introduce a soft rule to order inheritance list: `sanitizer` comes before `features` comes before `base`. Though we can't really mandate such a rule (thus it's "soft") or make it clear in comments (our current cmake dosn't support comment in json), we hope people will notice this pattern and follow it when editing this file. ### Are these changes tested? Manually tested. ### Are there any user-facing changes? None. * GitHub Issue: #45209 Lead-authored-by: Rossi Sun <zanmato1984@gmail.com> Co-authored-by: Sutou Kouhei <kou@cozmixng.org> Signed-off-by: Rossi Sun <zanmato1984@gmail.com>
2025-01-10 23:14:20 +08:00
"sanitizer-asan",
"ninja-debug"
GH-42109: [C++][CMake] Add preset for Valgrind (#42110) ### Rationale for this change If we want to use Valgrind for our tests, we need to specify at least the following CMake options: * `ARROW_RUNTIME_SIMD_LEVEL=AVX2` * `ARROW_TEST_MEMCHECK=ON` If we have a CMake preset for Valgrind, we don't need to remember them. ### What changes are included in this PR? Add `features-valgrind` and `ninja-debug-valgrind` preset. `features-valgrind` is a hidden preset. ### Are these changes tested? Yes. I used this to reproduce #42107 on local. ### Are there any user-facing changes? No. * GitHub Issue: #42109 Authored-by: Sutou Kouhei <kou@clear-code.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2024-06-13 18:04:31 +09:00
],
GH-45209: [C++][CMake] Fix the issue that allocator not disabled for sanitizer cmake presets (#45210) ### Rationale for this change I gave the reason in #45209 ### What changes are included in this PR? Adjust the inheritance list order and make a lot of simplification/regrouping/reordering for existing presets the way I see fit. Also introduce a soft rule to order inheritance list: `sanitizer` comes before `features` comes before `base`. Though we can't really mandate such a rule (thus it's "soft") or make it clear in comments (our current cmake dosn't support comment in json), we hope people will notice this pattern and follow it when editing this file. ### Are these changes tested? Manually tested. ### Are there any user-facing changes? None. * GitHub Issue: #45209 Lead-authored-by: Rossi Sun <zanmato1984@gmail.com> Co-authored-by: Sutou Kouhei <kou@cozmixng.org> Signed-off-by: Rossi Sun <zanmato1984@gmail.com>
2025-01-10 23:14:20 +08:00
"displayName": "Debug build for ASAN with tests and more optional components",
GH-42109: [C++][CMake] Add preset for Valgrind (#42110) ### Rationale for this change If we want to use Valgrind for our tests, we need to specify at least the following CMake options: * `ARROW_RUNTIME_SIMD_LEVEL=AVX2` * `ARROW_TEST_MEMCHECK=ON` If we have a CMake preset for Valgrind, we don't need to remember them. ### What changes are included in this PR? Add `features-valgrind` and `ninja-debug-valgrind` preset. `features-valgrind` is a hidden preset. ### Are these changes tested? Yes. I used this to reproduce #42107 on local. ### Are there any user-facing changes? No. * GitHub Issue: #42109 Authored-by: Sutou Kouhei <kou@clear-code.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2024-06-13 18:04:31 +09:00
"cacheVariables": {}
},
ARROW-14714: [C++][Doc] Rework CMake presets and add documentation Try to define CMake presets that correspond to common use cases. Switch to version 3 of the format so that `binaryDir` isn't mandatory anymore. Also add display names so that the command line can be more informative. Document the use of CMake presets. Summary of available presets: ``` $ cmake --list-presets Available configure presets: "ninja-debug-minimal" - Debug build without anything enabled "ninja-debug-basic" - Debug build with tests and reduced dependencies "ninja-debug" - Debug build with tests and more optional components "ninja-debug-cuda" - Debug build with tests and CUDA integration "ninja-debug-filesystems" - Debug build with tests and filesystems "ninja-debug-flight" - Debug build with tests and Flight "ninja-debug-gandiva" - Debug build with tests and Gandiva "ninja-debug-python" - Debug build with tests and Python support "ninja-debug-maximal" - Debug build with everything enabled (except benchmarks and CUDA) "ninja-release-minimal" - Release build without anything enabled "ninja-release-basic" - Release build with reduced dependencies "ninja-release" - Release build with more optional components "ninja-release-cuda" - Release build with CUDA integration "ninja-release-flight" - Release build with Flight "ninja-release-gandiva" - Release build with Gandiva "ninja-release-python" - Release build with Python support "ninja-release-maximal" - Release build with everything enabled (except benchmarks and CUDA) "ninja-benchmarks-basic" - Benchmarking build with reduced dependencies "ninja-benchmarks" - Benchmarking build with more optional components ``` Closes #11778 from pitrou/ARROW-14714-cmake-presets Authored-by: Antoine Pitrou <antoine@python.org> Signed-off-by: Krisztián Szűcs <szucs.krisztian@gmail.com>
2021-12-01 20:33:23 +01:00
{
GH-45209: [C++][CMake] Fix the issue that allocator not disabled for sanitizer cmake presets (#45210) ### Rationale for this change I gave the reason in #45209 ### What changes are included in this PR? Adjust the inheritance list order and make a lot of simplification/regrouping/reordering for existing presets the way I see fit. Also introduce a soft rule to order inheritance list: `sanitizer` comes before `features` comes before `base`. Though we can't really mandate such a rule (thus it's "soft") or make it clear in comments (our current cmake dosn't support comment in json), we hope people will notice this pattern and follow it when editing this file. ### Are these changes tested? Manually tested. ### Are there any user-facing changes? None. * GitHub Issue: #45209 Lead-authored-by: Rossi Sun <zanmato1984@gmail.com> Co-authored-by: Sutou Kouhei <kou@cozmixng.org> Signed-off-by: Rossi Sun <zanmato1984@gmail.com>
2025-01-10 23:14:20 +08:00
"name": "ninja-debug-tsan",
GH-34004: [C++] Add a benchmarks-maximal CMake preset (#34005) ### Rationale for this change Add a benchmarks-maximal CMake preset to benchmark all components or to test the compilation of all benchmark files. ### What changes are included in this PR? Along with the new preset, also 1. Fixed indentation of the json file. 2. The "maximal" presets actually include CUDA, so I fixed their display names. ### Are these changes tested? The preset works locally on my machine. ### Are there any user-facing changes? No. * Closes: #34004 Authored-by: Jin Shang <shangjin1997@gmail.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2023-02-03 04:03:59 +08:00
"inherits": [
GH-45209: [C++][CMake] Fix the issue that allocator not disabled for sanitizer cmake presets (#45210) ### Rationale for this change I gave the reason in #45209 ### What changes are included in this PR? Adjust the inheritance list order and make a lot of simplification/regrouping/reordering for existing presets the way I see fit. Also introduce a soft rule to order inheritance list: `sanitizer` comes before `features` comes before `base`. Though we can't really mandate such a rule (thus it's "soft") or make it clear in comments (our current cmake dosn't support comment in json), we hope people will notice this pattern and follow it when editing this file. ### Are these changes tested? Manually tested. ### Are there any user-facing changes? None. * GitHub Issue: #45209 Lead-authored-by: Rossi Sun <zanmato1984@gmail.com> Co-authored-by: Sutou Kouhei <kou@cozmixng.org> Signed-off-by: Rossi Sun <zanmato1984@gmail.com>
2025-01-10 23:14:20 +08:00
"sanitizer-tsan",
"ninja-debug"
GH-34004: [C++] Add a benchmarks-maximal CMake preset (#34005) ### Rationale for this change Add a benchmarks-maximal CMake preset to benchmark all components or to test the compilation of all benchmark files. ### What changes are included in this PR? Along with the new preset, also 1. Fixed indentation of the json file. 2. The "maximal" presets actually include CUDA, so I fixed their display names. ### Are these changes tested? The preset works locally on my machine. ### Are there any user-facing changes? No. * Closes: #34004 Authored-by: Jin Shang <shangjin1997@gmail.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2023-02-03 04:03:59 +08:00
],
GH-45209: [C++][CMake] Fix the issue that allocator not disabled for sanitizer cmake presets (#45210) ### Rationale for this change I gave the reason in #45209 ### What changes are included in this PR? Adjust the inheritance list order and make a lot of simplification/regrouping/reordering for existing presets the way I see fit. Also introduce a soft rule to order inheritance list: `sanitizer` comes before `features` comes before `base`. Though we can't really mandate such a rule (thus it's "soft") or make it clear in comments (our current cmake dosn't support comment in json), we hope people will notice this pattern and follow it when editing this file. ### Are these changes tested? Manually tested. ### Are there any user-facing changes? None. * GitHub Issue: #45209 Lead-authored-by: Rossi Sun <zanmato1984@gmail.com> Co-authored-by: Sutou Kouhei <kou@cozmixng.org> Signed-off-by: Rossi Sun <zanmato1984@gmail.com>
2025-01-10 23:14:20 +08:00
"displayName": "Debug build for TSAN with tests and more optional components",
ARROW-14714: [C++][Doc] Rework CMake presets and add documentation Try to define CMake presets that correspond to common use cases. Switch to version 3 of the format so that `binaryDir` isn't mandatory anymore. Also add display names so that the command line can be more informative. Document the use of CMake presets. Summary of available presets: ``` $ cmake --list-presets Available configure presets: "ninja-debug-minimal" - Debug build without anything enabled "ninja-debug-basic" - Debug build with tests and reduced dependencies "ninja-debug" - Debug build with tests and more optional components "ninja-debug-cuda" - Debug build with tests and CUDA integration "ninja-debug-filesystems" - Debug build with tests and filesystems "ninja-debug-flight" - Debug build with tests and Flight "ninja-debug-gandiva" - Debug build with tests and Gandiva "ninja-debug-python" - Debug build with tests and Python support "ninja-debug-maximal" - Debug build with everything enabled (except benchmarks and CUDA) "ninja-release-minimal" - Release build without anything enabled "ninja-release-basic" - Release build with reduced dependencies "ninja-release" - Release build with more optional components "ninja-release-cuda" - Release build with CUDA integration "ninja-release-flight" - Release build with Flight "ninja-release-gandiva" - Release build with Gandiva "ninja-release-python" - Release build with Python support "ninja-release-maximal" - Release build with everything enabled (except benchmarks and CUDA) "ninja-benchmarks-basic" - Benchmarking build with reduced dependencies "ninja-benchmarks" - Benchmarking build with more optional components ``` Closes #11778 from pitrou/ARROW-14714-cmake-presets Authored-by: Antoine Pitrou <antoine@python.org> Signed-off-by: Krisztián Szűcs <szucs.krisztian@gmail.com>
2021-12-01 20:33:23 +01:00
"cacheVariables": {}
},
{
GH-45209: [C++][CMake] Fix the issue that allocator not disabled for sanitizer cmake presets (#45210) ### Rationale for this change I gave the reason in #45209 ### What changes are included in this PR? Adjust the inheritance list order and make a lot of simplification/regrouping/reordering for existing presets the way I see fit. Also introduce a soft rule to order inheritance list: `sanitizer` comes before `features` comes before `base`. Though we can't really mandate such a rule (thus it's "soft") or make it clear in comments (our current cmake dosn't support comment in json), we hope people will notice this pattern and follow it when editing this file. ### Are these changes tested? Manually tested. ### Are there any user-facing changes? None. * GitHub Issue: #45209 Lead-authored-by: Rossi Sun <zanmato1984@gmail.com> Co-authored-by: Sutou Kouhei <kou@cozmixng.org> Signed-off-by: Rossi Sun <zanmato1984@gmail.com>
2025-01-10 23:14:20 +08:00
"name": "ninja-debug-ubsan",
GH-34004: [C++] Add a benchmarks-maximal CMake preset (#34005) ### Rationale for this change Add a benchmarks-maximal CMake preset to benchmark all components or to test the compilation of all benchmark files. ### What changes are included in this PR? Along with the new preset, also 1. Fixed indentation of the json file. 2. The "maximal" presets actually include CUDA, so I fixed their display names. ### Are these changes tested? The preset works locally on my machine. ### Are there any user-facing changes? No. * Closes: #34004 Authored-by: Jin Shang <shangjin1997@gmail.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2023-02-03 04:03:59 +08:00
"inherits": [
GH-45209: [C++][CMake] Fix the issue that allocator not disabled for sanitizer cmake presets (#45210) ### Rationale for this change I gave the reason in #45209 ### What changes are included in this PR? Adjust the inheritance list order and make a lot of simplification/regrouping/reordering for existing presets the way I see fit. Also introduce a soft rule to order inheritance list: `sanitizer` comes before `features` comes before `base`. Though we can't really mandate such a rule (thus it's "soft") or make it clear in comments (our current cmake dosn't support comment in json), we hope people will notice this pattern and follow it when editing this file. ### Are these changes tested? Manually tested. ### Are there any user-facing changes? None. * GitHub Issue: #45209 Lead-authored-by: Rossi Sun <zanmato1984@gmail.com> Co-authored-by: Sutou Kouhei <kou@cozmixng.org> Signed-off-by: Rossi Sun <zanmato1984@gmail.com>
2025-01-10 23:14:20 +08:00
"sanitizer-ubsan",
"ninja-debug"
GH-34004: [C++] Add a benchmarks-maximal CMake preset (#34005) ### Rationale for this change Add a benchmarks-maximal CMake preset to benchmark all components or to test the compilation of all benchmark files. ### What changes are included in this PR? Along with the new preset, also 1. Fixed indentation of the json file. 2. The "maximal" presets actually include CUDA, so I fixed their display names. ### Are these changes tested? The preset works locally on my machine. ### Are there any user-facing changes? No. * Closes: #34004 Authored-by: Jin Shang <shangjin1997@gmail.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2023-02-03 04:03:59 +08:00
],
GH-45209: [C++][CMake] Fix the issue that allocator not disabled for sanitizer cmake presets (#45210) ### Rationale for this change I gave the reason in #45209 ### What changes are included in this PR? Adjust the inheritance list order and make a lot of simplification/regrouping/reordering for existing presets the way I see fit. Also introduce a soft rule to order inheritance list: `sanitizer` comes before `features` comes before `base`. Though we can't really mandate such a rule (thus it's "soft") or make it clear in comments (our current cmake dosn't support comment in json), we hope people will notice this pattern and follow it when editing this file. ### Are these changes tested? Manually tested. ### Are there any user-facing changes? None. * GitHub Issue: #45209 Lead-authored-by: Rossi Sun <zanmato1984@gmail.com> Co-authored-by: Sutou Kouhei <kou@cozmixng.org> Signed-off-by: Rossi Sun <zanmato1984@gmail.com>
2025-01-10 23:14:20 +08:00
"displayName": "Debug build for UBSAN with tests and more optional components",
ARROW-14714: [C++][Doc] Rework CMake presets and add documentation Try to define CMake presets that correspond to common use cases. Switch to version 3 of the format so that `binaryDir` isn't mandatory anymore. Also add display names so that the command line can be more informative. Document the use of CMake presets. Summary of available presets: ``` $ cmake --list-presets Available configure presets: "ninja-debug-minimal" - Debug build without anything enabled "ninja-debug-basic" - Debug build with tests and reduced dependencies "ninja-debug" - Debug build with tests and more optional components "ninja-debug-cuda" - Debug build with tests and CUDA integration "ninja-debug-filesystems" - Debug build with tests and filesystems "ninja-debug-flight" - Debug build with tests and Flight "ninja-debug-gandiva" - Debug build with tests and Gandiva "ninja-debug-python" - Debug build with tests and Python support "ninja-debug-maximal" - Debug build with everything enabled (except benchmarks and CUDA) "ninja-release-minimal" - Release build without anything enabled "ninja-release-basic" - Release build with reduced dependencies "ninja-release" - Release build with more optional components "ninja-release-cuda" - Release build with CUDA integration "ninja-release-flight" - Release build with Flight "ninja-release-gandiva" - Release build with Gandiva "ninja-release-python" - Release build with Python support "ninja-release-maximal" - Release build with everything enabled (except benchmarks and CUDA) "ninja-benchmarks-basic" - Benchmarking build with reduced dependencies "ninja-benchmarks" - Benchmarking build with more optional components ``` Closes #11778 from pitrou/ARROW-14714-cmake-presets Authored-by: Antoine Pitrou <antoine@python.org> Signed-off-by: Krisztián Szűcs <szucs.krisztian@gmail.com>
2021-12-01 20:33:23 +01:00
"cacheVariables": {}
},
{
GH-45209: [C++][CMake] Fix the issue that allocator not disabled for sanitizer cmake presets (#45210) ### Rationale for this change I gave the reason in #45209 ### What changes are included in this PR? Adjust the inheritance list order and make a lot of simplification/regrouping/reordering for existing presets the way I see fit. Also introduce a soft rule to order inheritance list: `sanitizer` comes before `features` comes before `base`. Though we can't really mandate such a rule (thus it's "soft") or make it clear in comments (our current cmake dosn't support comment in json), we hope people will notice this pattern and follow it when editing this file. ### Are these changes tested? Manually tested. ### Are there any user-facing changes? None. * GitHub Issue: #45209 Lead-authored-by: Rossi Sun <zanmato1984@gmail.com> Co-authored-by: Sutou Kouhei <kou@cozmixng.org> Signed-off-by: Rossi Sun <zanmato1984@gmail.com>
2025-01-10 23:14:20 +08:00
"name": "fuzzing",
GH-34004: [C++] Add a benchmarks-maximal CMake preset (#34005) ### Rationale for this change Add a benchmarks-maximal CMake preset to benchmark all components or to test the compilation of all benchmark files. ### What changes are included in this PR? Along with the new preset, also 1. Fixed indentation of the json file. 2. The "maximal" presets actually include CUDA, so I fixed their display names. ### Are these changes tested? The preset works locally on my machine. ### Are there any user-facing changes? No. * Closes: #34004 Authored-by: Jin Shang <shangjin1997@gmail.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2023-02-03 04:03:59 +08:00
"inherits": [
GH-45209: [C++][CMake] Fix the issue that allocator not disabled for sanitizer cmake presets (#45210) ### Rationale for this change I gave the reason in #45209 ### What changes are included in this PR? Adjust the inheritance list order and make a lot of simplification/regrouping/reordering for existing presets the way I see fit. Also introduce a soft rule to order inheritance list: `sanitizer` comes before `features` comes before `base`. Though we can't really mandate such a rule (thus it's "soft") or make it clear in comments (our current cmake dosn't support comment in json), we hope people will notice this pattern and follow it when editing this file. ### Are these changes tested? Manually tested. ### Are there any user-facing changes? None. * GitHub Issue: #45209 Lead-authored-by: Rossi Sun <zanmato1984@gmail.com> Co-authored-by: Sutou Kouhei <kou@cozmixng.org> Signed-off-by: Rossi Sun <zanmato1984@gmail.com>
2025-01-10 23:14:20 +08:00
"sanitizer-asan",
"sanitizer-ubsan",
"base"
GH-34004: [C++] Add a benchmarks-maximal CMake preset (#34005) ### Rationale for this change Add a benchmarks-maximal CMake preset to benchmark all components or to test the compilation of all benchmark files. ### What changes are included in this PR? Along with the new preset, also 1. Fixed indentation of the json file. 2. The "maximal" presets actually include CUDA, so I fixed their display names. ### Are these changes tested? The preset works locally on my machine. ### Are there any user-facing changes? No. * Closes: #34004 Authored-by: Jin Shang <shangjin1997@gmail.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2023-02-03 04:03:59 +08:00
],
GH-45209: [C++][CMake] Fix the issue that allocator not disabled for sanitizer cmake presets (#45210) ### Rationale for this change I gave the reason in #45209 ### What changes are included in this PR? Adjust the inheritance list order and make a lot of simplification/regrouping/reordering for existing presets the way I see fit. Also introduce a soft rule to order inheritance list: `sanitizer` comes before `features` comes before `base`. Though we can't really mandate such a rule (thus it's "soft") or make it clear in comments (our current cmake dosn't support comment in json), we hope people will notice this pattern and follow it when editing this file. ### Are these changes tested? Manually tested. ### Are there any user-facing changes? None. * GitHub Issue: #45209 Lead-authored-by: Rossi Sun <zanmato1984@gmail.com> Co-authored-by: Sutou Kouhei <kou@cozmixng.org> Signed-off-by: Rossi Sun <zanmato1984@gmail.com>
2025-01-10 23:14:20 +08:00
"displayName": "Debug build with IPC and Parquet fuzzing targets",
"cacheVariables": {
GH-48395: [C++][Dev] Update fuzzing CMake preset (#48396) ### Rationale for this change We have more features enabled on our fuzzing setup but we haven't updated the corresponding CMake preset. ### Are these changes tested? Manually. ### Are there any user-facing changes? No. * GitHub Issue: #48395 Authored-by: Antoine Pitrou <antoine@python.org> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2025-12-09 21:55:11 +01:00
"ARROW_CSV": "ON",
"ARROW_DEPENDENCY_SOURCE": "BUNDLED",
"ARROW_FUZZING": "ON",
"ARROW_IPC": "ON",
"ARROW_PARQUET": "ON",
"ARROW_WITH_BROTLI": "ON",
"ARROW_WITH_LZ4": "ON",
"ARROW_WITH_SNAPPY": "ON",
"ARROW_WITH_ZLIB": "ON",
"ARROW_WITH_ZSTD": "ON",
GH-45209: [C++][CMake] Fix the issue that allocator not disabled for sanitizer cmake presets (#45210) ### Rationale for this change I gave the reason in #45209 ### What changes are included in this PR? Adjust the inheritance list order and make a lot of simplification/regrouping/reordering for existing presets the way I see fit. Also introduce a soft rule to order inheritance list: `sanitizer` comes before `features` comes before `base`. Though we can't really mandate such a rule (thus it's "soft") or make it clear in comments (our current cmake dosn't support comment in json), we hope people will notice this pattern and follow it when editing this file. ### Are these changes tested? Manually tested. ### Are there any user-facing changes? None. * GitHub Issue: #45209 Lead-authored-by: Rossi Sun <zanmato1984@gmail.com> Co-authored-by: Sutou Kouhei <kou@cozmixng.org> Signed-off-by: Rossi Sun <zanmato1984@gmail.com>
2025-01-10 23:14:20 +08:00
"CMAKE_BUILD_TYPE": "Debug",
"CMAKE_C_COMPILER": "clang",
"CMAKE_CXX_COMPILER": "clang++",
GH-48395: [C++][Dev] Update fuzzing CMake preset (#48396) ### Rationale for this change We have more features enabled on our fuzzing setup but we haven't updated the corresponding CMake preset. ### Are these changes tested? Manually. ### Are there any user-facing changes? No. * GitHub Issue: #48395 Authored-by: Antoine Pitrou <antoine@python.org> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2025-12-09 21:55:11 +01:00
"PARQUET_REQUIRE_ENCRYPTION": "ON"
GH-45209: [C++][CMake] Fix the issue that allocator not disabled for sanitizer cmake presets (#45210) ### Rationale for this change I gave the reason in #45209 ### What changes are included in this PR? Adjust the inheritance list order and make a lot of simplification/regrouping/reordering for existing presets the way I see fit. Also introduce a soft rule to order inheritance list: `sanitizer` comes before `features` comes before `base`. Though we can't really mandate such a rule (thus it's "soft") or make it clear in comments (our current cmake dosn't support comment in json), we hope people will notice this pattern and follow it when editing this file. ### Are these changes tested? Manually tested. ### Are there any user-facing changes? None. * GitHub Issue: #45209 Lead-authored-by: Rossi Sun <zanmato1984@gmail.com> Co-authored-by: Sutou Kouhei <kou@cozmixng.org> Signed-off-by: Rossi Sun <zanmato1984@gmail.com>
2025-01-10 23:14:20 +08:00
}
},
{
"name": "ninja-release-minimal",
"inherits": [
"features-minimal",
"base-release"
],
"displayName": "Release build without anything enabled",
ARROW-14714: [C++][Doc] Rework CMake presets and add documentation Try to define CMake presets that correspond to common use cases. Switch to version 3 of the format so that `binaryDir` isn't mandatory anymore. Also add display names so that the command line can be more informative. Document the use of CMake presets. Summary of available presets: ``` $ cmake --list-presets Available configure presets: "ninja-debug-minimal" - Debug build without anything enabled "ninja-debug-basic" - Debug build with tests and reduced dependencies "ninja-debug" - Debug build with tests and more optional components "ninja-debug-cuda" - Debug build with tests and CUDA integration "ninja-debug-filesystems" - Debug build with tests and filesystems "ninja-debug-flight" - Debug build with tests and Flight "ninja-debug-gandiva" - Debug build with tests and Gandiva "ninja-debug-python" - Debug build with tests and Python support "ninja-debug-maximal" - Debug build with everything enabled (except benchmarks and CUDA) "ninja-release-minimal" - Release build without anything enabled "ninja-release-basic" - Release build with reduced dependencies "ninja-release" - Release build with more optional components "ninja-release-cuda" - Release build with CUDA integration "ninja-release-flight" - Release build with Flight "ninja-release-gandiva" - Release build with Gandiva "ninja-release-python" - Release build with Python support "ninja-release-maximal" - Release build with everything enabled (except benchmarks and CUDA) "ninja-benchmarks-basic" - Benchmarking build with reduced dependencies "ninja-benchmarks" - Benchmarking build with more optional components ``` Closes #11778 from pitrou/ARROW-14714-cmake-presets Authored-by: Antoine Pitrou <antoine@python.org> Signed-off-by: Krisztián Szűcs <szucs.krisztian@gmail.com>
2021-12-01 20:33:23 +01:00
"cacheVariables": {}
},
{
GH-45209: [C++][CMake] Fix the issue that allocator not disabled for sanitizer cmake presets (#45210) ### Rationale for this change I gave the reason in #45209 ### What changes are included in this PR? Adjust the inheritance list order and make a lot of simplification/regrouping/reordering for existing presets the way I see fit. Also introduce a soft rule to order inheritance list: `sanitizer` comes before `features` comes before `base`. Though we can't really mandate such a rule (thus it's "soft") or make it clear in comments (our current cmake dosn't support comment in json), we hope people will notice this pattern and follow it when editing this file. ### Are these changes tested? Manually tested. ### Are there any user-facing changes? None. * GitHub Issue: #45209 Lead-authored-by: Rossi Sun <zanmato1984@gmail.com> Co-authored-by: Sutou Kouhei <kou@cozmixng.org> Signed-off-by: Rossi Sun <zanmato1984@gmail.com>
2025-01-10 23:14:20 +08:00
"name": "ninja-release-basic",
GH-34004: [C++] Add a benchmarks-maximal CMake preset (#34005) ### Rationale for this change Add a benchmarks-maximal CMake preset to benchmark all components or to test the compilation of all benchmark files. ### What changes are included in this PR? Along with the new preset, also 1. Fixed indentation of the json file. 2. The "maximal" presets actually include CUDA, so I fixed their display names. ### Are these changes tested? The preset works locally on my machine. ### Are there any user-facing changes? No. * Closes: #34004 Authored-by: Jin Shang <shangjin1997@gmail.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2023-02-03 04:03:59 +08:00
"inherits": [
GH-45209: [C++][CMake] Fix the issue that allocator not disabled for sanitizer cmake presets (#45210) ### Rationale for this change I gave the reason in #45209 ### What changes are included in this PR? Adjust the inheritance list order and make a lot of simplification/regrouping/reordering for existing presets the way I see fit. Also introduce a soft rule to order inheritance list: `sanitizer` comes before `features` comes before `base`. Though we can't really mandate such a rule (thus it's "soft") or make it clear in comments (our current cmake dosn't support comment in json), we hope people will notice this pattern and follow it when editing this file. ### Are these changes tested? Manually tested. ### Are there any user-facing changes? None. * GitHub Issue: #45209 Lead-authored-by: Rossi Sun <zanmato1984@gmail.com> Co-authored-by: Sutou Kouhei <kou@cozmixng.org> Signed-off-by: Rossi Sun <zanmato1984@gmail.com>
2025-01-10 23:14:20 +08:00
"features-basic",
"base-release"
GH-34004: [C++] Add a benchmarks-maximal CMake preset (#34005) ### Rationale for this change Add a benchmarks-maximal CMake preset to benchmark all components or to test the compilation of all benchmark files. ### What changes are included in this PR? Along with the new preset, also 1. Fixed indentation of the json file. 2. The "maximal" presets actually include CUDA, so I fixed their display names. ### Are these changes tested? The preset works locally on my machine. ### Are there any user-facing changes? No. * Closes: #34004 Authored-by: Jin Shang <shangjin1997@gmail.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2023-02-03 04:03:59 +08:00
],
GH-45209: [C++][CMake] Fix the issue that allocator not disabled for sanitizer cmake presets (#45210) ### Rationale for this change I gave the reason in #45209 ### What changes are included in this PR? Adjust the inheritance list order and make a lot of simplification/regrouping/reordering for existing presets the way I see fit. Also introduce a soft rule to order inheritance list: `sanitizer` comes before `features` comes before `base`. Though we can't really mandate such a rule (thus it's "soft") or make it clear in comments (our current cmake dosn't support comment in json), we hope people will notice this pattern and follow it when editing this file. ### Are these changes tested? Manually tested. ### Are there any user-facing changes? None. * GitHub Issue: #45209 Lead-authored-by: Rossi Sun <zanmato1984@gmail.com> Co-authored-by: Sutou Kouhei <kou@cozmixng.org> Signed-off-by: Rossi Sun <zanmato1984@gmail.com>
2025-01-10 23:14:20 +08:00
"displayName": "Release build with reduced dependencies",
ARROW-14714: [C++][Doc] Rework CMake presets and add documentation Try to define CMake presets that correspond to common use cases. Switch to version 3 of the format so that `binaryDir` isn't mandatory anymore. Also add display names so that the command line can be more informative. Document the use of CMake presets. Summary of available presets: ``` $ cmake --list-presets Available configure presets: "ninja-debug-minimal" - Debug build without anything enabled "ninja-debug-basic" - Debug build with tests and reduced dependencies "ninja-debug" - Debug build with tests and more optional components "ninja-debug-cuda" - Debug build with tests and CUDA integration "ninja-debug-filesystems" - Debug build with tests and filesystems "ninja-debug-flight" - Debug build with tests and Flight "ninja-debug-gandiva" - Debug build with tests and Gandiva "ninja-debug-python" - Debug build with tests and Python support "ninja-debug-maximal" - Debug build with everything enabled (except benchmarks and CUDA) "ninja-release-minimal" - Release build without anything enabled "ninja-release-basic" - Release build with reduced dependencies "ninja-release" - Release build with more optional components "ninja-release-cuda" - Release build with CUDA integration "ninja-release-flight" - Release build with Flight "ninja-release-gandiva" - Release build with Gandiva "ninja-release-python" - Release build with Python support "ninja-release-maximal" - Release build with everything enabled (except benchmarks and CUDA) "ninja-benchmarks-basic" - Benchmarking build with reduced dependencies "ninja-benchmarks" - Benchmarking build with more optional components ``` Closes #11778 from pitrou/ARROW-14714-cmake-presets Authored-by: Antoine Pitrou <antoine@python.org> Signed-off-by: Krisztián Szűcs <szucs.krisztian@gmail.com>
2021-12-01 20:33:23 +01:00
"cacheVariables": {}
},
GH-23221: [C++] Add support for building with Emscripten (#37821) Split from #37696 This is just the cmake changes to enable building on emscripten. Changes are: 1) Support for target system "emscripten" 2) Cmake preset for building libarrow ` ninja-release-python-emscripten` (same as `ninja-release-python`, but with emscripten support) 3) Override file for cmake on emscripten, to set various build parameters that need setting to make it build there. 4) Changes in pyarrow cmake so it works if you are building libarrow as shared library, and also an option to enable the cmake file there to just dump the current arrow configuration, which is useful for cross-compile builds. * Closes: #23221 Lead-authored-by: Joe Marshall <joe.marshall@nottingham.ac.uk> Co-authored-by: Sutou Kouhei <kou@clear-code.com> Co-authored-by: Joris Van den Bossche <jorisvandenbossche@gmail.com> Co-authored-by: Sutou Kouhei <kou@cozmixng.org> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2024-04-05 03:34:32 +01:00
{
GH-45209: [C++][CMake] Fix the issue that allocator not disabled for sanitizer cmake presets (#45210) ### Rationale for this change I gave the reason in #45209 ### What changes are included in this PR? Adjust the inheritance list order and make a lot of simplification/regrouping/reordering for existing presets the way I see fit. Also introduce a soft rule to order inheritance list: `sanitizer` comes before `features` comes before `base`. Though we can't really mandate such a rule (thus it's "soft") or make it clear in comments (our current cmake dosn't support comment in json), we hope people will notice this pattern and follow it when editing this file. ### Are these changes tested? Manually tested. ### Are there any user-facing changes? None. * GitHub Issue: #45209 Lead-authored-by: Rossi Sun <zanmato1984@gmail.com> Co-authored-by: Sutou Kouhei <kou@cozmixng.org> Signed-off-by: Rossi Sun <zanmato1984@gmail.com>
2025-01-10 23:14:20 +08:00
"name": "ninja-release",
GH-23221: [C++] Add support for building with Emscripten (#37821) Split from #37696 This is just the cmake changes to enable building on emscripten. Changes are: 1) Support for target system "emscripten" 2) Cmake preset for building libarrow ` ninja-release-python-emscripten` (same as `ninja-release-python`, but with emscripten support) 3) Override file for cmake on emscripten, to set various build parameters that need setting to make it build there. 4) Changes in pyarrow cmake so it works if you are building libarrow as shared library, and also an option to enable the cmake file there to just dump the current arrow configuration, which is useful for cross-compile builds. * Closes: #23221 Lead-authored-by: Joe Marshall <joe.marshall@nottingham.ac.uk> Co-authored-by: Sutou Kouhei <kou@clear-code.com> Co-authored-by: Joris Van den Bossche <jorisvandenbossche@gmail.com> Co-authored-by: Sutou Kouhei <kou@cozmixng.org> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2024-04-05 03:34:32 +01:00
"inherits": [
GH-45209: [C++][CMake] Fix the issue that allocator not disabled for sanitizer cmake presets (#45210) ### Rationale for this change I gave the reason in #45209 ### What changes are included in this PR? Adjust the inheritance list order and make a lot of simplification/regrouping/reordering for existing presets the way I see fit. Also introduce a soft rule to order inheritance list: `sanitizer` comes before `features` comes before `base`. Though we can't really mandate such a rule (thus it's "soft") or make it clear in comments (our current cmake dosn't support comment in json), we hope people will notice this pattern and follow it when editing this file. ### Are these changes tested? Manually tested. ### Are there any user-facing changes? None. * GitHub Issue: #45209 Lead-authored-by: Rossi Sun <zanmato1984@gmail.com> Co-authored-by: Sutou Kouhei <kou@cozmixng.org> Signed-off-by: Rossi Sun <zanmato1984@gmail.com>
2025-01-10 23:14:20 +08:00
"features-main",
"base-release"
GH-23221: [C++] Add support for building with Emscripten (#37821) Split from #37696 This is just the cmake changes to enable building on emscripten. Changes are: 1) Support for target system "emscripten" 2) Cmake preset for building libarrow ` ninja-release-python-emscripten` (same as `ninja-release-python`, but with emscripten support) 3) Override file for cmake on emscripten, to set various build parameters that need setting to make it build there. 4) Changes in pyarrow cmake so it works if you are building libarrow as shared library, and also an option to enable the cmake file there to just dump the current arrow configuration, which is useful for cross-compile builds. * Closes: #23221 Lead-authored-by: Joe Marshall <joe.marshall@nottingham.ac.uk> Co-authored-by: Sutou Kouhei <kou@clear-code.com> Co-authored-by: Joris Van den Bossche <jorisvandenbossche@gmail.com> Co-authored-by: Sutou Kouhei <kou@cozmixng.org> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2024-04-05 03:34:32 +01:00
],
GH-45209: [C++][CMake] Fix the issue that allocator not disabled for sanitizer cmake presets (#45210) ### Rationale for this change I gave the reason in #45209 ### What changes are included in this PR? Adjust the inheritance list order and make a lot of simplification/regrouping/reordering for existing presets the way I see fit. Also introduce a soft rule to order inheritance list: `sanitizer` comes before `features` comes before `base`. Though we can't really mandate such a rule (thus it's "soft") or make it clear in comments (our current cmake dosn't support comment in json), we hope people will notice this pattern and follow it when editing this file. ### Are these changes tested? Manually tested. ### Are there any user-facing changes? None. * GitHub Issue: #45209 Lead-authored-by: Rossi Sun <zanmato1984@gmail.com> Co-authored-by: Sutou Kouhei <kou@cozmixng.org> Signed-off-by: Rossi Sun <zanmato1984@gmail.com>
2025-01-10 23:14:20 +08:00
"displayName": "Release build with more optional components",
GH-23221: [C++] Add support for building with Emscripten (#37821) Split from #37696 This is just the cmake changes to enable building on emscripten. Changes are: 1) Support for target system "emscripten" 2) Cmake preset for building libarrow ` ninja-release-python-emscripten` (same as `ninja-release-python`, but with emscripten support) 3) Override file for cmake on emscripten, to set various build parameters that need setting to make it build there. 4) Changes in pyarrow cmake so it works if you are building libarrow as shared library, and also an option to enable the cmake file there to just dump the current arrow configuration, which is useful for cross-compile builds. * Closes: #23221 Lead-authored-by: Joe Marshall <joe.marshall@nottingham.ac.uk> Co-authored-by: Sutou Kouhei <kou@clear-code.com> Co-authored-by: Joris Van den Bossche <jorisvandenbossche@gmail.com> Co-authored-by: Sutou Kouhei <kou@cozmixng.org> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2024-04-05 03:34:32 +01:00
"cacheVariables": {}
},
{
GH-45209: [C++][CMake] Fix the issue that allocator not disabled for sanitizer cmake presets (#45210) ### Rationale for this change I gave the reason in #45209 ### What changes are included in this PR? Adjust the inheritance list order and make a lot of simplification/regrouping/reordering for existing presets the way I see fit. Also introduce a soft rule to order inheritance list: `sanitizer` comes before `features` comes before `base`. Though we can't really mandate such a rule (thus it's "soft") or make it clear in comments (our current cmake dosn't support comment in json), we hope people will notice this pattern and follow it when editing this file. ### Are these changes tested? Manually tested. ### Are there any user-facing changes? None. * GitHub Issue: #45209 Lead-authored-by: Rossi Sun <zanmato1984@gmail.com> Co-authored-by: Sutou Kouhei <kou@cozmixng.org> Signed-off-by: Rossi Sun <zanmato1984@gmail.com>
2025-01-10 23:14:20 +08:00
"name": "ninja-release-cuda",
GH-23221: [C++] Add support for building with Emscripten (#37821) Split from #37696 This is just the cmake changes to enable building on emscripten. Changes are: 1) Support for target system "emscripten" 2) Cmake preset for building libarrow ` ninja-release-python-emscripten` (same as `ninja-release-python`, but with emscripten support) 3) Override file for cmake on emscripten, to set various build parameters that need setting to make it build there. 4) Changes in pyarrow cmake so it works if you are building libarrow as shared library, and also an option to enable the cmake file there to just dump the current arrow configuration, which is useful for cross-compile builds. * Closes: #23221 Lead-authored-by: Joe Marshall <joe.marshall@nottingham.ac.uk> Co-authored-by: Sutou Kouhei <kou@clear-code.com> Co-authored-by: Joris Van den Bossche <jorisvandenbossche@gmail.com> Co-authored-by: Sutou Kouhei <kou@cozmixng.org> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2024-04-05 03:34:32 +01:00
"inherits": [
GH-45209: [C++][CMake] Fix the issue that allocator not disabled for sanitizer cmake presets (#45210) ### Rationale for this change I gave the reason in #45209 ### What changes are included in this PR? Adjust the inheritance list order and make a lot of simplification/regrouping/reordering for existing presets the way I see fit. Also introduce a soft rule to order inheritance list: `sanitizer` comes before `features` comes before `base`. Though we can't really mandate such a rule (thus it's "soft") or make it clear in comments (our current cmake dosn't support comment in json), we hope people will notice this pattern and follow it when editing this file. ### Are these changes tested? Manually tested. ### Are there any user-facing changes? None. * GitHub Issue: #45209 Lead-authored-by: Rossi Sun <zanmato1984@gmail.com> Co-authored-by: Sutou Kouhei <kou@cozmixng.org> Signed-off-by: Rossi Sun <zanmato1984@gmail.com>
2025-01-10 23:14:20 +08:00
"features-cuda",
GH-23221: [C++] Add support for building with Emscripten (#37821) Split from #37696 This is just the cmake changes to enable building on emscripten. Changes are: 1) Support for target system "emscripten" 2) Cmake preset for building libarrow ` ninja-release-python-emscripten` (same as `ninja-release-python`, but with emscripten support) 3) Override file for cmake on emscripten, to set various build parameters that need setting to make it build there. 4) Changes in pyarrow cmake so it works if you are building libarrow as shared library, and also an option to enable the cmake file there to just dump the current arrow configuration, which is useful for cross-compile builds. * Closes: #23221 Lead-authored-by: Joe Marshall <joe.marshall@nottingham.ac.uk> Co-authored-by: Sutou Kouhei <kou@clear-code.com> Co-authored-by: Joris Van den Bossche <jorisvandenbossche@gmail.com> Co-authored-by: Sutou Kouhei <kou@cozmixng.org> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2024-04-05 03:34:32 +01:00
"base-release"
],
GH-45209: [C++][CMake] Fix the issue that allocator not disabled for sanitizer cmake presets (#45210) ### Rationale for this change I gave the reason in #45209 ### What changes are included in this PR? Adjust the inheritance list order and make a lot of simplification/regrouping/reordering for existing presets the way I see fit. Also introduce a soft rule to order inheritance list: `sanitizer` comes before `features` comes before `base`. Though we can't really mandate such a rule (thus it's "soft") or make it clear in comments (our current cmake dosn't support comment in json), we hope people will notice this pattern and follow it when editing this file. ### Are these changes tested? Manually tested. ### Are there any user-facing changes? None. * GitHub Issue: #45209 Lead-authored-by: Rossi Sun <zanmato1984@gmail.com> Co-authored-by: Sutou Kouhei <kou@cozmixng.org> Signed-off-by: Rossi Sun <zanmato1984@gmail.com>
2025-01-10 23:14:20 +08:00
"displayName": "Release build with CUDA integration",
GH-23221: [C++] Add support for building with Emscripten (#37821) Split from #37696 This is just the cmake changes to enable building on emscripten. Changes are: 1) Support for target system "emscripten" 2) Cmake preset for building libarrow ` ninja-release-python-emscripten` (same as `ninja-release-python`, but with emscripten support) 3) Override file for cmake on emscripten, to set various build parameters that need setting to make it build there. 4) Changes in pyarrow cmake so it works if you are building libarrow as shared library, and also an option to enable the cmake file there to just dump the current arrow configuration, which is useful for cross-compile builds. * Closes: #23221 Lead-authored-by: Joe Marshall <joe.marshall@nottingham.ac.uk> Co-authored-by: Sutou Kouhei <kou@clear-code.com> Co-authored-by: Joris Van den Bossche <jorisvandenbossche@gmail.com> Co-authored-by: Sutou Kouhei <kou@cozmixng.org> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2024-04-05 03:34:32 +01:00
"cacheVariables": {}
},
ARROW-14714: [C++][Doc] Rework CMake presets and add documentation Try to define CMake presets that correspond to common use cases. Switch to version 3 of the format so that `binaryDir` isn't mandatory anymore. Also add display names so that the command line can be more informative. Document the use of CMake presets. Summary of available presets: ``` $ cmake --list-presets Available configure presets: "ninja-debug-minimal" - Debug build without anything enabled "ninja-debug-basic" - Debug build with tests and reduced dependencies "ninja-debug" - Debug build with tests and more optional components "ninja-debug-cuda" - Debug build with tests and CUDA integration "ninja-debug-filesystems" - Debug build with tests and filesystems "ninja-debug-flight" - Debug build with tests and Flight "ninja-debug-gandiva" - Debug build with tests and Gandiva "ninja-debug-python" - Debug build with tests and Python support "ninja-debug-maximal" - Debug build with everything enabled (except benchmarks and CUDA) "ninja-release-minimal" - Release build without anything enabled "ninja-release-basic" - Release build with reduced dependencies "ninja-release" - Release build with more optional components "ninja-release-cuda" - Release build with CUDA integration "ninja-release-flight" - Release build with Flight "ninja-release-gandiva" - Release build with Gandiva "ninja-release-python" - Release build with Python support "ninja-release-maximal" - Release build with everything enabled (except benchmarks and CUDA) "ninja-benchmarks-basic" - Benchmarking build with reduced dependencies "ninja-benchmarks" - Benchmarking build with more optional components ``` Closes #11778 from pitrou/ARROW-14714-cmake-presets Authored-by: Antoine Pitrou <antoine@python.org> Signed-off-by: Krisztián Szűcs <szucs.krisztian@gmail.com>
2021-12-01 20:33:23 +01:00
{
"name": "ninja-release-flight",
GH-34004: [C++] Add a benchmarks-maximal CMake preset (#34005) ### Rationale for this change Add a benchmarks-maximal CMake preset to benchmark all components or to test the compilation of all benchmark files. ### What changes are included in this PR? Along with the new preset, also 1. Fixed indentation of the json file. 2. The "maximal" presets actually include CUDA, so I fixed their display names. ### Are these changes tested? The preset works locally on my machine. ### Are there any user-facing changes? No. * Closes: #34004 Authored-by: Jin Shang <shangjin1997@gmail.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2023-02-03 04:03:59 +08:00
"inherits": [
GH-45209: [C++][CMake] Fix the issue that allocator not disabled for sanitizer cmake presets (#45210) ### Rationale for this change I gave the reason in #45209 ### What changes are included in this PR? Adjust the inheritance list order and make a lot of simplification/regrouping/reordering for existing presets the way I see fit. Also introduce a soft rule to order inheritance list: `sanitizer` comes before `features` comes before `base`. Though we can't really mandate such a rule (thus it's "soft") or make it clear in comments (our current cmake dosn't support comment in json), we hope people will notice this pattern and follow it when editing this file. ### Are these changes tested? Manually tested. ### Are there any user-facing changes? None. * GitHub Issue: #45209 Lead-authored-by: Rossi Sun <zanmato1984@gmail.com> Co-authored-by: Sutou Kouhei <kou@cozmixng.org> Signed-off-by: Rossi Sun <zanmato1984@gmail.com>
2025-01-10 23:14:20 +08:00
"features-flight",
"base-release"
GH-34004: [C++] Add a benchmarks-maximal CMake preset (#34005) ### Rationale for this change Add a benchmarks-maximal CMake preset to benchmark all components or to test the compilation of all benchmark files. ### What changes are included in this PR? Along with the new preset, also 1. Fixed indentation of the json file. 2. The "maximal" presets actually include CUDA, so I fixed their display names. ### Are these changes tested? The preset works locally on my machine. ### Are there any user-facing changes? No. * Closes: #34004 Authored-by: Jin Shang <shangjin1997@gmail.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2023-02-03 04:03:59 +08:00
],
ARROW-14714: [C++][Doc] Rework CMake presets and add documentation Try to define CMake presets that correspond to common use cases. Switch to version 3 of the format so that `binaryDir` isn't mandatory anymore. Also add display names so that the command line can be more informative. Document the use of CMake presets. Summary of available presets: ``` $ cmake --list-presets Available configure presets: "ninja-debug-minimal" - Debug build without anything enabled "ninja-debug-basic" - Debug build with tests and reduced dependencies "ninja-debug" - Debug build with tests and more optional components "ninja-debug-cuda" - Debug build with tests and CUDA integration "ninja-debug-filesystems" - Debug build with tests and filesystems "ninja-debug-flight" - Debug build with tests and Flight "ninja-debug-gandiva" - Debug build with tests and Gandiva "ninja-debug-python" - Debug build with tests and Python support "ninja-debug-maximal" - Debug build with everything enabled (except benchmarks and CUDA) "ninja-release-minimal" - Release build without anything enabled "ninja-release-basic" - Release build with reduced dependencies "ninja-release" - Release build with more optional components "ninja-release-cuda" - Release build with CUDA integration "ninja-release-flight" - Release build with Flight "ninja-release-gandiva" - Release build with Gandiva "ninja-release-python" - Release build with Python support "ninja-release-maximal" - Release build with everything enabled (except benchmarks and CUDA) "ninja-benchmarks-basic" - Benchmarking build with reduced dependencies "ninja-benchmarks" - Benchmarking build with more optional components ``` Closes #11778 from pitrou/ARROW-14714-cmake-presets Authored-by: Antoine Pitrou <antoine@python.org> Signed-off-by: Krisztián Szűcs <szucs.krisztian@gmail.com>
2021-12-01 20:33:23 +01:00
"displayName": "Release build with Flight",
"cacheVariables": {}
},
GH-35315: [C++][CMake] Add presets for Flight SQL (#35317) ### Rationale for this change The `ninja-release-maximal` preset doesn't enable Flight SQL. ### What changes are included in this PR? Add Flight SQL related presets. ### Are these changes tested? Yes. ### Are there any user-facing changes? Yes. * Closes: #35315 Authored-by: Sutou Kouhei <kou@clear-code.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2023-04-26 09:23:58 +09:00
{
"name": "ninja-release-flight-sql",
"inherits": [
GH-45209: [C++][CMake] Fix the issue that allocator not disabled for sanitizer cmake presets (#45210) ### Rationale for this change I gave the reason in #45209 ### What changes are included in this PR? Adjust the inheritance list order and make a lot of simplification/regrouping/reordering for existing presets the way I see fit. Also introduce a soft rule to order inheritance list: `sanitizer` comes before `features` comes before `base`. Though we can't really mandate such a rule (thus it's "soft") or make it clear in comments (our current cmake dosn't support comment in json), we hope people will notice this pattern and follow it when editing this file. ### Are these changes tested? Manually tested. ### Are there any user-facing changes? None. * GitHub Issue: #45209 Lead-authored-by: Rossi Sun <zanmato1984@gmail.com> Co-authored-by: Sutou Kouhei <kou@cozmixng.org> Signed-off-by: Rossi Sun <zanmato1984@gmail.com>
2025-01-10 23:14:20 +08:00
"features-flight-sql",
"base-release"
GH-35315: [C++][CMake] Add presets for Flight SQL (#35317) ### Rationale for this change The `ninja-release-maximal` preset doesn't enable Flight SQL. ### What changes are included in this PR? Add Flight SQL related presets. ### Are these changes tested? Yes. ### Are there any user-facing changes? Yes. * Closes: #35315 Authored-by: Sutou Kouhei <kou@clear-code.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2023-04-26 09:23:58 +09:00
],
"displayName": "Release build with Flight SQL",
"cacheVariables": {}
},
GH-48575: [C++][FlightRPC] Standalone ODBC macOS CI (#48577) ### Rationale for this change #48575 ### What changes are included in this PR? - Add new ODBC workflow for macOS Intel 15 and 14 arm64. - Added ODBC build fixes to enable build on macOS CI. ### Are these changes tested? Tested in CI and local macOS Intel and M1 environments. ### Are there any user-facing changes? N/A * GitHub Issue: #48575 Lead-authored-by: Alina (Xi) Li <alina.li@improving.com> Co-authored-by: justing-bq <62349012+justing-bq@users.noreply.github.com> Co-authored-by: Victor Tsang <victor.tsang@improving.com> Co-authored-by: Alina (Xi) Li <alinal@bitquilltech.com> Co-authored-by: vic-tsang <victor.tsang@improving.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2026-02-07 03:54:25 -08:00
{
"name": "ninja-release-flight-sql-odbc",
"inherits": [
"features-flight-sql",
"base-release"
],
"displayName": "Release build with Flight SQL ODBC",
"cacheVariables": {
"ARROW_FLIGHT_SQL_ODBC": "ON"
}
},
ARROW-14714: [C++][Doc] Rework CMake presets and add documentation Try to define CMake presets that correspond to common use cases. Switch to version 3 of the format so that `binaryDir` isn't mandatory anymore. Also add display names so that the command line can be more informative. Document the use of CMake presets. Summary of available presets: ``` $ cmake --list-presets Available configure presets: "ninja-debug-minimal" - Debug build without anything enabled "ninja-debug-basic" - Debug build with tests and reduced dependencies "ninja-debug" - Debug build with tests and more optional components "ninja-debug-cuda" - Debug build with tests and CUDA integration "ninja-debug-filesystems" - Debug build with tests and filesystems "ninja-debug-flight" - Debug build with tests and Flight "ninja-debug-gandiva" - Debug build with tests and Gandiva "ninja-debug-python" - Debug build with tests and Python support "ninja-debug-maximal" - Debug build with everything enabled (except benchmarks and CUDA) "ninja-release-minimal" - Release build without anything enabled "ninja-release-basic" - Release build with reduced dependencies "ninja-release" - Release build with more optional components "ninja-release-cuda" - Release build with CUDA integration "ninja-release-flight" - Release build with Flight "ninja-release-gandiva" - Release build with Gandiva "ninja-release-python" - Release build with Python support "ninja-release-maximal" - Release build with everything enabled (except benchmarks and CUDA) "ninja-benchmarks-basic" - Benchmarking build with reduced dependencies "ninja-benchmarks" - Benchmarking build with more optional components ``` Closes #11778 from pitrou/ARROW-14714-cmake-presets Authored-by: Antoine Pitrou <antoine@python.org> Signed-off-by: Krisztián Szűcs <szucs.krisztian@gmail.com>
2021-12-01 20:33:23 +01:00
{
"name": "ninja-release-gandiva",
GH-34004: [C++] Add a benchmarks-maximal CMake preset (#34005) ### Rationale for this change Add a benchmarks-maximal CMake preset to benchmark all components or to test the compilation of all benchmark files. ### What changes are included in this PR? Along with the new preset, also 1. Fixed indentation of the json file. 2. The "maximal" presets actually include CUDA, so I fixed their display names. ### Are these changes tested? The preset works locally on my machine. ### Are there any user-facing changes? No. * Closes: #34004 Authored-by: Jin Shang <shangjin1997@gmail.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2023-02-03 04:03:59 +08:00
"inherits": [
GH-45209: [C++][CMake] Fix the issue that allocator not disabled for sanitizer cmake presets (#45210) ### Rationale for this change I gave the reason in #45209 ### What changes are included in this PR? Adjust the inheritance list order and make a lot of simplification/regrouping/reordering for existing presets the way I see fit. Also introduce a soft rule to order inheritance list: `sanitizer` comes before `features` comes before `base`. Though we can't really mandate such a rule (thus it's "soft") or make it clear in comments (our current cmake dosn't support comment in json), we hope people will notice this pattern and follow it when editing this file. ### Are these changes tested? Manually tested. ### Are there any user-facing changes? None. * GitHub Issue: #45209 Lead-authored-by: Rossi Sun <zanmato1984@gmail.com> Co-authored-by: Sutou Kouhei <kou@cozmixng.org> Signed-off-by: Rossi Sun <zanmato1984@gmail.com>
2025-01-10 23:14:20 +08:00
"features-gandiva",
"base-release"
GH-34004: [C++] Add a benchmarks-maximal CMake preset (#34005) ### Rationale for this change Add a benchmarks-maximal CMake preset to benchmark all components or to test the compilation of all benchmark files. ### What changes are included in this PR? Along with the new preset, also 1. Fixed indentation of the json file. 2. The "maximal" presets actually include CUDA, so I fixed their display names. ### Are these changes tested? The preset works locally on my machine. ### Are there any user-facing changes? No. * Closes: #34004 Authored-by: Jin Shang <shangjin1997@gmail.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2023-02-03 04:03:59 +08:00
],
ARROW-14714: [C++][Doc] Rework CMake presets and add documentation Try to define CMake presets that correspond to common use cases. Switch to version 3 of the format so that `binaryDir` isn't mandatory anymore. Also add display names so that the command line can be more informative. Document the use of CMake presets. Summary of available presets: ``` $ cmake --list-presets Available configure presets: "ninja-debug-minimal" - Debug build without anything enabled "ninja-debug-basic" - Debug build with tests and reduced dependencies "ninja-debug" - Debug build with tests and more optional components "ninja-debug-cuda" - Debug build with tests and CUDA integration "ninja-debug-filesystems" - Debug build with tests and filesystems "ninja-debug-flight" - Debug build with tests and Flight "ninja-debug-gandiva" - Debug build with tests and Gandiva "ninja-debug-python" - Debug build with tests and Python support "ninja-debug-maximal" - Debug build with everything enabled (except benchmarks and CUDA) "ninja-release-minimal" - Release build without anything enabled "ninja-release-basic" - Release build with reduced dependencies "ninja-release" - Release build with more optional components "ninja-release-cuda" - Release build with CUDA integration "ninja-release-flight" - Release build with Flight "ninja-release-gandiva" - Release build with Gandiva "ninja-release-python" - Release build with Python support "ninja-release-maximal" - Release build with everything enabled (except benchmarks and CUDA) "ninja-benchmarks-basic" - Benchmarking build with reduced dependencies "ninja-benchmarks" - Benchmarking build with more optional components ``` Closes #11778 from pitrou/ARROW-14714-cmake-presets Authored-by: Antoine Pitrou <antoine@python.org> Signed-off-by: Krisztián Szűcs <szucs.krisztian@gmail.com>
2021-12-01 20:33:23 +01:00
"displayName": "Release build with Gandiva",
"cacheVariables": {}
},
ARROW-17868: [C++][Python] Restore the ARROW_PYTHON CMake option (#14273) Restore it but it's marked as a deprecated option. Because the Python component in Apache Arrow C++ was moved to PyArrow by ARROW-16340. It' removed in a feature release. Users should use CMake presets instead of ARROW_PYTHON but CMake presets requires CMake 3.19 or later. Lead-authored-by: Sutou Kouhei <kou@clear-code.com> Co-authored-by: Sutou Kouhei <kou@cozmixng.org> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2022-10-01 20:46:17 +09:00
{
"name": "ninja-release-python-minimal",
GH-34004: [C++] Add a benchmarks-maximal CMake preset (#34005) ### Rationale for this change Add a benchmarks-maximal CMake preset to benchmark all components or to test the compilation of all benchmark files. ### What changes are included in this PR? Along with the new preset, also 1. Fixed indentation of the json file. 2. The "maximal" presets actually include CUDA, so I fixed their display names. ### Are these changes tested? The preset works locally on my machine. ### Are there any user-facing changes? No. * Closes: #34004 Authored-by: Jin Shang <shangjin1997@gmail.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2023-02-03 04:03:59 +08:00
"inherits": [
GH-45209: [C++][CMake] Fix the issue that allocator not disabled for sanitizer cmake presets (#45210) ### Rationale for this change I gave the reason in #45209 ### What changes are included in this PR? Adjust the inheritance list order and make a lot of simplification/regrouping/reordering for existing presets the way I see fit. Also introduce a soft rule to order inheritance list: `sanitizer` comes before `features` comes before `base`. Though we can't really mandate such a rule (thus it's "soft") or make it clear in comments (our current cmake dosn't support comment in json), we hope people will notice this pattern and follow it when editing this file. ### Are these changes tested? Manually tested. ### Are there any user-facing changes? None. * GitHub Issue: #45209 Lead-authored-by: Rossi Sun <zanmato1984@gmail.com> Co-authored-by: Sutou Kouhei <kou@cozmixng.org> Signed-off-by: Rossi Sun <zanmato1984@gmail.com>
2025-01-10 23:14:20 +08:00
"features-python-minimal",
"base-release"
GH-34004: [C++] Add a benchmarks-maximal CMake preset (#34005) ### Rationale for this change Add a benchmarks-maximal CMake preset to benchmark all components or to test the compilation of all benchmark files. ### What changes are included in this PR? Along with the new preset, also 1. Fixed indentation of the json file. 2. The "maximal" presets actually include CUDA, so I fixed their display names. ### Are these changes tested? The preset works locally on my machine. ### Are there any user-facing changes? No. * Closes: #34004 Authored-by: Jin Shang <shangjin1997@gmail.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2023-02-03 04:03:59 +08:00
],
ARROW-17868: [C++][Python] Restore the ARROW_PYTHON CMake option (#14273) Restore it but it's marked as a deprecated option. Because the Python component in Apache Arrow C++ was moved to PyArrow by ARROW-16340. It' removed in a feature release. Users should use CMake presets instead of ARROW_PYTHON but CMake presets requires CMake 3.19 or later. Lead-authored-by: Sutou Kouhei <kou@clear-code.com> Co-authored-by: Sutou Kouhei <kou@cozmixng.org> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2022-10-01 20:46:17 +09:00
"displayName": "Release build for PyArrow with minimal features",
"cacheVariables": {}
},
{
"name": "ninja-release-python",
GH-34004: [C++] Add a benchmarks-maximal CMake preset (#34005) ### Rationale for this change Add a benchmarks-maximal CMake preset to benchmark all components or to test the compilation of all benchmark files. ### What changes are included in this PR? Along with the new preset, also 1. Fixed indentation of the json file. 2. The "maximal" presets actually include CUDA, so I fixed their display names. ### Are these changes tested? The preset works locally on my machine. ### Are there any user-facing changes? No. * Closes: #34004 Authored-by: Jin Shang <shangjin1997@gmail.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2023-02-03 04:03:59 +08:00
"inherits": [
GH-45209: [C++][CMake] Fix the issue that allocator not disabled for sanitizer cmake presets (#45210) ### Rationale for this change I gave the reason in #45209 ### What changes are included in this PR? Adjust the inheritance list order and make a lot of simplification/regrouping/reordering for existing presets the way I see fit. Also introduce a soft rule to order inheritance list: `sanitizer` comes before `features` comes before `base`. Though we can't really mandate such a rule (thus it's "soft") or make it clear in comments (our current cmake dosn't support comment in json), we hope people will notice this pattern and follow it when editing this file. ### Are these changes tested? Manually tested. ### Are there any user-facing changes? None. * GitHub Issue: #45209 Lead-authored-by: Rossi Sun <zanmato1984@gmail.com> Co-authored-by: Sutou Kouhei <kou@cozmixng.org> Signed-off-by: Rossi Sun <zanmato1984@gmail.com>
2025-01-10 23:14:20 +08:00
"features-python",
"base-release"
GH-34004: [C++] Add a benchmarks-maximal CMake preset (#34005) ### Rationale for this change Add a benchmarks-maximal CMake preset to benchmark all components or to test the compilation of all benchmark files. ### What changes are included in this PR? Along with the new preset, also 1. Fixed indentation of the json file. 2. The "maximal" presets actually include CUDA, so I fixed their display names. ### Are these changes tested? The preset works locally on my machine. ### Are there any user-facing changes? No. * Closes: #34004 Authored-by: Jin Shang <shangjin1997@gmail.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2023-02-03 04:03:59 +08:00
],
ARROW-17868: [C++][Python] Restore the ARROW_PYTHON CMake option (#14273) Restore it but it's marked as a deprecated option. Because the Python component in Apache Arrow C++ was moved to PyArrow by ARROW-16340. It' removed in a feature release. Users should use CMake presets instead of ARROW_PYTHON but CMake presets requires CMake 3.19 or later. Lead-authored-by: Sutou Kouhei <kou@clear-code.com> Co-authored-by: Sutou Kouhei <kou@cozmixng.org> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2022-10-01 20:46:17 +09:00
"displayName": "Release build for PyArrow with common features (for backward compatibility)",
"cacheVariables": {}
},
{
"name": "ninja-release-python-maximal",
GH-34004: [C++] Add a benchmarks-maximal CMake preset (#34005) ### Rationale for this change Add a benchmarks-maximal CMake preset to benchmark all components or to test the compilation of all benchmark files. ### What changes are included in this PR? Along with the new preset, also 1. Fixed indentation of the json file. 2. The "maximal" presets actually include CUDA, so I fixed their display names. ### Are these changes tested? The preset works locally on my machine. ### Are there any user-facing changes? No. * Closes: #34004 Authored-by: Jin Shang <shangjin1997@gmail.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2023-02-03 04:03:59 +08:00
"inherits": [
GH-45209: [C++][CMake] Fix the issue that allocator not disabled for sanitizer cmake presets (#45210) ### Rationale for this change I gave the reason in #45209 ### What changes are included in this PR? Adjust the inheritance list order and make a lot of simplification/regrouping/reordering for existing presets the way I see fit. Also introduce a soft rule to order inheritance list: `sanitizer` comes before `features` comes before `base`. Though we can't really mandate such a rule (thus it's "soft") or make it clear in comments (our current cmake dosn't support comment in json), we hope people will notice this pattern and follow it when editing this file. ### Are these changes tested? Manually tested. ### Are there any user-facing changes? None. * GitHub Issue: #45209 Lead-authored-by: Rossi Sun <zanmato1984@gmail.com> Co-authored-by: Sutou Kouhei <kou@cozmixng.org> Signed-off-by: Rossi Sun <zanmato1984@gmail.com>
2025-01-10 23:14:20 +08:00
"features-python-maximal",
"base-release"
GH-34004: [C++] Add a benchmarks-maximal CMake preset (#34005) ### Rationale for this change Add a benchmarks-maximal CMake preset to benchmark all components or to test the compilation of all benchmark files. ### What changes are included in this PR? Along with the new preset, also 1. Fixed indentation of the json file. 2. The "maximal" presets actually include CUDA, so I fixed their display names. ### Are these changes tested? The preset works locally on my machine. ### Are there any user-facing changes? No. * Closes: #34004 Authored-by: Jin Shang <shangjin1997@gmail.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2023-02-03 04:03:59 +08:00
],
"displayName": "Release build for PyArrow with everything enabled",
ARROW-17868: [C++][Python] Restore the ARROW_PYTHON CMake option (#14273) Restore it but it's marked as a deprecated option. Because the Python component in Apache Arrow C++ was moved to PyArrow by ARROW-16340. It' removed in a feature release. Users should use CMake presets instead of ARROW_PYTHON but CMake presets requires CMake 3.19 or later. Lead-authored-by: Sutou Kouhei <kou@clear-code.com> Co-authored-by: Sutou Kouhei <kou@cozmixng.org> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2022-10-01 20:46:17 +09:00
"cacheVariables": {}
},
ARROW-14714: [C++][Doc] Rework CMake presets and add documentation Try to define CMake presets that correspond to common use cases. Switch to version 3 of the format so that `binaryDir` isn't mandatory anymore. Also add display names so that the command line can be more informative. Document the use of CMake presets. Summary of available presets: ``` $ cmake --list-presets Available configure presets: "ninja-debug-minimal" - Debug build without anything enabled "ninja-debug-basic" - Debug build with tests and reduced dependencies "ninja-debug" - Debug build with tests and more optional components "ninja-debug-cuda" - Debug build with tests and CUDA integration "ninja-debug-filesystems" - Debug build with tests and filesystems "ninja-debug-flight" - Debug build with tests and Flight "ninja-debug-gandiva" - Debug build with tests and Gandiva "ninja-debug-python" - Debug build with tests and Python support "ninja-debug-maximal" - Debug build with everything enabled (except benchmarks and CUDA) "ninja-release-minimal" - Release build without anything enabled "ninja-release-basic" - Release build with reduced dependencies "ninja-release" - Release build with more optional components "ninja-release-cuda" - Release build with CUDA integration "ninja-release-flight" - Release build with Flight "ninja-release-gandiva" - Release build with Gandiva "ninja-release-python" - Release build with Python support "ninja-release-maximal" - Release build with everything enabled (except benchmarks and CUDA) "ninja-benchmarks-basic" - Benchmarking build with reduced dependencies "ninja-benchmarks" - Benchmarking build with more optional components ``` Closes #11778 from pitrou/ARROW-14714-cmake-presets Authored-by: Antoine Pitrou <antoine@python.org> Signed-off-by: Krisztián Szűcs <szucs.krisztian@gmail.com>
2021-12-01 20:33:23 +01:00
{
"name": "ninja-release-maximal",
GH-34004: [C++] Add a benchmarks-maximal CMake preset (#34005) ### Rationale for this change Add a benchmarks-maximal CMake preset to benchmark all components or to test the compilation of all benchmark files. ### What changes are included in this PR? Along with the new preset, also 1. Fixed indentation of the json file. 2. The "maximal" presets actually include CUDA, so I fixed their display names. ### Are these changes tested? The preset works locally on my machine. ### Are there any user-facing changes? No. * Closes: #34004 Authored-by: Jin Shang <shangjin1997@gmail.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2023-02-03 04:03:59 +08:00
"inherits": [
GH-45209: [C++][CMake] Fix the issue that allocator not disabled for sanitizer cmake presets (#45210) ### Rationale for this change I gave the reason in #45209 ### What changes are included in this PR? Adjust the inheritance list order and make a lot of simplification/regrouping/reordering for existing presets the way I see fit. Also introduce a soft rule to order inheritance list: `sanitizer` comes before `features` comes before `base`. Though we can't really mandate such a rule (thus it's "soft") or make it clear in comments (our current cmake dosn't support comment in json), we hope people will notice this pattern and follow it when editing this file. ### Are these changes tested? Manually tested. ### Are there any user-facing changes? None. * GitHub Issue: #45209 Lead-authored-by: Rossi Sun <zanmato1984@gmail.com> Co-authored-by: Sutou Kouhei <kou@cozmixng.org> Signed-off-by: Rossi Sun <zanmato1984@gmail.com>
2025-01-10 23:14:20 +08:00
"features-maximal",
"base-release"
GH-34004: [C++] Add a benchmarks-maximal CMake preset (#34005) ### Rationale for this change Add a benchmarks-maximal CMake preset to benchmark all components or to test the compilation of all benchmark files. ### What changes are included in this PR? Along with the new preset, also 1. Fixed indentation of the json file. 2. The "maximal" presets actually include CUDA, so I fixed their display names. ### Are these changes tested? The preset works locally on my machine. ### Are there any user-facing changes? No. * Closes: #34004 Authored-by: Jin Shang <shangjin1997@gmail.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2023-02-03 04:03:59 +08:00
],
"displayName": "Release build with everything enabled (except benchmarks)",
ARROW-14714: [C++][Doc] Rework CMake presets and add documentation Try to define CMake presets that correspond to common use cases. Switch to version 3 of the format so that `binaryDir` isn't mandatory anymore. Also add display names so that the command line can be more informative. Document the use of CMake presets. Summary of available presets: ``` $ cmake --list-presets Available configure presets: "ninja-debug-minimal" - Debug build without anything enabled "ninja-debug-basic" - Debug build with tests and reduced dependencies "ninja-debug" - Debug build with tests and more optional components "ninja-debug-cuda" - Debug build with tests and CUDA integration "ninja-debug-filesystems" - Debug build with tests and filesystems "ninja-debug-flight" - Debug build with tests and Flight "ninja-debug-gandiva" - Debug build with tests and Gandiva "ninja-debug-python" - Debug build with tests and Python support "ninja-debug-maximal" - Debug build with everything enabled (except benchmarks and CUDA) "ninja-release-minimal" - Release build without anything enabled "ninja-release-basic" - Release build with reduced dependencies "ninja-release" - Release build with more optional components "ninja-release-cuda" - Release build with CUDA integration "ninja-release-flight" - Release build with Flight "ninja-release-gandiva" - Release build with Gandiva "ninja-release-python" - Release build with Python support "ninja-release-maximal" - Release build with everything enabled (except benchmarks and CUDA) "ninja-benchmarks-basic" - Benchmarking build with reduced dependencies "ninja-benchmarks" - Benchmarking build with more optional components ``` Closes #11778 from pitrou/ARROW-14714-cmake-presets Authored-by: Antoine Pitrou <antoine@python.org> Signed-off-by: Krisztián Szűcs <szucs.krisztian@gmail.com>
2021-12-01 20:33:23 +01:00
"cacheVariables": {}
},
GH-45209: [C++][CMake] Fix the issue that allocator not disabled for sanitizer cmake presets (#45210) ### Rationale for this change I gave the reason in #45209 ### What changes are included in this PR? Adjust the inheritance list order and make a lot of simplification/regrouping/reordering for existing presets the way I see fit. Also introduce a soft rule to order inheritance list: `sanitizer` comes before `features` comes before `base`. Though we can't really mandate such a rule (thus it's "soft") or make it clear in comments (our current cmake dosn't support comment in json), we hope people will notice this pattern and follow it when editing this file. ### Are these changes tested? Manually tested. ### Are there any user-facing changes? None. * GitHub Issue: #45209 Lead-authored-by: Rossi Sun <zanmato1984@gmail.com> Co-authored-by: Sutou Kouhei <kou@cozmixng.org> Signed-off-by: Rossi Sun <zanmato1984@gmail.com>
2025-01-10 23:14:20 +08:00
{
"name": "ninja-release-emscripten",
"inherits": [
"features-emscripten",
"base-release"
],
"displayName": "Release build which builds an Emscripten library",
"cacheVariables": {}
},
ARROW-14714: [C++][Doc] Rework CMake presets and add documentation Try to define CMake presets that correspond to common use cases. Switch to version 3 of the format so that `binaryDir` isn't mandatory anymore. Also add display names so that the command line can be more informative. Document the use of CMake presets. Summary of available presets: ``` $ cmake --list-presets Available configure presets: "ninja-debug-minimal" - Debug build without anything enabled "ninja-debug-basic" - Debug build with tests and reduced dependencies "ninja-debug" - Debug build with tests and more optional components "ninja-debug-cuda" - Debug build with tests and CUDA integration "ninja-debug-filesystems" - Debug build with tests and filesystems "ninja-debug-flight" - Debug build with tests and Flight "ninja-debug-gandiva" - Debug build with tests and Gandiva "ninja-debug-python" - Debug build with tests and Python support "ninja-debug-maximal" - Debug build with everything enabled (except benchmarks and CUDA) "ninja-release-minimal" - Release build without anything enabled "ninja-release-basic" - Release build with reduced dependencies "ninja-release" - Release build with more optional components "ninja-release-cuda" - Release build with CUDA integration "ninja-release-flight" - Release build with Flight "ninja-release-gandiva" - Release build with Gandiva "ninja-release-python" - Release build with Python support "ninja-release-maximal" - Release build with everything enabled (except benchmarks and CUDA) "ninja-benchmarks-basic" - Benchmarking build with reduced dependencies "ninja-benchmarks" - Benchmarking build with more optional components ``` Closes #11778 from pitrou/ARROW-14714-cmake-presets Authored-by: Antoine Pitrou <antoine@python.org> Signed-off-by: Krisztián Szűcs <szucs.krisztian@gmail.com>
2021-12-01 20:33:23 +01:00
{
"name": "ninja-benchmarks-basic",
GH-34004: [C++] Add a benchmarks-maximal CMake preset (#34005) ### Rationale for this change Add a benchmarks-maximal CMake preset to benchmark all components or to test the compilation of all benchmark files. ### What changes are included in this PR? Along with the new preset, also 1. Fixed indentation of the json file. 2. The "maximal" presets actually include CUDA, so I fixed their display names. ### Are these changes tested? The preset works locally on my machine. ### Are there any user-facing changes? No. * Closes: #34004 Authored-by: Jin Shang <shangjin1997@gmail.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2023-02-03 04:03:59 +08:00
"inherits": [
GH-45209: [C++][CMake] Fix the issue that allocator not disabled for sanitizer cmake presets (#45210) ### Rationale for this change I gave the reason in #45209 ### What changes are included in this PR? Adjust the inheritance list order and make a lot of simplification/regrouping/reordering for existing presets the way I see fit. Also introduce a soft rule to order inheritance list: `sanitizer` comes before `features` comes before `base`. Though we can't really mandate such a rule (thus it's "soft") or make it clear in comments (our current cmake dosn't support comment in json), we hope people will notice this pattern and follow it when editing this file. ### Are these changes tested? Manually tested. ### Are there any user-facing changes? None. * GitHub Issue: #45209 Lead-authored-by: Rossi Sun <zanmato1984@gmail.com> Co-authored-by: Sutou Kouhei <kou@cozmixng.org> Signed-off-by: Rossi Sun <zanmato1984@gmail.com>
2025-01-10 23:14:20 +08:00
"features-basic",
"base-benchmarks"
GH-34004: [C++] Add a benchmarks-maximal CMake preset (#34005) ### Rationale for this change Add a benchmarks-maximal CMake preset to benchmark all components or to test the compilation of all benchmark files. ### What changes are included in this PR? Along with the new preset, also 1. Fixed indentation of the json file. 2. The "maximal" presets actually include CUDA, so I fixed their display names. ### Are these changes tested? The preset works locally on my machine. ### Are there any user-facing changes? No. * Closes: #34004 Authored-by: Jin Shang <shangjin1997@gmail.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2023-02-03 04:03:59 +08:00
],
ARROW-14714: [C++][Doc] Rework CMake presets and add documentation Try to define CMake presets that correspond to common use cases. Switch to version 3 of the format so that `binaryDir` isn't mandatory anymore. Also add display names so that the command line can be more informative. Document the use of CMake presets. Summary of available presets: ``` $ cmake --list-presets Available configure presets: "ninja-debug-minimal" - Debug build without anything enabled "ninja-debug-basic" - Debug build with tests and reduced dependencies "ninja-debug" - Debug build with tests and more optional components "ninja-debug-cuda" - Debug build with tests and CUDA integration "ninja-debug-filesystems" - Debug build with tests and filesystems "ninja-debug-flight" - Debug build with tests and Flight "ninja-debug-gandiva" - Debug build with tests and Gandiva "ninja-debug-python" - Debug build with tests and Python support "ninja-debug-maximal" - Debug build with everything enabled (except benchmarks and CUDA) "ninja-release-minimal" - Release build without anything enabled "ninja-release-basic" - Release build with reduced dependencies "ninja-release" - Release build with more optional components "ninja-release-cuda" - Release build with CUDA integration "ninja-release-flight" - Release build with Flight "ninja-release-gandiva" - Release build with Gandiva "ninja-release-python" - Release build with Python support "ninja-release-maximal" - Release build with everything enabled (except benchmarks and CUDA) "ninja-benchmarks-basic" - Benchmarking build with reduced dependencies "ninja-benchmarks" - Benchmarking build with more optional components ``` Closes #11778 from pitrou/ARROW-14714-cmake-presets Authored-by: Antoine Pitrou <antoine@python.org> Signed-off-by: Krisztián Szűcs <szucs.krisztian@gmail.com>
2021-12-01 20:33:23 +01:00
"displayName": "Benchmarking build with reduced dependencies",
"cacheVariables": {}
},
{
"name": "ninja-benchmarks",
GH-34004: [C++] Add a benchmarks-maximal CMake preset (#34005) ### Rationale for this change Add a benchmarks-maximal CMake preset to benchmark all components or to test the compilation of all benchmark files. ### What changes are included in this PR? Along with the new preset, also 1. Fixed indentation of the json file. 2. The "maximal" presets actually include CUDA, so I fixed their display names. ### Are these changes tested? The preset works locally on my machine. ### Are there any user-facing changes? No. * Closes: #34004 Authored-by: Jin Shang <shangjin1997@gmail.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2023-02-03 04:03:59 +08:00
"inherits": [
GH-45209: [C++][CMake] Fix the issue that allocator not disabled for sanitizer cmake presets (#45210) ### Rationale for this change I gave the reason in #45209 ### What changes are included in this PR? Adjust the inheritance list order and make a lot of simplification/regrouping/reordering for existing presets the way I see fit. Also introduce a soft rule to order inheritance list: `sanitizer` comes before `features` comes before `base`. Though we can't really mandate such a rule (thus it's "soft") or make it clear in comments (our current cmake dosn't support comment in json), we hope people will notice this pattern and follow it when editing this file. ### Are these changes tested? Manually tested. ### Are there any user-facing changes? None. * GitHub Issue: #45209 Lead-authored-by: Rossi Sun <zanmato1984@gmail.com> Co-authored-by: Sutou Kouhei <kou@cozmixng.org> Signed-off-by: Rossi Sun <zanmato1984@gmail.com>
2025-01-10 23:14:20 +08:00
"features-main",
"base-benchmarks"
GH-34004: [C++] Add a benchmarks-maximal CMake preset (#34005) ### Rationale for this change Add a benchmarks-maximal CMake preset to benchmark all components or to test the compilation of all benchmark files. ### What changes are included in this PR? Along with the new preset, also 1. Fixed indentation of the json file. 2. The "maximal" presets actually include CUDA, so I fixed their display names. ### Are these changes tested? The preset works locally on my machine. ### Are there any user-facing changes? No. * Closes: #34004 Authored-by: Jin Shang <shangjin1997@gmail.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2023-02-03 04:03:59 +08:00
],
ARROW-14714: [C++][Doc] Rework CMake presets and add documentation Try to define CMake presets that correspond to common use cases. Switch to version 3 of the format so that `binaryDir` isn't mandatory anymore. Also add display names so that the command line can be more informative. Document the use of CMake presets. Summary of available presets: ``` $ cmake --list-presets Available configure presets: "ninja-debug-minimal" - Debug build without anything enabled "ninja-debug-basic" - Debug build with tests and reduced dependencies "ninja-debug" - Debug build with tests and more optional components "ninja-debug-cuda" - Debug build with tests and CUDA integration "ninja-debug-filesystems" - Debug build with tests and filesystems "ninja-debug-flight" - Debug build with tests and Flight "ninja-debug-gandiva" - Debug build with tests and Gandiva "ninja-debug-python" - Debug build with tests and Python support "ninja-debug-maximal" - Debug build with everything enabled (except benchmarks and CUDA) "ninja-release-minimal" - Release build without anything enabled "ninja-release-basic" - Release build with reduced dependencies "ninja-release" - Release build with more optional components "ninja-release-cuda" - Release build with CUDA integration "ninja-release-flight" - Release build with Flight "ninja-release-gandiva" - Release build with Gandiva "ninja-release-python" - Release build with Python support "ninja-release-maximal" - Release build with everything enabled (except benchmarks and CUDA) "ninja-benchmarks-basic" - Benchmarking build with reduced dependencies "ninja-benchmarks" - Benchmarking build with more optional components ``` Closes #11778 from pitrou/ARROW-14714-cmake-presets Authored-by: Antoine Pitrou <antoine@python.org> Signed-off-by: Krisztián Szűcs <szucs.krisztian@gmail.com>
2021-12-01 20:33:23 +01:00
"displayName": "Benchmarking build with more optional components",
"cacheVariables": {}
GH-34004: [C++] Add a benchmarks-maximal CMake preset (#34005) ### Rationale for this change Add a benchmarks-maximal CMake preset to benchmark all components or to test the compilation of all benchmark files. ### What changes are included in this PR? Along with the new preset, also 1. Fixed indentation of the json file. 2. The "maximal" presets actually include CUDA, so I fixed their display names. ### Are these changes tested? The preset works locally on my machine. ### Are there any user-facing changes? No. * Closes: #34004 Authored-by: Jin Shang <shangjin1997@gmail.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2023-02-03 04:03:59 +08:00
},
{
"name": "ninja-benchmarks-maximal",
"inherits": [
GH-45209: [C++][CMake] Fix the issue that allocator not disabled for sanitizer cmake presets (#45210) ### Rationale for this change I gave the reason in #45209 ### What changes are included in this PR? Adjust the inheritance list order and make a lot of simplification/regrouping/reordering for existing presets the way I see fit. Also introduce a soft rule to order inheritance list: `sanitizer` comes before `features` comes before `base`. Though we can't really mandate such a rule (thus it's "soft") or make it clear in comments (our current cmake dosn't support comment in json), we hope people will notice this pattern and follow it when editing this file. ### Are these changes tested? Manually tested. ### Are there any user-facing changes? None. * GitHub Issue: #45209 Lead-authored-by: Rossi Sun <zanmato1984@gmail.com> Co-authored-by: Sutou Kouhei <kou@cozmixng.org> Signed-off-by: Rossi Sun <zanmato1984@gmail.com>
2025-01-10 23:14:20 +08:00
"features-maximal",
"base-benchmarks"
GH-34004: [C++] Add a benchmarks-maximal CMake preset (#34005) ### Rationale for this change Add a benchmarks-maximal CMake preset to benchmark all components or to test the compilation of all benchmark files. ### What changes are included in this PR? Along with the new preset, also 1. Fixed indentation of the json file. 2. The "maximal" presets actually include CUDA, so I fixed their display names. ### Are these changes tested? The preset works locally on my machine. ### Are there any user-facing changes? No. * Closes: #34004 Authored-by: Jin Shang <shangjin1997@gmail.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2023-02-03 04:03:59 +08:00
],
GH-38977: [C++] Fix spelling (#38978) ### Rationale for this change ### What changes are included in this PR? ### Are these changes tested? ### Are there any user-facing changes? * Closes: #38977 Authored-by: Josh Soref <2119212+jsoref@users.noreply.github.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2023-12-10 07:19:44 -05:00
"displayName": "Benchmarking build with everything enabled",
GH-34004: [C++] Add a benchmarks-maximal CMake preset (#34005) ### Rationale for this change Add a benchmarks-maximal CMake preset to benchmark all components or to test the compilation of all benchmark files. ### What changes are included in this PR? Along with the new preset, also 1. Fixed indentation of the json file. 2. The "maximal" presets actually include CUDA, so I fixed their display names. ### Are these changes tested? The preset works locally on my machine. ### Are there any user-facing changes? No. * Closes: #34004 Authored-by: Jin Shang <shangjin1997@gmail.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2023-02-03 04:03:59 +08:00
"cacheVariables": {}
GH-47222: [CI][C++] Add a CI job that uses the same build options for JNI on macOS (#47305) ### Rationale for this change Static building for JNI build on macOS is failing in apache/arrow-java. We should avoid this in apache/arrow. See also: https://github.com/apache/arrow-java/pull/799 ### What changes are included in this PR? * Add a CI job for JNI build on macOS * Fix build problems for bundled AWS SDK for C++ ### Are these changes tested? Yes. ### Are there any user-facing changes? Yes. * GitHub Issue: #47222 Authored-by: Sutou Kouhei <kou@clear-code.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2025-08-14 14:26:52 +09:00
},
GH-47632: [CI][C++] Add a CI job for JNI on Linux (#47746) ### Rationale for this change This is for preventing to break Apache Arrow Java JNI use case on Linux. ### What changes are included in this PR? * Add a CI job that uses build options for JNI use case * Install more packages in manylinux image that is also used by JNI build ### Are these changes tested? Yes. ### Are there any user-facing changes? No. * GitHub Issue: #47632 Authored-by: Sutou Kouhei <kou@clear-code.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2025-10-12 23:57:32 +09:00
{
"name": "ninja-release-jni-linux",
"inherits": [
"base-release"
],
"displayName": "Build for JNI on Linux",
"cacheVariables": {
"ARROW_ACERO": "ON",
"ARROW_BUILD_SHARED": "OFF",
"ARROW_BUILD_STATIC": "ON",
"ARROW_CSV": "ON",
"ARROW_DATASET": "ON",
"ARROW_DEPENDENCY_SOURCE": "VCPKG",
"ARROW_DEPENDENCY_USE_SHARED": "OFF",
"ARROW_GANDIVA": "ON",
"ARROW_GANDIVA_STATIC_LIBSTDCPP": "ON",
"ARROW_GCS": "ON",
"ARROW_JSON": "ON",
"ARROW_ORC": "ON",
"ARROW_PARQUET": "ON",
"ARROW_RPATH_ORIGIN": "ON",
"ARROW_S3": "ON",
"ARROW_SUBSTRAIT": "ON",
"PARQUET_BUILD_EXAMPLES": "OFF",
"PARQUET_BUILD_EXECUTABLES": "OFF",
"PARQUET_REQUIRE_ENCRYPTION": "OFF",
"VCPKG_MANIFEST_MODE": "OFF",
"VCPKG_ROOT": "$env{VCPKG_ROOT}",
"VCPKG_TARGET_TRIPLET": "$env{VCPKG_TARGET_TRIPLET}"
}
},
GH-47222: [CI][C++] Add a CI job that uses the same build options for JNI on macOS (#47305) ### Rationale for this change Static building for JNI build on macOS is failing in apache/arrow-java. We should avoid this in apache/arrow. See also: https://github.com/apache/arrow-java/pull/799 ### What changes are included in this PR? * Add a CI job for JNI build on macOS * Fix build problems for bundled AWS SDK for C++ ### Are these changes tested? Yes. ### Are there any user-facing changes? Yes. * GitHub Issue: #47222 Authored-by: Sutou Kouhei <kou@clear-code.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2025-08-14 14:26:52 +09:00
{
"name": "ninja-release-jni-macos",
"inherits": [
"base-release"
],
"displayName": "Build for JNI on macOS",
"cacheVariables": {
"ARROW_ACERO": "ON",
"ARROW_BUILD_SHARED": "OFF",
"ARROW_BUILD_STATIC": "ON",
"ARROW_CSV": "ON",
"ARROW_DATASET": "ON",
"ARROW_DEPENDENCY_USE_SHARED": "OFF",
"ARROW_GANDIVA": "ON",
"ARROW_GANDIVA_STATIC_LIBSTDCPP": "ON",
"ARROW_JSON": "ON",
"ARROW_ORC": "ON",
"ARROW_PARQUET": "ON",
"ARROW_S3": "ON",
"ARROW_SUBSTRAIT": "ON",
"AWSSDK_SOURCE": "BUNDLED",
"GTest_SOURCE": "BUNDLED",
"PARQUET_BUILD_EXAMPLES": "OFF",
"PARQUET_BUILD_EXECUTABLES": "OFF",
"PARQUET_REQUIRE_ENCRYPTION": "OFF",
"re2_SOURCE": "BUNDLED"
}
ARROW-14714: [C++][Doc] Rework CMake presets and add documentation Try to define CMake presets that correspond to common use cases. Switch to version 3 of the format so that `binaryDir` isn't mandatory anymore. Also add display names so that the command line can be more informative. Document the use of CMake presets. Summary of available presets: ``` $ cmake --list-presets Available configure presets: "ninja-debug-minimal" - Debug build without anything enabled "ninja-debug-basic" - Debug build with tests and reduced dependencies "ninja-debug" - Debug build with tests and more optional components "ninja-debug-cuda" - Debug build with tests and CUDA integration "ninja-debug-filesystems" - Debug build with tests and filesystems "ninja-debug-flight" - Debug build with tests and Flight "ninja-debug-gandiva" - Debug build with tests and Gandiva "ninja-debug-python" - Debug build with tests and Python support "ninja-debug-maximal" - Debug build with everything enabled (except benchmarks and CUDA) "ninja-release-minimal" - Release build without anything enabled "ninja-release-basic" - Release build with reduced dependencies "ninja-release" - Release build with more optional components "ninja-release-cuda" - Release build with CUDA integration "ninja-release-flight" - Release build with Flight "ninja-release-gandiva" - Release build with Gandiva "ninja-release-python" - Release build with Python support "ninja-release-maximal" - Release build with everything enabled (except benchmarks and CUDA) "ninja-benchmarks-basic" - Benchmarking build with reduced dependencies "ninja-benchmarks" - Benchmarking build with more optional components ``` Closes #11778 from pitrou/ARROW-14714-cmake-presets Authored-by: Antoine Pitrou <antoine@python.org> Signed-off-by: Krisztián Szűcs <szucs.krisztian@gmail.com>
2021-12-01 20:33:23 +01:00
}
]
GH-42109: [C++][CMake] Add preset for Valgrind (#42110) ### Rationale for this change If we want to use Valgrind for our tests, we need to specify at least the following CMake options: * `ARROW_RUNTIME_SIMD_LEVEL=AVX2` * `ARROW_TEST_MEMCHECK=ON` If we have a CMake preset for Valgrind, we don't need to remember them. ### What changes are included in this PR? Add `features-valgrind` and `ninja-debug-valgrind` preset. `features-valgrind` is a hidden preset. ### Are these changes tested? Yes. I used this to reproduce #42107 on local. ### Are there any user-facing changes? No. * GitHub Issue: #42109 Authored-by: Sutou Kouhei <kou@clear-code.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
2024-06-13 18:04:31 +09:00
}
Reference in New Issue Copy Permalink