I'm not sure of this is a reasonable feature request.
Currently GDB setting is a global setting under Settings->GDB Settings. The problem is if you have multiple compilers installed GDB isn't necessarily compatible between them, so when you switch from an ARM, AVR, or Windows based project you need to need to change the GDB settings too, okay but annoying. Seems it would make sense to move the GDB setting (at least the path) to the Compilers->Tools setting. (This sounds like it could be ugly with the amount of changes needed).
I could add this as a feature request if it might happen someday.
Move GDB Settings to Compiler->Tools?
-
- CodeLite Expert
- Posts: 167
- Joined: Fri Jul 22, 2011 5:32 am
- Genuine User: Yes
- IDE Question: C++
- Contact:
- eranif
- CodeLite Plugin
- Posts: 6375
- Joined: Wed Feb 06, 2008 9:29 pm
- Genuine User: Yes
- IDE Question: C++
- Contact:
Re: Move GDB Settings to Compiler->Tools?
Most of the debugger settings can be set per project in the project settings -> debugger section
Especially, the debugger executable and startup commands
Isn't it enough?
Eran
Especially, the debugger executable and startup commands
Isn't it enough?
Eran
Make sure you have read the HOW TO POST thread
-
- CodeLite Expert
- Posts: 231
- Joined: Sat Nov 24, 2012 8:04 pm
- Genuine User: Yes
- IDE Question: c++
- Location: Los Angeles
- Contact:
Re: Move GDB Settings to Compiler->Tools?
Hi Eran,
I've been trying to add new error/warning regexes in Build Settings -> Patterns to catch some currently undetected cases but it's hard to debug without a log. Would it be possible to log all the captures (within quotes) when CL's log level is set to Debug?
thx a lot & cheers,
-- p
I've been trying to add new error/warning regexes in Build Settings -> Patterns to catch some currently undetected cases but it's hard to debug without a log. Would it be possible to log all the captures (within quotes) when CL's log level is set to Debug?
thx a lot & cheers,
-- p
main: Debian Jessie x64 + custom wxTrunk
-
- CodeLite Expert
- Posts: 231
- Joined: Sat Nov 24, 2012 8:04 pm
- Genuine User: Yes
- IDE Question: c++
- Location: Los Angeles
- Contact:
Re: Move GDB Settings to Compiler->Tools?
nevermind my last request; I just saw the wxRegEx logic using Match() so extracting partial matches on a global fail isn't that easy, not to mention dicy to pass through a vararg logger. I'll try to think of some other way.
thx & cheers,
-- p
thx & cheers,
-- p
main: Debian Jessie x64 + custom wxTrunk
-
- CodeLite Expert
- Posts: 231
- Joined: Sat Nov 24, 2012 8:04 pm
- Genuine User: Yes
- IDE Question: c++
- Location: Los Angeles
- Contact:
Re: Move GDB Settings to Compiler->Tools?
to close the thread I so rudely hijacked (sorry about that ), there's really no need for a new CL feature to debug regexes - I just needed to know what regex syntax it uses, then I'll cut & paste undetected errors & warnings into my own test app to debug them. Should have thought about it earlier...
cheers,
-- p
cheers,
-- p
main: Debian Jessie x64 + custom wxTrunk