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

Debug build goes straight to linker and fails

nvaneck
New Contributor I
586 Views

I edited a few routines, and now when I build, rebuild, clean and rebuild, empty the debug directory in debug 32bit it starts the linker and complains:

Compiling resources... Rc /fo "Debug/Osir.res" "D:\Projects\MicrOsiris\INCLUDE\Osir.rc" Microsoft (R) Windows (R) Resource Compiler Version 6.1.7600.16385 Copyright (C) Microsoft Corporation. All rights reserved. Linking... Link /OUT:"Debug/MicrOsiris.exe" /VERSION:19 /INCREMENTAL:NO /NOLOGO /MANIFEST:NO /DEBUG /PDB:"Debug/MicrOsiris.pdb" /SUBSYSTEM:WINDOWS /OPT:REF /IMPLIB:"D:\Projects\MicrOsiris\Debug\MicrOsiris.lib" mkl_lapack95.lib mkl_intel_c.lib mkl_sequential.lib mkl_core.lib "Debug/Osir.res" Link: executing 'link' LINK : warning LNK4068: /MACHINE not specified; defaulting to X86 LINK : error LNK2001: unresolved external symbol _WinMainCRTStartup Debug/MicrOsiris.exe : fatal error LNK1120: 1 unresolved externals MicrOsiris - 2 error(s), 1 warning(s)

Everything works fine for relase mode in 32bit, relaease mode in 64bit, and debug in 64 bit mode.  Indivdual files compile ofin all modes.

I changed nothing in project properties.  What happend, and how can I fix it?

 

Thanks

0 Kudos
2 Replies
SergeyKostrov
Valued Contributor II
586 Views
>>...I changed nothing in project properties. What happend, and how can I fix it? Could you provide *.sln and *.vfproj files of the project for review? It is Not clear what is going on and it looks like simple project configuration issue.
0 Kudos
nvaneck
New Contributor I
586 Views

Thanks! In looking to upload those files, I noticed an extra file decided to close and open the solution, and the problem went away.  Something must have been corrupted.... Should have tried that first...

0 Kudos
Reply