Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.

"Build Log" Location

michael_m2
Novice
1,065 Views

Hello:

In the project settings, is there a way to specify the location of the Build Log (BuildLog.htm)? What about changing the name of this file?

Thanks.

0 Kudos
5 Replies
Steven_L_Intel1
Employee
1,065 Views
I'm not aware of a way to specify or change this. The log is placed in the "intermediate output" folder for the configuration (typically Release or Debug).
0 Kudos
michael_m2
Novice
1,065 Views

In the Property Pages of the project, there are two separate directories (under "Configuration Properties...General): "Output Directory" and "Intermediate Directory". I'm not sure which you meant when you said "Intermediate Output", but it looks like the real one that controls where the BuildLog.html goes is the "Output Directory".

I was hoping to get around the limitation of not being able to directly specify where the log file goes by playing around with the "Supported Build Macros", but it looks like the "Output Directory" and the "Intermediate Directory" do not accept these macros. Do you know if that's a bug or if they're supposed to not accept the macros?

Thanks again.

0 Kudos
Steven_L_Intel1
Employee
1,065 Views
Right, it's Output Directory. Output Directory itself defines a macro, $(OUTPUT). This is all Visual Studio stuff not under our control, you may want to peruse the Microsoft documentation on using VS to see if there's something there for you.

Perhaps I don't understand your last post - you can change the output directory. How would you use build macros here?
0 Kudos
michael_m2
Novice
1,065 Views

Sorry for being unclear. What I meant is that I was hoping to use the build macros such as $(SolutionDir)$(ConfigurationName) to set the "Output Directory". But when I tried that I found that VS did not expand those macros, it just used them as literal strings.

0 Kudos
Steven_L_Intel1
Employee
1,065 Views
You weren't unclear - I don't know why VS doesn't recognize macros there.
0 Kudos
Reply