-
Notifications
You must be signed in to change notification settings - Fork 13
Dev #195
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
Conversation
Summary of ChangesHello @gameknife, 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 introduces a new batch script to simplify the execution of the PowerShell-based build process on Windows command prompts, improving developer experience. Concurrently, it reflects significant progress in addressing multi-platform build system challenges by updating the project plan to show several GitHub Actions workflow fixes as completed. 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. Ignored Files
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
|
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 a build.bat script to wrap the PowerShell build script, making it easier to run from a standard command prompt. It also updates a planning document. The new batch script is a good addition for convenience. My review includes a suggestion to make the argument parsing in build.bat more robust to prevent silently ignoring invalid options.
| ) else ( | ||
| REM Assuming the first non-flag argument is the target | ||
| if /i "%~1"=="windows" ( | ||
| set "TARGET=windows-dev" | ||
| ) else ( | ||
| set "TARGET=%~1" | ||
| ) | ||
| ) |
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.
The argument parsing logic could be more robust. Currently, any unrecognized argument (e.g., a mistyped flag like --cleen) is treated as a target. If another valid target is specified later, the invalid flag is silently ignored. This can hide errors and lead to unexpected build configurations.
I suggest adding a check to explicitly reject unknown flags (those starting with --). This will make the script fail fast and provide clearer error messages.
) else (
if "%~1:~0,2%"=="--" (
echo Unrecognized option: %~1 >&2
exit /b 1
)
REM Assuming the non-flag argument is the target
if /i "%~1"=="windows" (
set "TARGET=windows-dev"
) else (
set "TARGET=%~1"
)
)
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.
Pull request overview
This pull request fixes multi-platform build system issues by standardizing build target arguments across GitHub Actions workflows and adding a Windows batch wrapper script. The changes ensure that platform-specific build presets from CMakePresets.json are used correctly in CI pipelines.
Key Changes:
- Updated CI workflows to use explicit build targets (
macos-arm64,linux-release) instead of generic platform names - Added
build.batwrapper script for Windows to simplify command-line builds with proper argument handling - Marked Phase 1 tasks as completed in the project plan
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| conductor/tracks/fix_multiplatform_build_20251231/plan.md | Updated task completion status for Phase 1, marking all GitHub Actions workflow fixes as complete with commit references |
| build.bat | New Windows batch script that wraps build.ps1, providing convenient argument parsing for targets like windows, android, and --clean |
| .github/workflows/macos.yml | Changed build target from macos to macos-arm64 to match the specific CMake preset for ARM64 architecture |
| .github/workflows/linux.yml | Changed build target from linux to linux-release to match the specific CMake preset for release builds |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
…fication' as complete
…omplete (no changes needed)
…fication' as complete
…ete (no changes needed)
…tion' as complete
No description provided.