Incorrect platform for Release configuration used by compiler

[jirina]

I am using Intel Compiler XE 2011, Update 2, and Visual C++ 2008 Professional, on Windows 7 Professional, 64-bit. The problem I have is following:
- If I select Debug configuration from the list in the Standard toolbar, the compiler takes into account also the selected platform (I have Win32 and x64).
- If I keep the Win32 platform and change the configuration to Release, the compiler does its job for Release x64 (I can see this in the window Output).
- The only way to compile Release Win32 is to use the menu item "Build - Batch Build..." and check the Release Win32 configuration.

Is there anything I can do to make the compiler take into account changes of the platform for the Release configuration?

[Steven_L_Intel1]

This isn't the "compiler", but Visual Studio, and my guess is that you have not correctly added the x64 configuration. In the toolbar, there are separate dropdowns for Debug/Release and Win32/x64. Typically if you change the platform to x64, you can switch back and forth between Debug and Release without issue.

Please attach the .vfproj file for your project so that I can look at it.

[jirina]

I admit I might have done something wrong when adding the x64 configuration even though it looked easy and straightforward. My problem is that Visual Studio ignores the drop-down for the platform when Release is selected in the first drop-down - x64 it used when either Win32 or x64 are selected.

Attached is my project's .vfproj file, thank you for checking it.

[Steven_L_Intel1]

You have a whole bunch of configurations in there - which ones are you using? I see one labeled "Release x64" which doesn't make a lot of sense to me. Can you show me a build log (buildlog.htm) with the wrong build type?

Did you make any changes in Tools > Options > Intel Visual Fortran > Compilers?

[jirina]

I use all of them for various purposes; however, I use Release and Debug, for both Win32 and x64 platforms, most frequently.

Indeed, I can see "Release x64" too in the file, even though it is not included in the correspoding drop-down. The question is whether this could be the cause of my problem and whether it can be manually removed from the project file.

I did not modify settings in Tools > Options > IVF > Compiler; they are the same since I installed Update 2.

My build logs are quite old files, so I deleted them, and I am not able to find in help or options how to enable generating buildlog.htm; am I overseeing something? It feels like buildlog.htm is not created (I created a completely new project and buildlog.htm does not get created, even though Build Log File parameter in General options is set to $(IntDir)\BuildLog.htm and $(IntDir) should be the value of the parameter Intermediate Directory, which is $(Configuration Name).

[Steven_L_Intel1]

If you are building a Fortran project, there will always be a buildlog.htm in the configuration subfolder (Debug, Release, etc.)

[jirina]

I must then be doing something wrong - I checked the contents of corresponding subfolders and there is no buildlog.htm file. I can only see *.obj, *.res, mainfest-related files and the executable. I tried rebuilding and made sure the contents of the corresponding subfolder had been deleted; buildlog.htm not appearing.

I am sure buildlog.htm was created by Update 1, so something must have happened since the time I uninstalled Update 1 and installed Update 2, maybe Microsoft Updates to Visual Studio? Let me try reinstalling Update 2 if it helps - OK, it seemed not to help, but I found out that there is an option in Tools > Options > IVF > General to Generate build logs, and this option was not checked.

So, you can find attached the build log from the compilation and linking when Release and Win32 are selected - the platform actually used is still x64.

[Steven_L_Intel1 · Accepted solution]

The log suggests that it thinks it is building a Release X64 configuration. I know it may be annoying, but perhaps it would be best at this point to create a new project, add the sources and work from there.

[jirina]

I will probably do that; it will take some time and effort, but it should resolve the problem.

Thank you for your help.