KhronosGroup / KhronosGroup/OpenCL-Docs
Use generated command prototypes and definitions in extension specification
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 421
- Forks
- 131
- Avg merge
- 5d 13h
- Merged PRs (30d)
- 11
Description
In the core specification, structures and function prototypes are generated from cl.xml and included as follows:
include::{generated}/api/protos/clCreateCommandQueueWithProperties.txt[]
In the extension specification, these are all spelled out manually. They should also be generated and included instead.
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 examining cl.xml and the extension specification's manually written command prototypes and definitions. Compare them with the generated include pattern used in the core specification, then verify that the extension specification uses generated includes instead and that its rendered output remains complete.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100