Fix binary build destination

[LiquidityC]

Summary by CodeRabbit

• Chores
  • Refined the installation process to deploy runtime files to appropriate directories based on the selected build configuration.

[coderabbitai]

Walkthrough

The changes modify the CMakeLists.txt file to update the installation commands for the project target. A conditional branch based on the STEAM variable determines the runtime destination. When STEAM is defined, the runtime is installed in the current directory (.); otherwise, it is installed in the bin/ directory. This update removes the original installation command and introduces a new conditional structure for installation paths.

Changes

File	Change Summary
CMakeLists.txt	Updated installation commands: when STEAM is defined, set runtime destination to .; if not, use bin/.

Sequence Diagram(s)

sequenceDiagram
    participant C as CMake
    participant I as Installer
    Note over C: Evaluate STEAM condition
    alt STEAM is defined
        C->>I: Set runtime destination to "."
    else STEAM is not defined
        C->>I: Set runtime destination to "bin/"
    end

Loading

Poem

I'm a bunny coder hopping through change,
Adjusting CMake paths, not out of range.
When STEAM is on, I set my course to ".",
Else, "bin/" is where the artifacts are born.
With floppy ears and a keyboard cheer,
I celebrate updates with a joyful beer! 🐰
Hoppy builds echo far and near!

---

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

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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.
  • Generate unit testing code for this file.
  • 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 generate unit testing code for this file.
  • @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 generate unit testing code.
  • @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.

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 resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @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.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (2)

CMakeLists.txt (2)

325-334: Clarify Installation Destination for Non-Steam Builds

In this block, the TARGET is installed with a runtime destination of bin/ and the asset files/directories are placed under share/breakhack/. This clearly distinguishes the non-Steam build installation layout.

It might be beneficial to add an inline comment briefly explaining why these particular destinations were chosen to enhance maintainability.

---

339-353: Correct Binary Installation Destination for Steam Builds

The changes in the else () block correctly update the installation commands such that when STEAM is enabled, the target as well as the asset files and directories are installed to the current directory (.). This aligns with the PR objective of fixing the binary build destination for Steam builds.

Consider adding a short comment indicating that this change ensures the Steam builds deploy binaries and related files in the working directory, which might help future maintainers understand the rationale.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 1c65461 and ef16aaf.

📒 Files selected for processing (1)

• CMakeLists.txt (2 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (11)

• GitHub Check: build (ubuntu-latest, Release, gcc)
• GitHub Check: build (macos-latest, Release, clang)
• GitHub Check: build (macos-latest, Debug, clang)
• GitHub Check: build (macos-latest, Debug, gcc)
• GitHub Check: build (macos-latest, Release, gcc)
• GitHub Check: build (ubuntu-latest, Debug, gcc)
• GitHub Check: build (ubuntu-latest, Release, mingw-w64-gcc)
• GitHub Check: build (ubuntu-latest, Release, clang)
• GitHub Check: build (ubuntu-latest, Debug, clang)
• GitHub Check: build (ubuntu-latest, Debug, mingw-w64-gcc)
• GitHub Check: Analyze (c-cpp)