Is it worth adding the GDB pretty printers like CodeLite does and include them in the C:B installer?IMO: Nope, these files shouldn't be part of the installation because they would get outdated. We cannot ship every given library or helper file in the world, for every version.
Does anyone have any ideas on when the WIKI editing will become available again?Unfortunately the answer here is nope again and it is not the case that I'm not asking the same question for some time already.
Is it worth adding the GDB pretty printers like CodeLite does and include them in the C:B installer?IMO: Nope, these files shouldn't be part of the installation because they would get outdated. We cannot ship every given library or helper file in the world, for every version.
Okay, so how do you make it easier for the end user to configure and setup the GDB pretty printers?On linux the build of a particular library should be embedding a section which specifies how gdb should auto-load its printers. No idea if there is the same feature for windows, but this is the only newbie friendly solution.
On linux the build of a particular library should be embedding a section which specifies how gdb should auto-load its printers. No idea if there is the same feature for windows, but this is the only newbie friendly solution.I have not been able to find info on this. Can you please point me where I can find info on this. I may not be using the correct search words in google.
p.s. Try the stl printers with something like a map<string, vector<string>> and you'll soon stop bothering with printers in C::B.On Windows this works because the GDB is shipped with a gdbinit that is configured to support C++. The following is the the MINGW32 gdbinit showing the C++ pretty printer support:
python
import sys
sys.path.insert(0, sys.path[0] + '/../../gcc-8.1.0/python')
from libstdcxx.v6.printers import register_libstdcxx_printers
register_libstdcxx_printers (None)
end