> Again, you have deleted my asking for an example scenario > and which library would need to be loaded from a long path.
Because I don't think that an example would be relevant. Generic library function must be able to load a library, no matter the location. You're talking as if MAX_PATH limited library loader is self-evidently superior, and it is the loader that has no such limitation that has to justify its existence. As far as I'm concerned it just the other way around. > For the longpaths attribute, you could surely argue that it's "just" > that you don't know whether it will work or not. > But forcing a different code page for a process _IS_ a fundamental > alteration. Which is necessary for compatibility with AviSynth, and commit message says exactly that: https://ffmpeg.org/pipermail/ffmpeg-devel/2022-April/295572.html. > I'm restoring the line of your own question which you have deleted: > > > > > Is it a big deal to change a registry and reboot? > My response to that was: > ... > Really? I answer your question and then you delete your question > and ask what my answer would have to do with the patchset? Sorry, I should've directly asked what: > 3. A registry key or group policy needs to be set on Windows to enable this > ´ (in both cases, administrative permission/UAC is required to set it) > 4. Even when registry key or group policy is set, it might still be pending > a reboot has to do with this patchset, instead of asking a rhetorical question of whether it's a big deal or not. _______________________________________________ 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".
