|
|
- There is some usage of GetCurrentDirectory, GetFullPathName and GetLongPathName with a fixed array size of 2048 in unrar; this can probably be ignored, we don't extract to disk
We do use MAX_PATH in various other places but from what I can see, they are all limited by the usage of Shell functions, which are still limited to MAX_PATH even when declaring this manifest entry. Sadly even the COM counterparts of some shell functions exhibit the same limitations.
From that perspective, it should be safe to turn on this feature. |
|
|
|
For future development, we should also review how std::filesystem handles long path names:
- is it compatible with long path awareness?
- does it prepend
\\?\ to long paths where necessary? if not, we should probably report this as a bug.
|
|
|
|
is it compatible with long path awareness?
probably
does it prepend \?\ to long paths where necessary? if not, we should probably report this as a bug.
it does not |
|
|
|
According to documentation long-path-awareness depends on a registry setting. Are we aware whether any known Windows version actually sets this registry setting, or is this purely a user setting for now?
In the latter case, I see little use in enabling support. |
|
|
|
IFF some Windows 10 version automatically sets the registry key, we might add the manifest for builds requiring this particular Windows 10 version and remove \\?\prefixing from this build completely. Otherwise, long-path-awareness does little but introduce another run-time variable that requires testing. |
|
