SFTtech/openage

Allow easy usage of different compiler versions in the buildsystem

已關閉

#1,253 建立於 2020年5月4日

在 GitHub 查看
 (1 則留言) (0 個反應) (0 位負責人)Python (1,135 個分叉)batch import
area: buildsystemgood first issueimprovement

倉庫指標

星標
 (12,130 顆星)
PR 合併指標
 (平均合併 9天 23小時) (30 天內合併 1 個 PR)

描述

Right now we can not easily set a compile and a version within our configure script. #1250 did a small fix for clang-9 and clang-10 because we needed that for the CI. But it would be nice to create some parser that "respects the versions making it easier to test for multiple compiler versions" (@TheJJ ).

Regarding:

This should be just a small fix, we should probably implement something that splits compiler into compiler-name and compiler-version => if it's clang and then append the version to clang++.

Originally posted by @simonsan in https://github.com/SFTtech/openage/pull/1250

And yes, the compiler-name-and-version parser would be the real fix. But, if we implement it, the version should actually be respected, since that way you may test multiple compiler versions easily.

Originally posted by @TheJJ in https://github.com/SFTtech/openage/pull/1250

貢獻者指南

研究方向
Examine the configure script (likely in the buildsystem directory) and the changes from PR #1250 to understand how compiler versions are currently handled. Implement a parser that splits the compiler string into name and version, then uses the version to select the appropriate compiler binary (e.g., clang++ 10). Ensure the parser respects the version to allow testing multiple compiler versions. Review the discussion in the linked PR for further context.
技術棧
pythoncpp
領域
build systemdeveloper experience
議題類型
功能
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
半天
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
較久未更新
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
清晰
前置要求
Python scriptingBuild system knowledgeC++ compiler basics
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
70