unhelpful diagnositc message

[YertleTheTurtle]

Hi:

For someone at Intel's attention:

Using VS, with fpp, if a program has a statement of the form

#include "a.f90"

and the file named "a.f90" doesn't exist, or can't be found, you willreceive a very puzzling error message:

".... error PRJ0019: A tool returned an error code"

You might want toturn this into a more useful diagnostic.

[abhimodak]

I think "Tool returned an error code" also appears when something similar (that file does not exist) happens in a post-build event, for example, file copy.

Abhi

[jimdempseyatthecove]

At the bottom (build output window) you will see

... Build Log bla bla bla .html

Open that up to see error (right click or is it shift click?)

Jim Dempsey

[mecej4]

That's the MS VisualStudio IDE, acting as a middleman and replacing the errors messages given by the compiler by something blander. So your complaint should be aimed at Microsoft rather than Intel.

There is an option to produce a build log. Enable it. Then, after a failed build, do CTRL-click on the link to the log-file, and the file will be opened up in an editor tab.

[Wendy_Doerner__Intel]

Yes Jim is correct, check the build log for the actual error. We have an FAQ on this error to point people to the build log. Not sure if we can give a better message or this comes from Microsoft Visual Studio, though. I am looking into it.

------

Wendy

Attaching or including files in a post