Skip to content

add MinGW/MSYS2 as compiling option #287

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

Closed
wants to merge 3 commits into from
Closed

Conversation

BJNFNE
Copy link
Contributor

@BJNFNE BJNFNE commented May 13, 2025

Summary by CodeRabbit

  • Documentation
    • Added instructions for building the project using MinGW/MSYS2, including package installation and build steps.

Copy link

coderabbitai bot commented May 13, 2025

Walkthrough

A new section was added to the build documentation, providing step-by-step instructions for building the project using MinGW/MSYS2. The instructions detail repository cloning, package installation, and the build process, aligning with guidance for other supported platforms.

Changes

File(s) Change Summary
docs/BUILD.md Added instructions for building the project with MinGW/MSYS2, including environment setup steps.

Possibly related PRs

  • Update Windows version #239: Updates Windows build instructions in the same documentation file, focusing on Windows version support and clarifying Visual Studio and Qt installation steps.

Poem

A new path for builders, with MinGW in hand,
MSYS2 guides us, through Windows' fair land.
Clone, install, and build with glee—
Qt and pacman, a recipe!
Now rabbits may hop, with docs up to date,
Our builds on Windows—oh, simply great!
🐇✨

Tip

⚡️ Faster reviews with caching
  • CodeRabbit now supports caching for code and dependencies, helping speed up reviews. This means quicker feedback, reduced wait times, and a smoother review experience overall. Cached data is encrypted and stored securely. This feature will be automatically enabled for all accounts on May 16th. To opt out, configure Review - Disable Cache at either the organization or repository level. If you prefer to disable all data retention across your organization, simply turn off the Data Retention setting under your Organization Settings.

Enjoy the performance boost—your workflow just got faster.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@BJNFNE BJNFNE marked this pull request as draft May 13, 2025 05:13
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (4)
docs/BUILD.md (4)

141-141: Standardize heading level for better hierarchy
The new section uses a top-level heading (#), matching other major build sections—but to improve document structure and accessibility, consider demoting it to a second-level heading (##). This avoids skipping levels when introducing subsections.

Proposed diff:

-# How to build with MinGW/MSYS2
+## How to build with MinGW/MSYS2

143-150: Fix subheading levels, remove trailing punctuation, and correct typo
Static analysis flags show heading levels jumping too far (h1→h4) and trailing colons. Align all subsections at one level deeper (e.g., ### under ##) and drop the colon. Also fix “libaries” → “libraries.”

Proposed diff:

-#### Clone this repo recursively:
+### Clone this repo recursively

-### Install libaries
+### Install libraries
🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

143-143: Heading levels should only increment by one level at a time
Expected: h2; Actual: h4

(MD001, heading-increment)


143-143: Trailing punctuation in heading
Punctuation: ':'

(MD026, no-trailing-punctuation)


153-155: Combine pacman installs and enable non-interactive mode
Running three separate pacman -S commands can be condensed; adding --needed --noconfirm avoids extra prompts.

Proposed diff:

-pacman -S mingw-w64-x86_64-qt5-base
-pacman -S mingw-w64-x86_64-qt5-tools
-pacman -S mingw-w64-x86_64-qt5-script
+pacman -S --needed --noconfirm \
+    mingw-w64-x86_64-qt5-base \
+    mingw-w64-x86_64-qt5-tools \
+    mingw-w64-x86_64-qt5-script

158-164: Clarify MSYS2 shell context before build
On Windows using MSYS2, users must open the correct MSYS2 MinGW shell (e.g., “MSYS2 MinGW 64-bit”) before running ./configure and make. Otherwise, the Qt packages won’t be found.

Example note to add:

> **Note:** Launch the **MSYS2 MinGW 64-bit** shell before proceeding with the build steps below.
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between acb7bd1 and eabe23c.

📒 Files selected for processing (1)
  • docs/BUILD.md (1 hunks)
🧰 Additional context used
🪛 markdownlint-cli2 (0.17.2)
docs/BUILD.md

143-143: Heading levels should only increment by one level at a time
Expected: h2; Actual: h4

(MD001, heading-increment)


143-143: Trailing punctuation in heading
Punctuation: ':'

(MD026, no-trailing-punctuation)

@BJNFNE
Copy link
Contributor Author

BJNFNE commented May 13, 2025

@coderabbitai review

Copy link

coderabbitai bot commented May 13, 2025

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🔭 Outside diff range comments (1)
docs/BUILD.md (1)

169-193: 🛠️ Refactor suggestion

⚠️ Potential issue

Remove duplicated MinGW/MSYS2 section
The "How to build with MinGW/MSYS2" section is duplicated, causing confusion (MD024). Consolidate into a single section by removing the duplicate block:

@@ -169,25 +169,6 @@
-# How to build with MinGW/MSYS2
-
-#### Clone this repo recursively:
-
-```bash
-git clone --recursive https://github.com/horsicq/DIE-engine.git
-cd DIE-engine
-```
-
-### Install libaries
-
-```bash
-pacman -S mingw-w64-x86_64-qt5-base
-pacman -S mingw-w64-x86_64-qt5-tools
-pacman -S mingw-w64-x86_64-qt5-script
-```
-
-#### Build
-
-```bash
-chmod a+x configure
-./configure
-make -j4
-```
🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

169-169: Multiple headings with the same content
null

(MD024, no-duplicate-heading)


171-171: Heading levels should only increment by one level at a time
Expected: h2; Actual: h4

(MD001, heading-increment)


171-171: Trailing punctuation in heading
Punctuation: ':'

(MD026, no-trailing-punctuation)

🧹 Nitpick comments (1)
docs/BUILD.md (1)

143-143: Convert bare URL to a Markdown link
Using a bare URL can trigger MD034. Wrap the MSYS2 URL in link syntax to improve readability and satisfy lint rules.
Apply this diff:

-Install MSYS2: https://www.msys2.org/
+Install MSYS2: [MSYS2 website](https://www.msys2.org/)
🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

143-143: Bare URL used
null

(MD034, no-bare-urls)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between eabe23c and bc68ebf.

📒 Files selected for processing (1)
  • docs/BUILD.md (1 hunks)
🧰 Additional context used
🪛 markdownlint-cli2 (0.17.2)
docs/BUILD.md

143-143: Bare URL used
null

(MD034, no-bare-urls)


145-145: Heading levels should only increment by one level at a time
Expected: h2; Actual: h4

(MD001, heading-increment)


145-145: Trailing punctuation in heading
Punctuation: ':'

(MD026, no-trailing-punctuation)


169-169: Multiple headings with the same content
null

(MD024, no-duplicate-heading)


171-171: Heading levels should only increment by one level at a time
Expected: h2; Actual: h4

(MD001, heading-increment)


171-171: Trailing punctuation in heading
Punctuation: ':'

(MD026, no-trailing-punctuation)


Install MSYS2: https://www.msys2.org/

#### Clone this repo recursively:
Copy link

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

Normalize heading level and remove trailing colon
Jumping from an H1 (# How to build…) to an H4 (#### Clone…:) violates MD001, and trailing punctuation violates MD026. Use a consistent level (H2) and drop the colon:

-#### Clone this repo recursively:
+## Clone this repo recursively
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
#### Clone this repo recursively:
## Clone this repo recursively
🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

145-145: Heading levels should only increment by one level at a time
Expected: h2; Actual: h4

(MD001, heading-increment)


145-145: Trailing punctuation in heading
Punctuation: ':'

(MD026, no-trailing-punctuation)

@BJNFNE
Copy link
Contributor Author

BJNFNE commented May 13, 2025

Closing in favour of #288

@BJNFNE BJNFNE closed this May 13, 2025
@BJNFNE BJNFNE deleted the msys2 branch May 13, 2025 07:30
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