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
As the title says I have this question regarding to C/C++ debuggers (in a more specific way with ccppr_vsc one).
I saw those lines in the installation steps for ccppr_vsc and this makes no sense to me due to
I think that the vast majority of C/C++ developers already have gdb installed system-wide.
gdb compilation can be a bit slow and if we already have it system-wide we should be able to skip this step (this could optimize a ton the time to install this debugger).
I know that providing everything ootb is great, but I feel like we don't really need to compile gdb from source if it's already installed system-wide. Maybe we can create a conditional with which gdb and check for the exit code to know if we should compile gdb from source?
The text was updated successfully, but these errors were encountered:
Hi mate, hope you're doing well!
As the title says I have this question regarding to C/C++ debuggers (in a more specific way with
ccppr_vsc
one).I saw those lines in the installation steps for
ccppr_vsc
and this makes no sense to me due togdb
installed system-wide.gdb
compilation can be a bit slow and if we already have it system-wide we should be able to skip this step (this could optimize a ton the time to install this debugger).I know that providing everything ootb is great, but I feel like we don't really need to compile gdb from source if it's already installed system-wide. Maybe we can create a conditional with
which gdb
and check for the exit code to know if we should compile gdb from source?The text was updated successfully, but these errors were encountered: