I think @8:02 you can specify the different build scripts in a task. Json file and hit shift + Ctrl +B to pick which script you want . That way you don't have to write the build script over and over.
@8:02 "Can you turn this into a button" - there is a button already there, in your VScode version too. Bottom blue task bar - somewhere in the middle - there is a cog and "Build" button :P When you click it it builds whatever config you selected - which is specified on another button to the left - here "CMake: [Debug]: Ready" - when you click on it you can change between Release/MinSizeRel/RelWithDebInfo. But I like your video otherwise, good effort :)
So the MSBuild.exe was not recognized in my terminal what am I supposed to do from there, where did the command come from? EDIT: ok so I just had to add that the user's PATH environment variable: C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Current\Bin" It might Enterprise/ instead of Community/ directory or something entirely different for other people.
Could you please make video for using C++ and VsCode in linux and how to configure tasks, launch, c_cpp_properties json fils and how to debugging application ? ☺
after doind ctrl+ shit +p -> Cmake : quickstart, i can not see any option with VS Community 2019 release... options. what can be wrong here in VScode? (i have already install CMAKE, C/C++ extension in VS code)
I get an error as _Bad CMake executable: "". Check to make sure it is installed or the value of the "cmake.cmakePath" setting contains the correct path_ Any idea on how to solve this? Thanks in advance
I had this error and solved it by installing CMake with the terminal (not just installing the CMake VSC extensions) I'm running a mac so your mileage may vary
Also, you say to make the CMakeLists.txt, then you say to use the quick start (which I did not have the same options as you), and then you say if that does not work, then do things manually... What if it DID work? Do I still need the txt file??? Why are there no good tutorials for C++ and vscode?
@@CodeTechandTutorials i believe everything in the bottom bar comes with cmake extension because you are also able to change compiler, part building etc from down there. EDIT: if you look at 6 minutes in the buttom of your screen below the terminal window. Those are buttons from I think the cmake extension
@@CodeTechandTutorials yeah, cmake build tools did it all. Everything related to c++ project management in vs code. C++/C ext only provides linting and stuff.
I wish I could get to the point of just #include working without red squiggles. On my 5th install of VS Code and following various guides installing cmake and compilers, VS Code Build Tools etc etc and it's always the same result, you can't write any code because VS Code never knows where anything is? Why is it so complex to just install and start coding in C++ I don't get it.
@@CodeTechandTutorials I just find where the whole .h, .hh, .lib, .dll side to C++ really confusing. Any library I want to use always seems to take me hours and hours to get working and often it seems it's worked purely by luck half the time. Hopefully it gets easier, it's the main barrier for me, the coding is easy by comparison haha!
I understand that - the problem with these ide's is they don't follow logic (as compared to coding), they just happen to be however the devs made them. I agree it is kind of annoying.
@@CodeTechandTutorials I learned a lot from your videos, I'm getting there, so thanks. It's a steep learning curve on the workflow, but guess it's just how it is.
@@SamHocking Any luck getting rid of those red squiggles??Or do you still just ignore them and work as if they don't exist?I have been looking for a fix for about 6 hours but no luck! :(
@@altrrrr Fair enough I missed that part. Still he did say that so quickly and skipped the hardest step and that's the Gigabyte of compielr downloads, setting up your compiler, cmake and paths. This is not as trival as saying, 'uh, you need a C++ compiler'
Thank you for this. In just 10 minutes I was able to get to the meat of writing and running C++ in VSCode.
with that sound in the back and your voice i feel like getting enlightened thank you for the great video
I think @8:02 you can specify the different build scripts in a task. Json file and hit shift + Ctrl +B to pick which script you want . That way you don't have to write the build script over and over.
Let's goooooooo!!
Thank you so much for making this.
you have the most relaxing voice omf
great video !!
thanks Gilfoyle
He really does look like Gilfoyle from Silicon Valley though
Really helpful! thanks man
Awesome video man! This helped a lot!
Glad it helped!
@8:02 "Can you turn this into a button" - there is a button already there, in your VScode version too.
Bottom blue task bar - somewhere in the middle - there is a cog and "Build" button :P When you click it it builds whatever config you selected - which is specified on another button to the left - here "CMake: [Debug]: Ready" - when you click on it you can change between Release/MinSizeRel/RelWithDebInfo.
But I like your video otherwise, good effort :)
That was very helpful, thanks for explaining the launch.json file. By the way, I like your vibe
So the MSBuild.exe was not recognized in my terminal what am I supposed to do from there, where did the command come from?
EDIT:
ok so I just had to add that the user's PATH environment variable:
C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Current\Bin"
It might Enterprise/ instead of Community/ directory or something entirely different for other people.
Thank you... You King
thanks much!
Thank you Gilfoyle.
He does look strangely similar to Gilfoyle from Silicon Valley though
Could you please make video for using C++ and VsCode in linux and how to configure tasks, launch, c_cpp_properties json fils and how to debugging application ? ☺
man, you just saved my ass, you have no idea. thank you so much
Thank you, random youtube video! You saved my sanity.
this method is tightly coupled to windows platform. There should be another way that doesn't use MS Visual Studio.
after doind ctrl+ shit +p -> Cmake : quickstart, i can not see any option with VS Community 2019 release... options. what can be wrong here in VScode? (i have already install CMAKE, C/C++ extension in VS code)
I don't see the .sln project file, what do I do?
3:12 what did you do here? why do you suddenly habe a "build" folder? where did that come from?
Can you do one on how to get this working in linux?
what about all those buttons in the blue bar at the bottom of the screen
why cant we compile the Cmake List from Visual Studio Code?
My build folder did not get created after running the >cmake: quickstart in the command pallette. Anyone know why?
same did you figure it out
Is there a way to run a watcher and rebuild automatically, ideally with the new vs 2022 hot reloading?
There is always a way.
I get an error as
_Bad CMake executable: "". Check to make sure it is installed or the value of the "cmake.cmakePath" setting contains the correct path_
Any idea on how to solve this? Thanks in advance
I had this error and solved it by installing CMake with the terminal (not just installing the CMake VSC extensions) I'm running a mac so your mileage may vary
Nvm if you see my old comments, i wasnt using the right build, i had to click "search generators" for vscode to find my vs 2022 then let me use it
Whoa, that first background music is so relaxing ^^ does anyone know where to find it?
Bad cmake executable please help
does it works on mac
Also, you say to make the CMakeLists.txt, then you say to use the quick start (which I did not have the same options as you), and then you say if that does not work, then do things manually... What if it DID work? Do I still need the txt file??? Why are there no good tutorials for C++ and vscode?
Can you do a video on using Visual Studio IDE Community with CMake & Any Compiler?
I came for the CMake tutorial, but I stayed for the trippy music.
whats the name of the music ?
I didn't get the sln file
Sorry for the late comment. Tbh I have always just used the build button in the bottom status bar to the right of where the tool chain is shown
I hadn't noticed that is that from an extension?
@@CodeTechandTutorials i believe everything in the bottom bar comes with cmake extension because you are also able to change compiler, part building etc from down there.
EDIT: if you look at 6 minutes in the buttom of your screen below the terminal window. Those are buttons from I think the cmake extension
@@tanja84dk1 I'll check it out, Thank you for the tip!
@@CodeTechandTutorials yeah, cmake build tools did it all. Everything related to c++ project management in vs code. C++/C ext only provides linting and stuff.
How did you get build folder out of nowhere
I'm also stuck on this did you find an answer?
I wish I could get to the point of just #include working without red squiggles. On my 5th install of VS Code and following various guides installing cmake and compilers, VS Code Build Tools etc etc and it's always the same result, you can't write any code because VS Code never knows where anything is? Why is it so complex to just install and start coding in C++ I don't get it.
It just needs to know where your headers are.
@@CodeTechandTutorials I just find where the whole .h, .hh, .lib, .dll side to C++ really confusing. Any library I want to use always seems to take me hours and hours to get working and often it seems it's worked purely by luck half the time. Hopefully it gets easier, it's the main barrier for me, the coding is easy by comparison haha!
I understand that - the problem with these ide's is they don't follow logic (as compared to coding), they just happen to be however the devs made them. I agree it is kind of annoying.
@@CodeTechandTutorials I learned a lot from your videos, I'm getting there, so thanks. It's a steep learning curve on the workflow, but guess it's just how it is.
@@SamHocking Any luck getting rid of those red squiggles??Or do you still just ignore them and work as if they don't exist?I have been looking for a fix for about 6 hours but no luck! :(
👍
Haha Bob Ross the programmer.
not much help if you forget to mention that you need a c++ compiler.
0:30
@@altrrrr Fair enough I missed that part. Still he did say that so quickly and skipped the hardest step and that's the Gigabyte of compielr downloads, setting up your compiler, cmake and paths. This is not as trival as saying, 'uh, you need a C++ compiler'
If you have Visual Studio why would you need to use VSCode to compile your C++ code ??
what a. strange workflow…
Also, WTF are you opening Visual Studio for a VSCode tutorial???
Wow.. you look like Jesus talking
tech jesus
While I appreciate your content. PLEASE SLOW DOWN! Every time you typed or did something, you left no time for viewers to pause and follow.