On 11/05/2022 09:57, Soft Works wrote:
[...] I'm not sure how much you had followed, so please excuse in case you had already read it: the manifest approach does not work on a default Windows installation. To activate long path support, the users needs to opt-in to a behavior that is probably deactivated by default for some reason. Also it requires administrative privileges to make this change. For me - and probably for others as well - that approach is useless, as it would be the same as if there would be no long path support. (when you cannot rely on that feature being always working, you cannot use it)
For me an analogous case is the usage of the "--large-address-aware" linker flag. It enables FFmpeg to use more than 2GiB of memory on Win32. That feature is useless to users having <= 2GiB of total system memory available, and it makes no guarantee that an OOM error is avoided. Still it allows to exceed a limit for those that match the requirements -- knowingly or by pure coincidence.
Regards, Tobias _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
