lucasfang opened a new pull request, #536:
URL: https://github.com/apache/paimon-cpp/pull/536

   ### Purpose
   
   Linked issue: closes #535
   
   Add an AppleClang Release job on the macOS 15 ARM64 runner. The job builds 
the library, runs CTest and verifies an installed external CMake consumer, with 
failure diagnostics uploaded as artifacts.
   
   Use Homebrew for build dependencies and ccache, configure libclang for 
Vortex, and support macOS CPU detection when building flatc. Link Vortex 
against Darwin libraries/frameworks instead of Linux-only system libraries. 
Keep all optional modules enabled except Lumina, whose pinned artifact is only 
available for Linux x86_64. External network tests remain disabled.
   
   ### Tests
   
   Passed locally in the Ubuntu container:
   
   ```bash
   bash -n ci/scripts/build_paimon.sh ci/scripts/setup_flatc.sh
   ci/scripts/test_cmake_modules.sh
   pre-commit run --files .github/actions/setup-ccache/action.yml 
.github/workflows/build_and_test.yaml ci/scripts/build_paimon.sh 
ci/scripts/setup_flatc.sh cmake_modules/ThirdpartyToolchain.cmake
   git diff --check
   ```
   
   Additional isolated script checks with mocked platform/tool commands passed 
for Linux x86_64/AArch64 and Darwin x86_64/ARM64 feature selection, plus macOS 
libclang setup and flatc build/export behavior. These checks do not compile or 
execute macOS binaries. Actual macOS build, CTest and installation results are 
pending the new CI job; no local macOS runner is available.
   
   ### API and Format
   
   No public API, storage format or protocol changes.
   
   ### Documentation
   
   No user-facing feature changes. The workflow records the runner, build 
configuration and diagnostic artifact paths.
   
   ### Generative AI tooling
   
   Generated-by: OpenAI Codex (GPT-6)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to