Skip to content

Conversation

@Du-Brandon
Copy link

Cmake4.1.0已不再支援SDL2的cmakelist(3.0.0),因此我新增了一個判斷,若不符合則退版。

Cmake4.1.0已不再支援SDL2的cmakelist(3.0.0),因此我新增了一個判斷,若不符合則退版
更正版,上一版commit到我自己的版本了,此版才是正確的
@github-actions
Copy link
Contributor

clang-tidy review says "All clean, LGTM! 👍"

Copy link
Member

@NOOBDY NOOBDY left a comment

Choose a reason for hiding this comment

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

why does the diff look like this? is there something wrong w/ the linebreak or something?

@Du-Brandon
Copy link
Author

why does the diff look like this? is there something wrong w/ the linebreak or something?

我今天使用CMAKE(version 4.1.0)建置時會出現錯誤,上面的提示是寫說4.1.0已不再支援3.5.0以下的cmake(SDL2的cmakelist 要求的版本是3.0.0),所以我新增了一個判斷是當版本為4.0.0以上時退版成3.5.0

@Dragonfly911117
Copy link
Member

Dragonfly911117 commented Aug 18, 2025

why does the diff look like this? is there something wrong w/ the linebreak or something?

我今天使用CMAKE(version 4.1.0)建置時會出現錯誤,上面的提示是寫說4.1.0已不再支援3.5.0以下的cmake(SDL2的cmakelist 要求的版本是3.0.0),所以我新增了一個判斷是當版本為4.0.0以上時退版成3.5.0

我覺得他指的是你的 CMakeLists.txt 的 diff 看起來有 tab/space 或 CRLF 問題
image

@Du-Brandon
Copy link
Author

why does the diff look like this? is there something wrong w/ the linebreak or something?

我今天使用CMAKE(version 4.1.0)建置時會出現錯誤,上面的提示是寫說4.1.0已不再支援3.5.0以下的cmake(SDL2的cmakelist 要求的版本是3.0.0),所以我新增了一個判斷是當版本為4.0.0以上時退版成3.5.0

我覺得他指的是你的 CMakeLists.txt 的 diff 看起來有 tab/space 或 CRLF 問題

image

我回去確認一下,可能是編碼的問題。

@github-project-automation github-project-automation bot moved this from 🆕 Backlog to 📋 Todo in New Game Framework Aug 18, 2025
@Dragonfly911117
Copy link
Member

Please also address and fix the sussy diff issue.

更正版本+刪除註解
@github-actions
Copy link
Contributor

clang-tidy review says "All clean, LGTM! 👍"

@github-actions
Copy link
Contributor

clang-tidy review says "All clean, LGTM! 👍"

@Du-Brandon
Copy link
Author

我更正了大部分的錯誤,但換行導致的問題我無法解決

Copilot AI and others added 3 commits August 20, 2025 08:17
@github-actions
Copy link
Contributor

clang-tidy review says "All clean, LGTM! 👍"

@github-actions
Copy link
Contributor

clang-tidy review says "All clean, LGTM! 👍"

@sonarqubecloud
Copy link

@github-actions
Copy link
Contributor

clang-tidy review says "All clean, LGTM! 👍"

Dragonfly911117
Dragonfly911117 previously approved these changes Sep 1, 2025
Copy link
Member

@Dragonfly911117 Dragonfly911117 left a comment

Choose a reason for hiding this comment

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

IWOMM.
CMake 4.1.1
GarudaLinux

Copy link

Copilot AI left a 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 PR addresses a compatibility issue between CMake 4.1.0 and SDL2's CMakeLists (3.0.0) by adding version checks and policy configurations to ensure backward compatibility.

  • Adds CMake version detection for versions 4.0 and above
  • Sets policy CMP0000 to NEW for newer CMake versions
  • Establishes minimum policy version to 3.5

Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.

@ntut-open-source-club ntut-open-source-club deleted a comment from Copilot AI Sep 1, 2025
@ntut-open-source-club ntut-open-source-club deleted a comment from Copilot AI Sep 1, 2025
@Dragonfly911117 Dragonfly911117 dismissed their stale review September 1, 2025 14:36

Wait, it doesn't seem like it was your script make it runnable. Taking a deep look, please hold on.

@Dragonfly911117
Copy link
Member

Dragonfly911117 commented Sep 1, 2025

why does the diff look like this? is there something wrong w/ the linebreak or something?

我今天使用CMAKE(version 4.1.0)建置時會出現錯誤,上面的提示是寫說4.1.0已不再支援3.5.0以下的cmake(SDL2的cmakelist 要求的版本是3.0.0),所以我新增了一個判斷是當版本為4.0.0以上時退版成3.5.0

可以請你提供 CMake 4.1.0 以上不再支援的文件或是你跑失敗的 Log 嗎?我這邊用 CMake 4.1.1 版本用 2866935 可以成功架好環境

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: 📋 Todo

Development

Successfully merging this pull request may close these issues.

3 participants