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.
29285 Discussions

No .exe file output

royxu
Beginner
‎01-31-2007 03:37 PM
581 Views
Hello,
I tried to find .exe file after successfully building my project but not found.
Here is the message after building project:

1>------ Build started: Project: version2ewoc, Configuration: Debug Win32 ------
1>There is no build command line to execute.
1>
1>Performing Makefile project actions
1>Build log was saved at "file://c:Documents and SettingsRoyVisual Fortranversion2ewocDebugBuildLog.htm"
1>version2ewoc - 0 error(s), 0 warning(s)
========== Build: 1 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========

I checked Project->Properties->Configuration Properties->General and found the output directory is .Debug. I should find .exe file in that directory. Do I miss something here?
Thanks for any input!

Roy
0 Kudos

Link Copied

1 Reply
Steven_L_Intel1
Employee
‎01-31-2007 04:48 PM
581 Views
It sounds as if this is not a Fortran project. Is there a blue box with a white F next to the Fortran project name? Did you convert this from a CVF project? If so, you seem to have missed the second step which is to right click on the project and select "Extract Compaq Visual Fortran Project Items".
0 Kudos
Copy link
Reply

Community support is provided Monday to Friday. Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.