RFR : 8217093: Support extended-length paths in parse_manifest.c on windows
matthias.baesken at sap.com
Wed Jan 16 14:43:13 UTC 2019
Hi Alan , do you think it is good to start a UNIX parse_manifest_md.c too with just a one-liner in it ?
Or do you prefer only having the windows - file with the Windows coding and keeping the UNIX one-liner for open_jarfile in parse_manifest.c ?
Best regards, Matthias
> -----Original Message-----
> From: Alan Bateman <Alan.Bateman at oracle.com>
> Sent: Mittwoch, 16. Januar 2019 10:37
> To: Baesken, Matthias <matthias.baesken at sap.com>; core-libs-
> dev at openjdk.java.net
> Subject: Re: RFR : 8217093: Support extended-length paths in
> parse_manifest.c on windows
> On 16/01/2019 09:07, Baesken, Matthias wrote:
> > Hi Alan, I thought having UNIX+Windows code in this case together at
> one place would be okay .
> > However, if you prefer separating it, should I put it here ?
> > src/java.base/windows/native/libjli/java_md.c
> > Or do you have a better suggestion ?
> With a few exceptions, the Windows specific code for jli.dll is in
> src/java.base/windows/native/libji so if it's not too difficult then I
> think that should be location for the Windows long path support. It's
> might be parse_manifest_md.c rather than java_md.c as the latter is the
> platform specific code to go with launcher code in java.c.
More information about the core-libs-dev