[ 
https://issues.apache.org/jira/browse/CB-12337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15941252#comment-15941252
 ] 

ASF subversion and git services commented on CB-12337:
------------------------------------------------------

Commit e62852c30a61899aa102ccf016984eed0f15244c in cordova-lib's branch 
refs/heads/master from [~sergeyz]
[ https://git-wip-us.apache.org/repos/asf?p=cordova-lib.git;h=e62852c ]

CB-12337 Resolve symbolic links in project root

If project path had symlinks its absolute value was different from that
returned by __dirname inside project-local modules. So when it was joined
with various dirs like 'www' the two absolute paths were merged resulting
in an invalid path.

This should make 'cordova emulate android' work on Windows for projects
with symlinks in path.

There may be other places where similar measures need to be taken.

 This closes #514


> 'cordova emulate' errors if path contains symlink on Windows
> ------------------------------------------------------------
>
>                 Key: CB-12337
>                 URL: https://issues.apache.org/jira/browse/CB-12337
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: CLI, Windows
>    Affects Versions: 6.4.0
>         Environment: Windows 10 x64
>            Reporter: Sergey Zolotarev
>            Priority: Minor
>              Labels: win64
>
> If you are inside a directory that was entered via a symlink (created via 
> mklink /D on Windows) cordova emulate android will fail with the following 
> error:
> Error: Source directory does not exist: 
> C:\Users\szx\Work\Projects\MyProject\E:\Work\Projects\MyProject\platforms\android\platform_www
> Here `C:\Users\szx\Work` is a symlink to `E:\Work`.
> It looks like it concatenate the source and destination paths.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to