Cygwin generates syscalls for *.lnk files on filesystems with native symlink support?

[Corinna Vinschen]

On Jan  8 17:11, matthew patton via Cygwin wrote:
> > For instance: Getting rid of .lnk files isn't easy with backward compatibility in mind.
> screw backward compatability! :)Why carry around bandaids on bandaids
> for an OS that is 10 years out of support?

We're using .lnk files for FIFOs. That's the compat concern, not some OS
from the past.

> Obviously not ripe for 3.6 or maybe even 3.7, but at some point we
> should just put a stick in the sand and say this .lnk crap is dead and
> you have to either compile it back in with an IFDEF or a CYGWIN var.

No ifdefs, and a Cygwin var setting unfortunately exists.

> And while we're at it use OS-native links instead of Junctions. I'm
> not sure how that came about but Junctions are unhelpful.

Cygwin does not create symlinks as junctions.  No idea where you got
that idea.


Corinna