add winos.file_signature function to retrieve file signature information#7333
add winos.file_signature function to retrieve file signature information#7333waruqi merged 60 commits intoxmake-io:devfrom
Conversation
…fullpath as file_signature would not work without full path provided
Added reference to GitHub issue regarding GIGA-BYTE signed gcc.exe.
Summary of ChangesHello @luadebug, 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 Xmake's Windows compatibility and robustness by integrating digital file signature verification. The primary goal is to prevent potential issues arising from specific Highlights
🧠 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. Changelog
Using Gemini Code AssistThe 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
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 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
|
|
@waruqi LGTM |
There was a problem hiding this comment.
Code Review
This pull request introduces a file signature verification feature for Windows and uses it to address an issue with a non-standard gcc.exe provided by Gigabyte. The overall implementation is good, but I've identified a couple of areas for improvement: a logic bug in the GCC detection script that could lead to incorrect results, and some dead code in the new C file for signature checking. My review includes specific suggestions to fix these issues.

Attempt to continue working on #7326 as I accidentally broke branch :(
TODO that still does not work.
Moved here from tboox/tbox#308
Resolves: #5629
Idea is that we can check for signature owner name GIGA-BYTE ... and if that is it and executable name is GCC.exe we should skip/filter out that .exe from find_tool("gcc")/find_gcc function at that case.
Currently I see:

Certainly mine wrapper over find_gcc/find_tool might be not correct... :/
Yet they should return void or either another GCC.exe. Maybe this would work or maybe not.