Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.
Announcements
FPGA community forums and blogs on community.intel.com are migrating to the new Altera Community and are read-only. For urgent support needs during this transition, please visit the FPGA Design Resources page or contact an Altera Authorized Distributor.

Printing BuildLog.htm - WordWrap

rasa
Beginner
639 Views
For documentation purposes, I need to hard-copy (printout) the HTML formatted BuildLog file. However the lines are too long and they do not wrap automatically. Is there a way to print the HTML such that all the lines are wrapped and nothing is cut from the page?

Example.
[bash]ifort /nologo /debug:full /QaxSSE4.1 /Qparallel /assume:buffered_io /Qipo /fpp /reentrancy:threaded /gen-interfaces /arch:IA32 /free /Qopenmp /stand:f03 /Qopenmp-report2 /warn:all /fp:source /Qfp-stack-check /Qfp-speculation=off /module:"Release\\" /object:"Release\\" /traceback /check:all /libs:static /threads /c /Qopenmp /Qopenmp-link:static /Qvc9 /Qlocation,link,"C:\Program Files\Microsoft Visual Studio 9.0\VC\bin" "C:\Ragu\sassiext\Kinds.F90"
[/bash]
The above line is cut somewhere beyond 80 characters in the printout.
0 Kudos
3 Replies
Steven_L_Intel1
Employee
639 Views
The HTML for this has the output wrapped in a
 tag, which disables word wrapping. If you don't mind editing the HTML you can fix that. I can't find an obvious way to do it automatically.
0 Kudos
rasa
Beginner
639 Views
Thanks Steve. But it does not help. I deleted all the
 and 
tags and it totally messed up the formatting.

Is there anyway we could request for a fix to this file in the future? Nine out of ten regular ifort users do not care for the files in \Release directory. Unfortunately in our workplace we need to document every single thing with the date/time stamp, checksum and all. The formatting of the BuidLog.htm drives us crazy.

Thanks.

0 Kudos
Steven_L_Intel1
Employee
639 Views
Unfortunately, we don't control this. It is completely handled by Visual Studio. To further depress you, it seems that VS2010 pretty much does away with the standard build log. Instead, it writes dozens of little files, most of which have minimal info. You can tell VS to write "detailed" info in the build log but then you get lots of noise. See here for more info.

The good news is that you won't have an HTML build log to worry about any more...
0 Kudos
Reply