Windows - Long Path Support (260 chars)
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 3.3k
- Forks
- 808
- PR merge metrics
- No merged PRs in 30d
Description
Currently, if input/output paths for opusenc are too long or Windows, opusenc is not able to find the file reporting error:
No such file or directory
This seems to be due to lack of support for long paths.
Would it be possible to fix this for Windows builds?
Similiar issues:
https://trac.ffmpeg.org/ticket/8885
https://github.com/staxrip/staxrip/issues/226
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 with the opusenc entry point and the Windows build configuration, then reproduce the failure using input and output paths longer than 260 characters. Trace how those paths are passed to file operations; done means Windows builds can locate and create files with long paths without the reported error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- audio-video-rtc
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100