Skip to content

Add windows long path support function #118

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Nov 1, 2019
Merged

Conversation

Larusso
Copy link
Owner

@Larusso Larusso commented Nov 1, 2019

Description

To activate support for long path names I added a utility function which can be used to prepend a given path with a specific opt in prefix \\?\ From the windows docs:

For file I/O, the "\?" prefix to a path string tells the Windows APIs to disable all string parsing and to send the string that follows it straight to the file system. For example, if the file system supports large paths and file names, you can exceed the MAX_PATH limits that are otherwise enforced by the Windows APIs. For more information about the normal maximum path limitation, see the previous section Maximum Path Length Limitation.

More info can be found here

The windows installer functions call this new utility function and prefix all destination urls.

Changes

  • ADD WINDOWS long path support

@Larusso Larusso added this to the Unity Hub install parity milestone Nov 1, 2019
@Larusso Larusso self-assigned this Nov 1, 2019
@Larusso Larusso force-pushed the add/long_pathname_support branch from df0ff44 to bbd38d9 Compare November 1, 2019 14:39
Description
============

To activate support for long path names I added a utility function which
can be used to prepend a given path with a specific opt in prefix `\\?\`
From the windows [docs][0]:

> For file I/O, the "\\?\" prefix to a path string tells the Windows APIs
> to disable all string parsing and to send the string that follows it
> straight to the file system. For example, if the file system supports
> large paths and file names, you can exceed the MAX_PATH limits that
> are otherwise enforced by the Windows APIs. For more information
> about the normal maximum path limitation, see the previous section
> Maximum Path Length Limitation.

More info can be found [here][0]

The windows installer functions call this new utility function and
prefix all destination urls.

Changes
=======

* ![ADD] ![WINDOWS] long path support

[0]: https://docs.microsoft.com/en-us/windows/win32/fileio/naming-a-file#maximum-path-length-limitation
@Larusso Larusso force-pushed the add/long_pathname_support branch from bbd38d9 to a76a2dd Compare November 1, 2019 17:25
@Larusso Larusso merged commit f7f05c2 into master Nov 1, 2019
@Larusso Larusso deleted the add/long_pathname_support branch November 1, 2019 19:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant