Re: [Lazarus] Long paths manifest
https://bugs.freepascal.org/view.php?id=34573 my attempt. I'm not sure about correct place of XML option. I did it like this page shows: https://gist.github.com/riverar/196d5aa6bb53bbdfb50beb323d0709df . So pls check it in work. AT -- ___ lazarus mailing list lazarus@lists.lazarus-ide.org https://lists.lazarus-ide.org/listinfo/lazarus
Re: [Lazarus] Long paths manifest
On 20.11.2018 1:17, Denis Kozlov via lazarus wrote: Any thoughts on integrating I'm making the patch. I dont know on which XML level to insert new XML part - inside or out of it in the root? xmlns:ws2="http://schemas.microsoft.com/SMI/2016/WindowsSettings";> true -- Regards, Alexey -- ___ lazarus mailing list lazarus@lists.lazarus-ide.org https://lists.lazarus-ide.org/listinfo/lazarus
Re: [Lazarus] Long paths manifest
Any thoughts on integrating the long paths manifest into Lazarus as a project option? On 13/11/2018 07:49, Denis Kozlov wrote: Hello, Windows API is capable of working with extended-length path for a maximum total path length of 32,767 characters, thus, overcoming the infamous 260 characters path limitation (a.k.a. MAX_PATH). To specify an extended-length path, use the "\\?\" prefix. For example, "\\?\C:\Very\Long\Path". According to Windows Docs, one can enable the new long path behavior per app via the manifest: - xmlns:ws2="http://schemas.microsoft.com/SMI/2016/WindowsSettings";> true - Has anyone had any experience with embedding such manifest? What would be the best way to add such a manifest to an application, currently? Perhaps this could be added as an option in Lazarus IDE, similarly to the option for enabling themes support. For the reference: Windows Docs - Naming Files, Paths, and Namespaces - Maximum Path Length Limitation https://docs.microsoft.com/en-us/windows/desktop/FileIO/naming-a-file#maximum-path-length-limitation Regards, Denis -- ___ lazarus mailing list lazarus@lists.lazarus-ide.org https://lists.lazarus-ide.org/listinfo/lazarus
Re: [Lazarus] Long paths manifest
--File I/O functions in the Windows API convert "/" to "\" as part of converting the name to an NT-style name, except when using the "\\?\" prefix as detailed in the following sections. So apps may have new bugs from this prefix. when app uses / shashes (fn := dir + '/' + name) by mistake. Alex -- ___ lazarus mailing list lazarus@lists.lazarus-ide.org https://lists.lazarus-ide.org/listinfo/lazarus
[Lazarus] Long paths manifest
Hello, Windows API is capable of working with extended-length path for a maximum total path length of 32,767 characters, thus, overcoming the infamous 260 characters path limitation (a.k.a. MAX_PATH). To specify an extended-length path, use the "\\?\" prefix. For example, "\\?\C:\Very\Long\Path". According to Windows Docs, one can enable the new long path behavior per app via the manifest: - xmlns:ws2="http://schemas.microsoft.com/SMI/2016/WindowsSettings";> true - Has anyone had any experience with embedding such manifest? What would be the best way to add such a manifest to an application, currently? Perhaps this could be added as an option in Lazarus IDE, similarly to the option for enabling themes support. For the reference: Windows Docs - Naming Files, Paths, and Namespaces - Maximum Path Length Limitation https://docs.microsoft.com/en-us/windows/desktop/FileIO/naming-a-file#maximum-path-length-limitation Regards, Denis -- ___ lazarus mailing list lazarus@lists.lazarus-ide.org https://lists.lazarus-ide.org/listinfo/lazarus