Build path on Mac seems wrong: \ vs /
See original GitHub issueI installed the extension on VS Code 1.15.1 on Mac OS Sierra and i cannot compile the sketches. To reproduce:
- open folder ‘sketch’ in VS Code
- open file ‘sketch.pde’
- create task file: OK
- run task
processing-java
Error in console: incorrect classpath: /blabla/sketch\out
java.io.FileNotFoundException:/blabla/sketch/out/source/noise_blur.java (No such file or directory)
Notice that out
uses the backslash symbol (\
) instead of the normal slash (/
). The .java file is then created in a folder literally called sketch\out
in mac (and it’s not launched from VS Code, since it cannot find it).
Issue Analytics
- State:
- Created 6 years ago
- Comments:8 (5 by maintainers)
Top Results From Across the Web
makefile pathing issues on OSX - Stack Overflow
I've posted an updated makefile and error message. It still comes down to avr-gcc not being found in the path, what I can...
Read more >Path of Building for Mac! 3.20-ready - Forum - Path of Exile
I've been enjoying POE on Mac, but found it annoying that Path of Building didn't work on Mac. Well, I found a version...
Read more >Clang linking error MacOS Big Sur | Apple Developer Forums
Hi All, I am trying to build my helloworld.cpp, but I am having problem since I updated to Big Sur. Below a verbose...
Read more >Compiling and Building - Visual Studio for Mac - Microsoft Learn
This article describes how to compile and build projects and solutions in Visual Studio for Mac.
Read more >MacOS - Set / Change $PATH Variable Command - nixCraft
$PATH is nothing but an environment variable on Linux, OS X, ... OR use vi text editor as follows to create /etc/paths.d/zmodemapp file:...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I’d suggest putting this in the readme. I stumbled onto this problem as well.
Perhaps I’m reading the issue wrong, so I don’t know if this is a “real” solution, but I just changed in the tasks.json,
"--output=${workspaceRoot}\\out"
to"--output=${workspaceRoot}/out"
and it seems to build ok now.If this wasn’t the problem you’re talking about and solves nothing, I apologize for butting in. 😊