asioexec configure_file should output to binary directory
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 2.4k
- Forks
- 270
- Avg merge
- 3d 6h
- Merged PRs (30d)
- 39
Description
set(ASIOEXEC_ASIO_CONFIG_FILE_PATH ${CMAKE_CURRENT_SOURCE_DIR}/include/asioexec)
configure_file(include/asioexec/asio_config.hpp.in ${ASIOEXEC_ASIO_CONFIG_FILE_PATH}/asio_config.hpp)
I think setting the output to ${CMAKE_CURRENT_BINARY_DIR}/stdexec_generated/include/asioexec and then added via target_include_directories(stdexec PUBLIC ${CMAKE_CURRENT_BINARY_DIR}/stdexec_generated/include) is the better way here.
Contributor guide
No contributing guide indexed for this repository
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 at the configure_file call in the linked commit diff and inspect how the generated asio_config.hpp path is added to the target include directories. Done means configuration writes the header under the binary directory, the generated include directory is exposed to stdexec, and the source tree is not modified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cmake, cpp
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 42/100