Code::Blocks Forums
User forums => Using Code::Blocks => Topic started by: akey on October 22, 2008, 10:42:56 am
-
Hello everybody,
I´m not quit sure whether I have a problem or if I simply want things from code::blocks which it isn`t build for.
In the moment I´m trying to build some additional features to the wpa_supplicant (http://hostap.epitest.fi/releases/wpa_supplicant-0.5.10.tar.gz) project. Doing this just on the console without the comfort of a debugger is very boring because it tooks several time to build the hole project just to get some added debug messages.
So my question is whether it is possible to build the hole supplicant inside code::blocks to have the comfort of a wesome IDE?
Regards
Arne
-
So my question is whether it is possible to build the hole supplicant inside code::blocks to have the comfort of awesome IDE?
What you can compile on the command line you will surely be able to compile in C::B. So: Yes.
-
OK nice answer :shock:
My Problem isn´t building the project but debugging it.
I´ve managed to build the project by specifying the Makefile but this causes C::B just to build the project like running "make all". After compiling all the stuff the binary is available but I can´t debug anything inside C::B.
Should I use the ugly DDD in stat or is there a possibility to do debugging in C::B?
regards
Arne
-
Should I use the ugly DDD in stat or is there a possibility to do debugging in C::B?
See - written this in the first place would have made it more understandable... :lol:
Yes, you can debug the sources in C::B. I never tried with Makefile based projects but if you setup a "true" C::B project there should be not problem at all. I am aware of issues related to debugging a Makefile based project. But this was related to path names being truncated during the compilation process so that was a GDB issue rather than C::B (IMHO).