You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I try to build (or run) a v file located on a folder of my NAS and mounted on my Windows machine as a drive as v run test.v I have the following error:
builder error: UNC\192.168.0.20\home\Projects\V\tuto does not exist
I'm actually in that folder.
If I copy that folder to a local drive, it works.
Reproduction Steps
v run test.v
Expected Behavior
should compile and run, regardless of the location if the file
Current Behavior
builder error: UNC path does not exist
Possible Solution
No response
Additional Information/Context
No response
V version
V 0.4.10 488434b
Environment details (OS name and version, etc.)
Win 10 64bit
Note
You can use the 👍 reaction to increase the issue's priority for developers.
Please note that only the 👍 reaction to the issue itself counts as a vote.
Other reactions and those to comments will not be taken into account.
The text was updated successfully, but these errors were encountered:
Describe the bug
When I try to build (or run) a v file located on a folder of my NAS and mounted on my Windows machine as a drive as v run test.v I have the following error:
builder error:
UNC\192.168.0.20\home\Projects\V\tuto
does not existI'm actually in that folder.
If I copy that folder to a local drive, it works.
Reproduction Steps
v run test.v
Expected Behavior
should compile and run, regardless of the location if the file
Current Behavior
builder error: UNC path does not exist
Possible Solution
No response
Additional Information/Context
No response
V version
V 0.4.10 488434b
Environment details (OS name and version, etc.)
Win 10 64bit
Note
You can use the 👍 reaction to increase the issue's priority for developers.
Please note that only the 👍 reaction to the issue itself counts as a vote.
Other reactions and those to comments will not be taken into account.
The text was updated successfully, but these errors were encountered: