SFTtech/openage

Allow easy usage of different compiler versions in the buildsystem

Open

#1,253 opened on 2020年5月4日

GitHub で見る
 (1 comment) (0 reactions) (0 assignees)Python (12,130 stars) (1,135 forks)batch import
area: buildsystemgood first issueimprovement

説明

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

コントリビューターガイド

技術スタック
pythoncpp
領域
build systemdeveloper experience
Issue 種別
feature
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
3
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
half day
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
stale
明確さ期待される変更、受け入れ条件、次の手順がどれだけ明確かを示します。
clear
前提条件
Python scriptingBuild system knowledgeC++ compiler basics
初心者向け度初回貢献者にどれだけ取り組みやすいかを 1-100 で推定したスコアです。
70
調査方針
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.