-
Notifications
You must be signed in to change notification settings - Fork 416
RHEL-104117: Add infrastructure for cab file creation #1400
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Summary of Changes
Hello @elizashurov, 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!
I've implemented the foundational infrastructure required for creating cabinet (.cab) files. This work involves adding a new dedicated build script, integrating it into the existing main build system, and defining the contents of the cabinet files through new Diamond Directive Files (.ddf) for various Windows platforms and architectures. This change streamlines the packaging of driver components.
Highlights
- New Cabinet File Build Script: I've introduced a new batch script, "build_cab.bat", specifically designed to automate the creation of cabinet (.cab) files for various Windows versions and architectures.
- Automated CAB File Generation: The new "build_cab.bat" script has been integrated into the existing "buildAll.bat" process, ensuring that cabinet files are automatically generated as part of the main build workflow.
- Comprehensive DDF File Definitions: I've added several Diamond Directive Files (.ddf) for Windows 10 and 11 across ARM64, x64, and x86 architectures. These files specify the exact content and structure for each corresponding cabinet file.
- CI Trigger Updates: To prevent unnecessary continuous integration (CI) runs, I've updated the CI triggers to ignore changes to the newly added .ddf files.
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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command>
or @gemini-code-assist <command>
. Below is a summary of the supported commands.
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 issue 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 or fill out our survey to provide feedback.
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
-
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. ↩
[Jenkins CI]: Can one of the admins verify this patch? |
There was a problem hiding this 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 introduces the infrastructure for creating cabinet (.cab) files for the drivers. It adds a new build_cab.bat
script, several .ddf
configuration files for different target platforms, and integrates the new script into the main buildAll.bat
. The changes look good and implement the desired functionality. My review includes a few suggestions to improve the maintainability of the new scripts and configuration files, mainly concerning code duplication in the .ddf
files and some minor cleanups in the batch script.
683cf99
to
53c41f6
Compare
/gemini review |
There was a problem hiding this 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 adds the necessary infrastructure to create cabinet (.cab) files for various Windows versions and architectures. It introduces a new build_cab.bat
script and several .ddf
configuration files. The main build script buildAll.bat
is updated to call this new script. My review has identified a couple of minor maintainability issues: one regarding code style in the batch script and another concerning a potentially confusing component name in one of the .ddf
files. Overall, the changes are well-structured and achieve the goal described.
53c41f6
to
d956ed3
Compare
scapces fixed |
/gemini review |
There was a problem hiding this 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 introduces the infrastructure for creating cabinet (.cab
) files for various driver packages. The changes include a new build_cab.bat
script, several Diamond Directive Files (.ddf
), integration into the main buildAll.bat
script, and updates to the CI configuration. My review focuses on improving the maintainability of the newly added .ddf
files, which currently contain significant duplication and some commented-out code that could cause confusion. Addressing these points will make the new build infrastructure more robust and easier to manage in the long run.
;.Set DestinationDir=fwcfg | ||
;.\fwcfg64\Install\Win10\ARM64\fwcfg.cat | ||
;.\fwcfg64\Install\Win10\ARM64\fwcfg.inf | ||
;.\fwcfg64\Install\Win10\ARM64\fwcfg.pdb |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok to test |
This commit adds the build_cab.bat script and its corresponding .ddf files, integrates it into the main buildAll.bat script, and updates the hck-ci triggers to ignore the new ddf files. Signed-off-by: Elizabeth Ashurov <[email protected]>
d956ed3
to
c38bf30
Compare
re-run test |
This commit adds the build_cab.bat script and its corresponding .ddf files, integrates it into the main buildAll.bat script, and updates the hck-ci triggers to ignore the new ddf files.