Skip to content

add target flags only for cross-compilation#7280

Merged
waruqi merged 3 commits intodevfrom
llvm
Feb 2, 2026
Merged

add target flags only for cross-compilation#7280
waruqi merged 3 commits intodevfrom
llvm

Conversation

@waruqi
Copy link
Member

@waruqi waruqi commented Jan 30, 2026

@waruqi waruqi added this to the v3.0.7 milestone Jan 30, 2026
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @waruqi, 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 enhances the robustness and clarity of Xmake's cross-compilation handling. It introduces a more granular distinction between a toolchain's inherent cross-compiling capability and the actual act of cross-compiling for a target platform. This improvement ensures that compiler-specific target flags, particularly for Clang and LLVM, are only injected into the build process when genuinely required for cross-compilation, thereby optimizing build configurations and preventing potential conflicts in native build environments.

Highlights

  • Refactored Cross-Compilation Detection: The logic for identifying cross-compilation has been refined by introducing a new is_cross_toolchain() method and updating the existing is_cross() method to provide a more precise and centralized check.
  • Conditional Target Flag Application: Target-specific flags for Clang and LLVM toolchains are now applied only when a cross-compilation context is detected, preventing their unnecessary inclusion during native builds.
  • Centralized Cross-Compilation Checks: Several toolchain configurations (Kotlin-Native, Zig) have been updated to utilize the new, unified toolchain:is_cross() method for determining cross-compilation status.

🧠 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 addresses the issue of adding target flags unnecessarily for native builds. The refactoring of is_cross into is_cross and is_cross_toolchain improves the clarity and correctness of the cross-compilation detection logic. The changes are applied consistently across all relevant toolchain files. I've included a couple of minor suggestions to improve code conciseness and maintainability.

@waruqi waruqi merged commit a024977 into dev Feb 2, 2026
71 of 73 checks passed
@waruqi waruqi deleted the llvm branch February 2, 2026 01:35
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.

1 participant