Hi,
I have some questions about the "Commands Only" target. (really architecture neutral query, but i am running under linux).
It seems that this target type only executes the commands listed in the pre-build and/or post-build, is that correct, or does it also still try and execute "make"? I think it is trying to execute "make" and i don't understand why it would with a "Commands Only" target, because "Make" may not be one of the commands i wish to execute. If i wanted to execute make, surely id just enter Make as one of the commands?
Also, the debugger front end is inoperable with a "Commands Only" target, again I'm not understanding why?
Surely just because CodeBlocks didn't build the code doesn't mean it cant be debugged?
It seems like this is what I'm after for my build environment, but it isn't quite there. Are there architectural reasons for these things, or is it just the way it happens to be at the moment.
With regard to debugging, is it because the "Output filename" and the "Execution working dir" cant be set for a Commands Only Target?
If so, what prevents these values being set? (Other than the dialog)
Id like to use CodeBlocks to develop code for embedded systems, and i dont feel the current paradigm fits for me, but i think "Commands Only" could be made to work, if i could use the debug front end with my embedded GDB, and i could specify the specific commands to execute to make a build happen.
Stevo