public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "gaoliming" <gaoliming@byosoft.com.cn>
To: <devel@edk2.groups.io>, <afish@apple.com>
Subject: 回复: [edk2-devel] Why is MAX_LONG_FILE_PATH 500 vs. PATH_MAX?
Date: Fri, 30 Oct 2020 09:34:58 +0800	[thread overview]
Message-ID: <004d01d6ae5c$e1228b10$a367a130$@byosoft.com.cn> (raw)
In-Reply-To: <86A23533-E614-4B71-BA87-6BFF8338E0FA@apple.com>

[-- Attachment #1: Type: text/plain, Size: 889 bytes --]

This macro is added to resolve the limitation on WINDOWS OS for the length
of entire file path can’t be larger than 255. It use the hard code 500,
because 500 is enough for most case. Do you meet with the problem that the
file path length exceeds 500?

 

Thanks

Liming

发件人: bounce+27952+66762+4905953+8761045@groups.io
<bounce+27952+66762+4905953+8761045@groups.io> 代表 Andrew Fish via
groups.io
发送时间: 2020年10月30日 1:24
收件人: edk2-devel-groups-io <devel@edk2.groups.io>
主题: [edk2-devel] Why is MAX_LONG_FILE_PATH 500 vs. PATH_MAX?

 

Does anyone know why MAX_LONG_FILE_PATH [1] is hard coded to 500 vs. using
the systems PATH_MAX?

 

On Linux I think PATH_MAX is 4KiB and on macOS it is 1KiB.

 

 

[1]
https://github.com/tianocore/edk2/blob/master/BaseTools/Source/C/Common/Comm
onLib.h#L17

 

Thanks,

 

Andrew Fish




[-- Attachment #2: Type: text/html, Size: 4678 bytes --]

  reply	other threads:[~2020-10-30  1:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-29 17:24 Why is MAX_LONG_FILE_PATH 500 vs. PATH_MAX? Andrew Fish
2020-10-30  1:34 ` gaoliming [this message]
2020-10-30  1:37   ` [edk2-devel] " Andrew Fish
2020-10-30  2:25     ` 回复: " gaoliming
2020-10-30  2:27       ` Andrew Fish
2020-10-30  2:53         ` 回复: " gaoliming
2020-10-30  2:54           ` Andrew Fish
2020-10-30  3:10             ` 回复: " gaoliming

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='004d01d6ae5c$e1228b10$a367a130$@byosoft.com.cn' \
    --to=devel@edk2.groups.io \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox