User forums > General (but related to Code::Blocks)
Proposal: Make compiler and linker command line visible to user
Vampyre_Dark:
Right Click in Build Window / [x] Show Command Line ?
szczepan:
--- Quote from: Vampyre_Dark on May 07, 2007, 09:24:13 pm ---Right Click in Build Window / [x] Show Command Line ?
--- End quote ---
I second this :)
szczepan:
--- Quote from: MortenMacFly on May 07, 2007, 09:09:17 pm ---
--- Quote from: Andi78 on May 07, 2007, 08:58:32 pm ---Or turn this option on by default... couldn't hurt :)
--- End quote ---
One could also argue like this:
- Is this an advanced option? : Yes.
--- End quote ---
... but that's a trivial "yes" IMO. C::B is a programming tool, and programming is an advanced thing to do in the first place :)
--- Quote ---- Does it make sense to turn advanced options initially on? : No.
--- End quote ---
Does it make sense to assume that a programmer is an "advanced user"? : Yes :)
--- Quote ---I also don't really know where else to put this option.
--- End quote ---
You could keep it where it is and add a frontside control for it.
--- Quote ---It is related to the tool chain (as it applies not only to the compiler but also to the linker, resource compiler etc...). In addition it is an "other" option - not truly related to any other section available in the compiler options (I mean: other than "other" ;-)).
--- End quote ---
My humble analysis is that it is a user preference or an environment option, not a compiler option at all, i.e. not actually related to the toolchain. It doesn't affect toolchain operation, does it? By similar logic it is very much related to the log, as the log is the only thing this option affects :)
Ceniza:
--- Quote from: szczepan ---My humble analysis is that it is a user preference or an environment option, not a compiler option at all, i.e. not actually related to the toolchain. It doesn't affect toolchain operation, does it? By similar logic it is very much related to the log, as the log is the only thing this option affects :)
--- End quote ---
It's a compiler option because it's the compiler the one that decides what to execute and how to show it in the log. In other words: it's provided by the compiler plugin, so it must be within its options.
If the compiler stuff was part of the IDE as it and not a plugin, it could make sense to move it elsewhere, but that's not the case.
manmach:
--- Quote from: Ceniza on May 10, 2007, 02:48:36 am ---
--- Quote from: szczepan ---My humble analysis is that it is a user preference or an environment option, not a compiler option at all, i.e. not actually related to the toolchain. It doesn't affect toolchain operation, does it? By similar logic it is very much related to the log, as the log is the only thing this option affects :)
--- End quote ---
It's a compiler option because it's the compiler the one that decides what to execute and how to show it in the log. In other words: it's provided by the compiler plugin, so it must be within its options.
If the compiler stuff was part of the IDE as it and not a plugin, it could make sense to move it elsewhere, but that's not the case.
--- End quote ---
It is not the compiler that decides. If anything, it's the compiler plugin. But that does not change the fact that from the user's point of view, it is part of the display. And therefore it should be a display setting.
Have a look at KDevelop. You can change its output setting by right clicking the view. And without recompiling anything. I would suggest the same would be done for Code::Blocks. Because if most of the time you do not wish to see al the details, you can turn it off. And then when something unexpected happens, you can have a quick peek without having to go to options dialogs and having to rebuild.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version