Make sure all board build regenerate oldconfig and defconfig to track changes in each modules requiring a config

未关闭
#2,238 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
38/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
linux

调研方向

Start by reading the board build rules and the coreboot.save_in_defconfig_format_backup recipe shown in the issue, then inspect how module configurations under config/* are handled. Determine which modules can reliably regenerate defconfigs during board builds; done means the selected configurations are regenerated automatically so developers can compare board deviations.

由索引模型根据 Issue 内容生成。

描述

We want to make sure that coreboot defconfig and oldconfig are regenerated for coreboot (and Linux?) but also for other modules which we track config under config/* (busybox and others)

It is known that regenerating oldconfigs embedds some versionning info so maybe make sure we generate at least defconfigs for everything we can

Ie

./docker_repro.sh make BOARD=EOL_x280-maximized coreboot.save_in_defconfig_format_backup

Should be done automatically so any devs can see deviations from default

Maybe just recipe for coreboot which is the minimal needed to be able to compare boards against each other and report discrepancies upstream.

主要语言
Makefile
星标
1.6k
派生
215
平均合并
4 天 5 小时
30 天内合并 PR
14

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

linuxboot/heads 的其他 Issue

查看 linuxboot/heads 的全部 Issue

相似的 Issue

更多 Build System Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。