User forums > Using Code::Blocks
Custom makefile problems
tomasbym:
Hello,
1)No I don't use the -g argument in makefile. I thought I just need to have it checked in Compiler and Debugger settings.
2) Solved, thanks
3) That was a first thing I've tried but without success. I don't understand quite well how this works, but unfortunately I haven't found any documentation - I assume that the variable $makefile if the name of my makefile and $target is the target name - what is the $make variable? The command I need to execute is make clean-all
Thank you again for all your replies,
T.
Jenna:
You should turn on full commandline logging to see which commands are executed: http://wiki.codeblocks.org/index.php?title=FAQ#Q:_How_do_I_troubleshoot_an_compiler_problem.3F
$make is the name of the make-executable as it is set in the "Toolchain executables" tab of the compiler you use,
$makefile is the name of the makefile as it is set in your project properties. It's needed, if the makefile is not named like the default makefile of your make-executable.
$target is the name of the target you currently compile.
tomasbym:
Thanks for explanation, but I am still struggling with the biggest issue - the debugging. Any suggestions?
Thank you,
T.
Jenna:
--- Quote from: tomasbym on March 18, 2011, 05:46:52 pm ---Thanks for explanation, but I am still struggling with the biggest issue - the debugging. Any suggestions?
Thank you,
T.
--- End quote ---
Without -g (if it's gcc) you have no chance.
If you use custom makefiles, you have to set it in the makefile, because you bypass C::B's build-system.
Some makefiles also have debug-targets, but you have to search for it in your makefile or in the documentation yourself.
tomasbym:
Hello,
I am able to debug the program with gdb from terminal. It should means that I had compiled it correctly with the debug marks. But I am not able to debug using CB.
Thanks,
T.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version