oneapi-src / oneapi-src/unified-memory-framework
vcpkg hwloc + linking it statically makes it install hwloc files among umf
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 98
- Forks
- 48
- Avg merge
- 3d 20h
- Merged PRs (30d)
- 6
Description
When hwloc is installed on Windows via vcpkg and we enable UMF_LINK_HWLOC_STATICALLY=ON hwloc files (headers, etc.) are installed along our library.
Reproduction steps:
vcpkg install # all dependencies defined in our repo will be installed
mkdir build && cd build
cmake .. -DUMF_LINK_HWLOC_STATICALLY=ON
make install
We should check if this is an issue in our installation steps or perhaps missing a flag in vcpkg installation of hwloc or... something else 😉
Priority: low
// found on my testing branch
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 with the vcpkg dependency installation and the CMake configuration using UMF_LINK_HWLOC_STATICALLY=ON, then follow the make install step on Windows. Check which hwloc headers and other files are copied into the UMF installation and determine whether the installation rules or dependency configuration causes them to be included. Done means a static hwloc build installs UMF without unintended hwloc files.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, cmake
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100