.\hello wont be recognized as the code has not been successfully compiled. As far as build tasks are concerned. Can I see the rest of your project? You should have a .vscode folder with three files: tasks.json, launch.json, and cpp-properties.json
i have the same problem
https://drive.google.com/file/d/1Uqv90YuM2yMjdlVCigOl-y4Qs20sR75J/view?usp=sharing
you can download it with the google drive link.
..vscode\hello
the path is successful
I’m not entirely sure, but it looks like it’s failing to compile. When you installed RayLib did you choose the one that came with the MinGW Compiler?
You problem is that you created a cpp file in “.vscode” folder. Move file one folder up (under project) and all should work now. (of course after moving file you need run compile task)
Image of hello.cpp file path in Project
3 Likes
Yup, you need to make sure your cpp files are in the root directory of your project. That’s where cmake and the build task looks.
2 Likes
This topic was automatically closed 20 days after the last reply. New replies are no longer allowed.
I’m getting the same problem and I’m not sure what I did wrong. Mine isn’t in a subfolder.
I feel like maybe some things have changed, maybe I got the wrong Microsoft C++ extension. The video wasn’t very clear on the exact extension and like Blender it seems things in Visual Studio Code break with every Update.
Can you try compiling your code to see if there’s a problem? If you’d like, you can also show me your installed extensions and I can tell you if you got the correct one or not.
Both VS Code and the C++ extension do get updated regularly, and unfortunately we can’t control when and if they break. But we can help you work around them!
1 Like
Thanks, I’ll do that in a bit.
I’m not sure how to compile from Visual Studio Code, in Visual Studio it’s pretty straight forward but I don’t know all those commands of Visual Studio Code.
Terminal > Run Build Task
You don’t technically need the extension pack, just C/C++, but it isn’t hurting you either. You can leave what you have.
That’s what I get when I use Terminal > Run Build Task
When I press a key, it just goes away. Maybe I need to go find a video on YouTube on using Visual Studio Code. Seems a lot of courses like this use it because it’s free and cross platform, so It’s probably a good idea for me to start learning to use it. I’ve just gotten a bit too comfortable with using IDE’s that don’t require written commands like this.
Good news is that means your build was successful! I know the output should really say that and I can’t explain why it does for Stephen.
VS Code can also be used without written commands, which we’ll be doing in the future.
1 Like
Thanks, that would be helpful