build: keep CMake and Meson definitions in sync - #896
Conversation
|
The failing Ubuntu Debug and macOS Build Example steps were caused by CRoaring 4.3.11 exposing I pushed
Replacement CI is now running on the updated head. |
|
@Sakshamm-Goyal Thanks for the PR! I opened #894 to track current status and initiated a discussion on how we can maintain and sync the build tools in the long term. Before taking actions, we'd better gather feedbacks from the community, especially from meson maintainers like @WillAyd. Meanwhile, there are prerequisite issues like #256 we need to resolve first. |
Summary
snapshot_summary_builder_test.ccin Meson'stable_testCloses #894.
Validation
python3 dev/test_build_definition_parity.pypre-commit run --files .github/workflows/test.yml cmake_modules/IcebergThirdpartyToolchain.cmake src/iceberg/catalog/CMakeLists.txt src/iceberg/catalog/rest/auth/meson.build src/iceberg/meson.build src/iceberg/test/meson.build dev/test_build_definition_parity.pycmake --build build-cmake-parity --target table_test --parallel 2ctest --test-dir build-cmake-parity -R '^table_test$' --output-on-failuremeson compile -C build-meson-parity table_test -j 2meson test -C build-meson-parity table_test --print-errorlogsAI assistance disclosure
AI-assisted tooling was used for initial regression-test scaffolding and mechanical build-definition edits. I reviewed the change end-to-end, verified the dependency choices and generated manifests, and ran the validations listed above. I am not aware of remaining uncertainty in the affected build paths.