Skip to content

(modules) strip embed-dir on clang / gcc#7349

Merged
waruqi merged 1 commit intoxmake-io:devfrom
Arthapz:add-embeddir-modules
Feb 26, 2026
Merged

(modules) strip embed-dir on clang / gcc#7349
waruqi merged 1 commit intoxmake-io:devfrom
Arthapz:add-embeddir-modules

Conversation

@Arthapz
Copy link
Member

@Arthapz Arthapz commented Feb 25, 2026

  • Before adding new features and new modules, please go to issues to submit the relevant feature description first.
  • Write good commit messages and use the same coding conventions as the rest of the project.
  • Please commit code to dev branch and we will merge into master branch in feature
  • Ensure your edited codes with four spaces instead of TAB.

  • 增加新特性和新模块之前,请先到issues提交相关特性说明,经过讨论评估确认后,再进行相应的代码提交,避免做无用工作。
  • 编写友好可读的提交信息,并使用与工程代码相同的代码规范,代码请用4个空格字符代替tab缩进。
  • 请提交代码到dev分支,如果通过,我们会在特定时间合并到master分支上。
  • 为了规范化提交日志的格式,commit消息,不要用中文,请用英文描述。

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @Arthapz, 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 xmake build tool by adding the ability to strip the embed-dir compiler flag, improving security by preventing sensitive directory information from being embedded in the compiled output. It also refines the flag stripping logic to handle different flag prefixes, ensuring more comprehensive flag removal.

Highlights

  • Compiler Flag Stripping: This PR modifies the xmake build tool to strip the embed-dir flag from compiler flags for both Clang and GCC. This ensures that the flag, which might contain sensitive information, is not included in the final build.
  • Flag Matching: The PR updates the flag stripping logic to correctly identify and remove flags that start with /, --, or -, enhancing the tool's ability to sanitize compiler flags.

🧠 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.

Activity
  • The pull request was created by Arthapz.
  • The pull request targets the dev branch.
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 modifies the xmake build system to strip the embed-dir flag from compiler flags when generating module build information (BMI) for both clang and gcc. It also adds support for stripping flags with double dashes (--) in addition to single dashes (-).

Comment on lines 122 to +123
splitted_strippeable_flags_set:insert("/" .. flag)
splitted_strippeable_flags_set:insert("--" .. flag)
Copy link
Contributor

Choose a reason for hiding this comment

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

high

high: Adding -- prefix support is crucial for handling compiler flags that use this notation. Failing to do so will result in flags not being stripped correctly, potentially leading to build errors or inconsistencies.

        table.insert(strippeable_flags, flag)
        splitted_strippeable_flags_set:insert("/" .. flag)
        splitted_strippeable_flags_set:insert("--" .. flag)

Comment on lines 140 to +141
break
elseif flag:startswith("/" .. _flag) or flag:startswith("-" .. _flag) then
elseif flag:startswith("/" .. _flag) or flag:startswith("--" .. _flag) or flag:startswith("-" .. _flag) then
Copy link
Contributor

Choose a reason for hiding this comment

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

high

high: Adding -- prefix support is crucial for handling compiler flags that use this notation. Failing to do so will result in flags not being stripped correctly, potentially leading to build errors or inconsistencies.

                elseif flag:startswith("/" .. _flag) or flag:startswith("--" .. _flag) or flag:startswith("-" .. _flag) then

@waruqi waruqi merged commit c6811ca into xmake-io:dev Feb 26, 2026
37 checks passed
@waruqi waruqi added this to the v3.0.8 milestone Feb 26, 2026
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