KhronosGroup / KhronosGroup/OpenXR-SDK-Source
Banish MAX_PATH limit
- Dominant language
- Python
- Stars
- 825
- Forks
- 306
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 1
Description
> We can use a bigger number, but many parts of windows use MAX_PATH so it is a bit of an unfortunate de-facto limit in Windows. Another option is to use PathCchCanonicalizeEx and dynamically allocate the buffer to the length needed. What I did was a bit of a lazy but common pattern in Windows programming.
_Originally posted by @brycehutchings in https://github.com/KhronosGroup/OpenXR-SDK-Source/pull/198_
Contributor guide
No contributing guide indexed for this repository
Research direction
Read the MAX_PATH discussion quoted from pull request 198, including the tradeoff between a larger fixed buffer and PathCchCanonicalizeEx with dynamic allocation. Determine the affected Windows path handling and define done as supporting paths beyond MAX_PATH without relying on a fixed buffer.
Written by the indexing model from the issue text.
Assessment
- Domain
- operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100