Bug 204633 - Ability to show full compiler output
Summary: Ability to show full compiler output
Status: RESOLVED DUPLICATE of bug 194403
Alias: None
Product: kdevelop
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR wishlist
Target Milestone: ---
Assignee: kdevelop-bugs-null
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-08-21 11:11 UTC by jan.fostier
Modified: 2009-08-21 12:54 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description jan.fostier 2009-08-21 11:11:03 UTC 
Version:           3.9.94 (using KDevPlatform 0.9.95) (using 4.3.00 (KDE 4.3.0), 4.3.0-2.fc11 Fedora)
Compiler:          gcc
OS:                Linux (x86_64) release 2.6.29.6-217.2.3.fc11.x86_64

Perhaps somewhat a duplicate of bug/wish 194403.  If you specify set(CMAKE_VERBOSE_MAKEFILE ON), kdevelop still truncates the compiler output to something like 'compiling xxx.cpp', instead of the full compiler output.

If you have different build targets with different compilation flags, it would be nice to be able to see the full compiler output.
Comment 1 Andreas Pakulat 2009-08-21 12:30:39 UTC 
right its a duplicate, why are you opening a new report then in the first place?

*** This bug has been marked as a duplicate of bug 194403 ***
Comment 2 jan.fostier 2009-08-21 12:54:51 UTC 
>
> right its a duplicate, why are you opening a new report then in the first
> place?
>    
Because the original submission (the ability to configure the verbosity 
of the compiler output) had been correctly marked as 'wishlist'.  
However, I consider truncating the compiler output *by default* with no 
way to change this, as a bug.

But indeed, perhaps I should have just added a comment in the original 
report.  My mistake.