View previous topic :: View next topic |
Author |
Message |
wahorger
Joined: 13 Oct 2014 Posts: 1227 Location: Morrison, CO, USA
|
Posted: Wed Jan 25, 2017 12:37 am Post subject: Additional output from compiler |
|
|
During the compilation of the 300+ files that make up my project, having the name of the file being compiled would be helpful. It's no problem when there is an error as the MAKE will quit, and the file name shows up in that case anyway. But when there are warnings, it can be difficult to track down which file contains the problem. If there are no errors, I really don't care about the name of the file all that much.
Or is there a compiler option that I am missing?
Thanks,
Bill |
|
Back to top |
|
|
PaulLaidler Site Admin
Joined: 21 Feb 2005 Posts: 8037 Location: Salford, UK
|
Posted: Wed Jan 25, 2017 9:03 am Post subject: |
|
|
There is currently no option that I can think of.
I guess that you could get your makefile to echo the file name before compiling each file.
Let me know how you get on. It might be a simple matter to add a new command line option. |
|
Back to top |
|
|
wahorger
Joined: 13 Oct 2014 Posts: 1227 Location: Morrison, CO, USA
|
Posted: Wed Jan 25, 2017 11:17 pm Post subject: |
|
|
I was hoping to avoid changing the makefile, but, alas, it will be done!
Thanks, Paul. |
|
Back to top |
|
|
JohnCampbell
Joined: 16 Feb 2006 Posts: 2593 Location: Sydney
|
Posted: Thu Jan 26, 2017 2:09 am Post subject: |
|
|
Paul,
An option that echoes the command line would be a help.
This could then be extended to echo all compiler options that have been selected, both in ftn95.cfg and the command line. This would exclude echoing compiler options that have not been selected and remain default.
This output would help when reading redirected compiler output, such as > ftn95.tce and also identify when some compiler options have been taken from ftn95.cfg files in the path. This can identify unexpected problems that I do get from time to time, especially when returning to projects that I am not actively working on.
ftn95 ... /echo could be a good
John |
|
Back to top |
|
|
PaulLaidler Site Admin
Joined: 21 Feb 2005 Posts: 8037 Location: Salford, UK
|
Posted: Thu Jan 26, 2017 8:14 am Post subject: |
|
|
John
I will add it to the wish-list.
In the meantime, as you will probably know, /list provides an output file that includes a list of the command line options currently in place. |
|
Back to top |
|
|
DanRRight
Joined: 10 Mar 2008 Posts: 2877 Location: South Pole, Antarctica
|
Posted: Fri Mar 24, 2017 1:20 pm Post subject: |
|
|
Yes, adding /echo_options will tell you useful info when you compile and redirect warnings to file
>FTN95 filename.f95 /blah /bla2 /blah224557 /sdffgjjkjjh /echo_options >warnings |
|
Back to top |
|
|
JohnCampbell
Joined: 16 Feb 2006 Posts: 2593 Location: Sydney
|
Posted: Sat Mar 25, 2017 2:08 am Post subject: |
|
|
When a rebuild involves 100's of files an indication of where you are can help a lot.
Having an option to echo the file name and compilation options would help for any redirection log. I typically use .bat files for rebuild and having this information in the log file would be very useful.
It would also be good if this, plus the summary report of each routine could be optionally included in the PLATO output window, if it did not conflict with the linkage of error messages to the source file. |
|
Back to top |
|
|
PaulLaidler Site Admin
Joined: 21 Feb 2005 Posts: 8037 Location: Salford, UK
|
Posted: Tue Apr 11, 2017 9:04 am Post subject: |
|
|
A new option /ECHO_OPTIONS has been added for the next release of FTN95. |
|
Back to top |
|
|
|