Bug 240017

Summary: Allow to disable compressed make output and show full make output
Product: [Applications] kdevelop Reporter: Jed Brown <jed>
Component: Build tools: MakeAssignee: kdevelop-bugs-null
Status: RESOLVED FIXED    
Severity: wishlist    
Priority: LO    
Version: 4.0.0   
Target Milestone: 4.1.0   
Platform: Arch Linux   
OS: Linux   
Latest Commit: http://commits.kde.org/kdevplatform/56bdd6c573b988b6fcb6267bca442e7a92feea38 Version Fixed In:
Sentry Crash Report:

Description Jed Brown 2010-05-29 21:48:41 UTC 
Version:           4.0.0 (using KDE 4.4.3) 
OS:                Linux

Make runs the following command:

/usr/bin/mpicc -o ksponly.o -c -fPIC -Wall -Wwrite-strings -Wno-strict-aliasing -g3   -I/home/jed/petsc/ompi/include -I/home/jed/petsc/include -I/usr/include -I/usr/lib/openmpi -I/home/jed/petsc/ompi/include -I/usr/lib -I/usr/local/include      -D__INSDIR__=src/snes/impls/ksponly/  ksponly.c

but the build output shows

linking ksponly.o (icc)

I believe this line should include the whole compiler name (maybe including path because I have multiple mpicc installed, but at least without truncating the basename).

Reproducible: Always

Steps to Reproduce:
Compile some source file with a compiler than has a name longer than three characters.



OS: Linux (x86_64) release 2.6.33-ARCH
Compiler: gcc
Comment 1 Andreas Pakulat 2010-05-30 00:00:46 UTC 
Thats intentional. The short output is supposed to give only minimal information.

Unfortunately currently we lack a way to disable this and show the full compiler output (instead of parsing and interpreting it), I'm turning this into a wish for doing that.
Comment 2 Jed Brown 2010-05-30 00:08:04 UTC 
Why not just show the whole basename?  "mpicc" is much different than "icc", and "clang++" is much different than "g++".  Showing verbose output is a different feature (that would occasionally be nice), but truncating the basename to three characters can be downright deceptive.
Comment 3 Andreas Pakulat 2010-05-30 00:23:27 UTC 
Its actually not truncated at all. The fact is the compressed output only supports the "wide-known" compilers gcc/g++ and icc. It matches your mpicc because it has icc in the compiler executable name.
Comment 4 Kevin Funk 2013-05-15 18:52:35 UTC 
Git commit 61d32ab3f4f273dadf445a11eff1cd26b7eb1a92 by Kevin Funk.
Committed on 15/05/2013 at 20:50.
Pushed by kfunk into branch 'master'.

Add support for Clang/Clang++ in build output view

Patch by Torbjoern Klatt.
REVIEW: 110068

M  +2    -2    outputview/outputfilteringstrategies.cpp

http://commits.kde.org/kdevplatform/61d32ab3f4f273dadf445a11eff1cd26b7eb1a92
Comment 5 Kevin Funk 2013-05-15 19:32:23 UTC 
Git commit 56bdd6c573b988b6fcb6267bca442e7a92feea38 by Kevin Funk.
Committed on 15/05/2013 at 21:29.
Pushed by kfunk into branch 'master'.

Fix detection of 'mpicc' compiler

Add tests for shortenedText property of FilterItem.

M  +2    -2    outputview/outputfilteringstrategies.cpp
M  +31   -0    outputview/tests/filteringstrategytest.cpp
M  +2    -0    outputview/tests/filteringstrategytest.h

http://commits.kde.org/kdevplatform/56bdd6c573b988b6fcb6267bca442e7a92feea38