Original bug ID: 7564 Reporter:@nojb Assigned to:@alainfrisch Status: resolved (set by @alainfrisch on 2017-07-18T22:05:42Z) Resolution: fixed Priority: normal Severity: minor Fixed in version: 4.06.0 +dev/beta1/beta2/rc1 Category: platform support (windows, cross-compilation, etc)
Bug description
It appears that the target of native Windows symlinks (as created by Unix.symlink under Windows) must necessarily use backward slashes. Otherwise the native Windows APIs will think that the target does not exist.
As a compatibility layer, Unix.symlink should allow forward slashes in its argument.
Original bug ID: 7564
Reporter: @nojb
Assigned to: @alainfrisch
Status: resolved (set by @alainfrisch on 2017-07-18T22:05:42Z)
Resolution: fixed
Priority: normal
Severity: minor
Fixed in version: 4.06.0 +dev/beta1/beta2/rc1
Category: platform support (windows, cross-compilation, etc)
Bug description
It appears that the target of native Windows symlinks (as created by Unix.symlink under Windows) must necessarily use backward slashes. Otherwise the native Windows APIs will think that the target does not exist.
As a compatibility layer, Unix.symlink should allow forward slashes in its argument.
Steps to reproduce
The text was updated successfully, but these errors were encountered: