SFTtech/openage

Allow easy usage of different compiler versions in the buildsystem

Open

#1,253 创建于 2020年5月4日

在 GitHub 查看
 (1 评论) (0 反应) (0 负责人)Python (12,130 star) (1,135 fork)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
议题类型
feature
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
half day
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
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.