oneapi-src / oneapi-src/level-zero
[Feature Request]: Consistent include directory when used as subproject or installed
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 335
- Forks
- 140
- Avg merge
- 12h 32m
- Merged PRs (30d)
- 5
Description
It is quite popular in CMake projects to depend on an upstream project by including it into the build system of the dependent project, for example using FetchContent.
Unfortunately if consumed like this, the recommended way of including the header files from the project can't work:
#include <level_zero/ze_api.h> // Can't work, the include folder does not have a parent named level_zero
Related to: #57
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 reviewing the CMake configuration and the include-directory layout used when Level Zero is consumed through FetchContent versus installed. Confirm how the headers are exposed in each mode. Done means consumers can use the documented <level_zero/ze_api.h> include consistently in both cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cmake, cpp
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100