Skip to content

Conversation

@bniladridas
Copy link
Member

I thought this might fix a bug I’m working on, but it turned out not to be the cause. Still, this setting is clearly incorrect and worth fixing.

CMAKE_OSX_DEPLOYMENT_TARGET="26.0" is invalid and should be set to a supported macOS version (e.g. "14.0"). This was surfaced while using clang-format version 21.1.8.

…and cleaned up some outdated content on the GitLab mirror.

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @bniladridas, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request primarily addresses a critical build configuration issue on macOS by correcting an invalid deployment target in CMake. This ensures that the project builds against a supported macOS version, preventing potential linker warnings or compatibility problems. Additionally, it updates the pre-commit configuration to leverage newer hooks and explicitly defines the path for clang-format, enhancing code quality checks and consistency.

Highlights

  • CMake Configuration Fix: Corrected an invalid CMAKE_OSX_DEPLOYMENT_TARGET value from "26.0" to "14.0" within the CMakeLists.txt file, ensuring proper macOS deployment target specification.
  • Pre-commit Hooks Update: Updated the pre-commit/pre-commit-hooks repository revision from v4.5.0 to v6.0.0 in .pre-commit-config.yaml.
  • Clang-format Path Specification: Modified the clang-format entry in .pre-commit-config.yaml to use an absolute path (/opt/homebrew/bin/clang-format), addressing potential issues with its discovery.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request correctly fixes an invalid macOS deployment target in the CMake configuration, which improves build stability on macOS. It also updates the pre-commit-hooks dependency to a newer version.

My review includes two main points:

  1. In .pre-commit-config.yaml, the path to clang-format has been hardcoded. This reduces portability and should be reverted to allow pre-commit to find the executable in the system's PATH.
  2. In CMakeLists.txt, the change to the deployment target has made a conditional block redundant. I've suggested a simplification to improve code clarity.

- id: clang-format
name: clang-format
entry: clang-format
entry: /opt/homebrew/bin/clang-format
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

high

Hardcoding the path to clang-format makes the pre-commit configuration less portable. This path is specific to Apple Silicon Macs with Homebrew installed in its default location. It will fail for developers on Intel-based Macs (where Homebrew is in /usr/local), on other operating systems, or for those who have installed clang-format through different means.

The language: system hook is designed to find the executable in the system's PATH. It's better to rely on that and ensure clang-format is in the PATH in the development environment. Please revert this to entry: clang-format.

        entry: clang-format

Comment on lines 149 to 153
set(CMAKE_OSX_DEPLOYMENT_TARGET "14.0" CACHE STRING "Minimum macOS version" FORCE)
else()
# Use current system version to avoid linker warnings with Homebrew libraries
set(CMAKE_OSX_DEPLOYMENT_TARGET "26.0" CACHE STRING "Minimum macOS version" FORCE)
set(CMAKE_OSX_DEPLOYMENT_TARGET "14.0" CACHE STRING "Minimum macOS version" FORCE)
endif()
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

With this change, both branches of the if(DEFINED ENV{CI} OR DEFINED ENV{GITHUB_ACTIONS}) conditional (starting on line 147) now set CMAKE_OSX_DEPLOYMENT_TARGET to the same value ("14.0"). The conditional logic is now redundant. To improve code clarity, you could remove the if/else block (lines 147-153) and replace it with a single set() command and an updated comment explaining why 14.0 is used.

@github-actions
Copy link

github-actions bot commented Jan 8, 2026

agent

Build: [##########.] 100% (Passed)
Tests: [##########.] 100% (Passed)
Quality: [#######...] 70% (3 issue(s))
Checks: [##########.] 100% (Passed)

Overall: Operational (92%)

@bniladridas bniladridas merged commit 249b373 into main Jan 8, 2026
20 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants