RT-Thread / RT-Thread/rt-thread
[Feature] 规范CPPPATH的使用
Open
Nobody has claimed this yet.
good first issue
- Dominant language
- C
- Stars
- 12.2k
- Forks
- 5.4k
- Avg merge
- 4d 12h
- Merged PRs (30d)
- 40
Description
Describe problem solved by the proposed feature
很多组件或者模块都将自身所在路径通过SConscript添加到了CPPPATH中，然后在编译时将这些路径都包含进来了，非常容易污染路径，不光软件包有这些问题，内核组件也是这样，项目大起来之后，非常容易冲突，目前已有的组件或者模块很难动了，先保证老代码兼容性，但是如果后续还有需要新增的组件，建议好好考虑怎么组织一下，不要再污染路径了。
Describe your preferred solution
No response
Describe possible alternatives
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the SConscript files that add component and kernel paths to CPPPATH, and review how existing modules depend on those paths. The scope is not yet defined; done would require an agreed organization that avoids new path pollution while preserving compatibility with legacy code.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- build-system, embedded-iot
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100