oneapi-src / oneapi-src/unified-memory-framework
Limiting symbol visibility on macos
Open
Nobody has claimed this yet.
question
- Dominant language
- C
- Stars
- 98
- Forks
- 48
- Avg merge
- 3d 20h
- Merged PRs (30d)
- 6
Description
Figure out if there is a way (and whether it's needed) to limit symbol visibility when building a shared library on MacOS (similarly to what we're doing on linux with --version-script).
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 comparing the existing Linux shared-library build and its --version-script configuration with the macOS build settings. Determine whether limiting exported symbols is needed and identify a concrete macOS approach; document the conclusion and any required implementation scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, macos
- Domain
- build-system, operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100