rojo icon indicating copy to clipboard operation
rojo copied to clipboard

Rojo 6.x "build" command fails when src contains symlinked folders

Open dejayc opened this issue 4 years ago • 1 comments

I encounter the following error when executing rojo build using Rojo 6.0.0-rc1 when my src folder contains a symlinked folder:

[ERROR] failed to query metadata of file `{...path}\src/shared\{symlinked_folder}`
[ERROR]   caused by The file cannot be accessed by the system. (os error 1920)

The error goes away when I replace the symlinked folder with an actual folder containing the same contents as the symlinked folder.

I'm using Windows 10 WSL2 running Debian for my development. My directory hierarchy is as such:

> project root
|  > submodules
|  |  > roact
|  |  |  > src
|  |  > rodux
|  |  |  > src
|  > rblx
|  |  > default.project.json
|  |  > place.rbxlx
|  |  > src
|  |  |  > shared
|  |  |  |  > Roact (symlink to >project root > submodules > roact > src)
|  |  |  |  > Rodux (symlink to > project root > submodules > rodux > src)

dejayc avatar Jan 26 '21 02:01 dejayc

Rojo is known to have issues with symlinks. I really need to go through and do some stuff with path canonicalization to fix these for good. 😢

In the meantime, you may be able to use Rojo's nested project feature to emulate symlinks. Instead of having an actual filesystem symlink, just create a project whose sole entry is a relative path!

LPGhatguy avatar Jan 26 '21 03:01 LPGhatguy