User forums > General (but related to Code::Blocks)
Proposal: Make compiler and linker command line visible to user
Andi78:
Hi!
As a developer one wants to have control over everything :) Configuring the compiler and linker is really nice in codeblocks, but I can't find a textfield (could be read-only like in MS VS++) showing the complete list of options given to the compiler/linker. In the "build log" window, the call of the compiler/linker is hidden somehow, only the error messages are shown. Would be nice to see the exact command line with all the options there to be able to imagine what the build process does and to find error quickly.
ByeBye, Andi
MortenMacFly:
--- Quote from: Andi78 on May 07, 2007, 10:24:21 am ---Would be nice to see the exact command line with all the options there to be able to imagine what the build process does and to find error quickly.
--- End quote ---
...have a look at my sig.
With regards, Morten.
szczepan:
--- Quote from: Andi78 on May 07, 2007, 10:24:21 am ---In the "build log" window, the call of the compiler/linker is hidden somehow, only the error messages are shown. Would be nice to see the exact command line with all the options there to be able to imagine what the build process does and to find error quickly.
--- End quote ---
Even though it is possible to enable full command line display, the depth at which this option is hidden in the configuration dialog seems to be a recurring usability problem for new users (including me when I was a new user). What about a toggle button somewhere near the log window, or a toggle item in the context menu of the log window? Just an idea.
Andi78:
Or turn this option on by default... couldn't hurt :)
MortenMacFly:
--- 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.
- Does it make sense to turn advanced options initially on? : No.
I also don't really know where else to put this option. 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" ;-)). It is further *not* related to the log - as this shows a lot messages, not only compiler/linker commands stuff. So my personal opinion is: It's good as it is.
What other options would we have?
With regards, Morten.
Navigation
[0] Message Index
[#] Next page
Go to full version