How I understand, it's senseless to install IVF on Windows 64 bit system, because impossibility to have integration with MS Visual Studio. Visual Studio Net 2003 dowsn't install, and Visual Studio 2005 doesn't supported. Is that correct?
链接已复制
18 回复数
Um, no, it's not senseless. You can use the 64-bit compiler from the command line with the Microsoft Platform SDK providing the prerequisite libraries and tools.
VS2003 does install (it didn't during a beta of Windows x64), but it is a 32-bit environment. With some fiddling you can use this to edit and build (but not debug) 64-bit applications on Windows x64.
VS2003 does install (it didn't during a beta of Windows x64), but it is a 32-bit environment. With some fiddling you can use this to edit and build (but not debug) 64-bit applications on Windows x64.
Thank you,I checked it, and VS doesn't install on Microsoft Windows [Version 5.2.3790] (Windows XP 64 Pro). But I can't recognize what the version VS I have. Setup writes "Unable to install Visual Studio .NET on a 64-bit operating system".
Command prompt isn't interesting. Could you say time when VS2005 will be completely supported?
I don't know which version of XP 64 you are using (I don't have the build numbers committed to memory), but VS2003 does install on the released version. I've verified this.
I can't talk about "when", but the version with VS2005 support has just entered beta test.
I can't talk about "when", but the version with VS2005 support has just entered beta test.
Yes, my version of VSwas wrong,. Now I installed another one, but still have no integration IVF into VS. Last version of Microst SDK is installed too. Unic possible on my look reason is that ??? was installed earlier. But I can deinstall all features of IVF, except integration, So,any advise will be appreciated.
You will need a version of Intel Visual Fortran at least 9.0.021 in order to allow the integration into VS.NET of the 32-bit compiler on an x64 system. There is no support in 9.0 for 64-bit compiler integration into VS - that will come in a future version and for VS2005 only.
You can manually change the directory paths used by VS2003 to reflect the 64-bit compiler, libraries and tools rather than 32-bit.
You can manually change the directory paths used by VS2003 to reflect the 64-bit compiler, libraries and tools rather than 32-bit.
There are two approaches you can take:
1. Open a "Fortran Build Environment for EM64T-based applications" window and type:
devenv /useenv
This will cause VS.NET to use the values of PATH, LIB and INCLUDE from your session and set the paths.
2. Manually edit the paths in Tools..Options..Intel Fortran..General..Directories to reflect the folders with the EM64T files.
Some people find that they have to manually add /machine:amd64 to the linker command line options, but it seems to depend on which version of the MS files you have installed.
Keep in mind that the compiler options will all reflect IA32, so be careful what you set using the UI. You can add manual options as needed.
1. Open a "Fortran Build Environment for EM64T-based applications" window and type:
devenv /useenv
This will cause VS.NET to use the values of PATH, LIB and INCLUDE from your session and set the paths.
2. Manually edit the paths in Tools..Options..Intel Fortran..General..Directories to reflect the folders with the EM64T files.
Some people find that they have to manually add /machine:amd64 to the linker command line options, but it seems to depend on which version of the MS files you have installed.
Keep in mind that the compiler options will all reflect IA32, so be careful what you set using the UI. You can add manual options as needed.
I have the following:
Windows Application Debugger for Intel EM64T-based applications, Version 9.0-
12, Build 20050730
(idb) devenv /useenv
The "/" command has failed because there is no running program.
12, Build 20050730
(idb) devenv /useenv
The "/" command has failed because there is no running program.
Does it means that I should use newer version of compiler?
I did not say to start idb. The shortcut I meant was Start..All Programs..Intel Software Development Tools..Intel Fortran Compiler 9.0..Build Environment for Fortran EM64T-based Applications. You type the devenv command at the command prompt.
On some systems, PATH may not be set up to include the location of devenv.exe. If that's the case for you, specify the full path.
On some systems, PATH may not be set up to include the location of devenv.exe. If that's the case for you, specify the full path.
Sorry, Steve, I was wrong. But Now I have:
Intel Fortran Compiler 9.0.024 build environment for EM64T-based applications
Copyright (C) 1985-2005 Intel Corporation. All rights reserved.
Targeting Windows Server 2003 X64 RETAIL
C:Documents and SettingsAdministrator>devenv /useenv
'devenv' is not recognized as an internal or external command,
operable program or batch file.
'devenv' is not recognized as an internal or external command,
operable program or batch file.
So, I have no right VS environment too. I'll be check it.
P;ease file a support request with Intel Premier Support regarding your inability to uninstall the integrations. We can help you through that channel. I suspect that it needs to be uninstalled and reinstalled so it can be seen.
