bazel-contrib / bazel-contrib/rules_devicetree
Support arbitrary preprocessor
Closed
- Dominant language
- Starlark
- Stars
- 6
- Forks
- 3
- Avg merge
- 6d 9h
- Merged PRs (30d)
- 9
Description
Right now, we rely on `ACTION_NAMES.preprocess_assemble` for the preprocessor. We should support arbitrary preprocessor because `preprocess_assemble` is not perfect; it might be resolved to DUMMY_GCC_TOOL if there is no action config for it.
Contributor guide
Research direction
Start by tracing uses of ACTION_NAMES.preprocess_assemble and the resolution path that can produce DUMMY_GCC_TOOL when no action config exists. Determine the supported preprocessor configuration entry point and verify that an arbitrary preprocessor can be selected without falling back to the dummy tool.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100