I find the Windows build logs very hard to read, and exceedingly
difficult to find errors in. One big problem, IMO, is all the junk
(presumably) emitted by IDE to tell us what the command line looks
like. What can be done about this to make the Windows logs as
readable as the UNIX ones?
For instance, here's the output of building the accumulate example
with Intel C++:
Build started: Project: accumulate, Configuration: 12d Optimized
Thread-safe Dll|Win32
-------
Creating temporary file "C:\DOCUME~1\batman\LOCALS~1\Temp\RSP1E05.bs"
with contents
[
/c /O1 /I "D:\bman5\builds\34008642\source-buildspace\examples\include"
/I "D:\bman5\builds\34008642\source-buildspace\include" /I
"D:\bman5\builds\34008642\source-buildspace\include\ansi" /I
"D:\bman5\builds\34008642\source-buildspace\build\icc-10.0\12d\include"
/D "_RWSHARED" /D "_MBCS" /FD /EHsc /MD /GS- /GR
/Fo"D:\bman5\builds\34008642\source-buildspace\build\icc-10.0\12d\examples\accumulate/"
/W3 /nologo /Zi /Gd /D_CRT_SECURE_NO_DEPRECATE /GA /Qvc8
/Qlocation,link,"C:\Program Files (x86)\Microsoft Visual Studio 8\VC\bin"
..\..\..\..\examples\manual\accumulate.cpp
]
Creating command line "icl.exe
"@C:\DOCUME~1\batman\LOCALS~1\Temp\RSP1E05.bs""
Creating temporary file "C:\DOCUME~1\batman\LOCALS~1\Temp\RSP1E09.bs"
with contents
[
kernel32.lib user32.lib kernel32.lib user32.lib gdi32.lib winspool.lib
comdlg32.lib advapi32.lib shell32.lib ole32.lib oleaut32.lib uuid.lib
odbc32.lib odbccp32.lib
/OUT:"D:\bman5\builds\34008642\source-buildspace\build\icc-10.0\12d\examples\accumulate.exe"
/INCREMENTAL:NO /nologo /NODEFAULTLIB:"libcp.lib"
/NODEFAULTLIB:"libcpd.lib" /NODEFAULTLIB:"libcpmt.lib"
/NODEFAULTLIB:"libcpmtd.lib" /NODEFAULTLIB:"msvcprt.lib"
/NODEFAULTLIB:"msvcprtd.lib" /TLBID:1 /DEBUG
/PDB:"D:\bman5\builds\34008642\source-buildspace\build\icc-10.0\12d\examples\accumulate.pdb"
/SUBSYSTEM:CONSOLE /OPT:REF /OPT:ICF
/IMPLIB:"D:\bman5\builds\34008642\source-buildspace\build\icc-10.0\12d\examples\accumulate.lib"
/MANIFEST
/MANIFESTFILE:"D:\bman5\builds\34008642\source-buildspace\build\icc-10.0\12d\examples\accumulate\accumulate.exe.intermediate.manifest"
D:\bman5\builds\34008642\source-buildspace\build\icc-10.0\12d\lib\libstd12d.lib
D:\bman5\builds\34008642\source-buildspace\build\icc-10.0\12d\examples\accumulate/accumulate.obj
]
Creating command line "xilink.exe
"@C:\DOCUME~1\batman\LOCALS~1\Temp\RSP1E09.bs""
Creating temporary file "C:\DOCUME~1\batman\LOCALS~1\Temp\RSP1E0E.bs"
with contents
[
/nologo /manifest
"D:\bman5\builds\34008642\source-buildspace\build\icc-10.0\12d\examples\accumulate\accumulate.exe.intermediate.manifest"
/outputresource:"D:\bman5\builds\34008642\source-buildspace\build\icc-10.0\12d\examples\accumulate.exe";#1
]
Creating command line "mt.exe
"@C:\DOCUME~1\batman\LOCALS~1\Temp\RSP1E0E.bs""
-------
Compiling with Intel(R) C++ 10.0.026 [IA-32]... (Intel C++ Environment)
accumulate.cpp
Linking... (Intel C++ Environment)
xilink: executing 'link'
Embedding manifest... (Microsoft VC++ Environment)
-------
Build log was saved at
"file://D:\bman5\builds\34008642\source-buildspace\build\icc-10.0\12d\examples\accumulate\BuildLog.htm"
accumulate - 0 error(s), 0 warning(s)
Contrast that to the gcc log on CygWin:
generating dependencies for $(TOPDIR)/examples/manual/accumulate.cpp
gcc -M -I$(TOPDIR)/include/ansi -D_REENTRANT -mthreads
-I$(TOPDIR)/include -I$(BUILDDIR)/include -I$(TOPDIR)/examples/include
-pedantic -nostdinc++ -O2 -W -Wall -Wcast-qual -Winline -Wshadow
-Wwrite-strings -Wno-long-long -Wcast-align
$(TOPDIR)/examples/manual/accumulate.cpp
gcc -c -I$(TOPDIR)/include/ansi -D_REENTRANT -mthreads
-I$(TOPDIR)/include -I$(BUILDDIR)/include -I$(TOPDIR)/examples/include
-pedantic -nostdinc++ -O2 -W -Wall -Wcast-qual -Winline -Wshadow
-Wwrite-strings -Wno-long-long -Wcast-align
$(TOPDIR)/examples/manual/accumulate.cpp
gcc accumulate.o -o accumulate -mthreads -L$(BUILDDIR)/lib -lstd
-lsupc++ -lcatgets -liconv -lm
