- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Our current development is IVF 9.1.028 with VS 2003 under Windows XP. I have now been asked to install VS 2005 (to run in parallel with existing development environment) to identify and fix any code problems before the remainder of our department install 2005.
I UNinstalled the IVF integration. Then installed VS2005 and the VS2005 SP1 (after some problems running out of disk space! - whatever happened to the days of software fitting on one or two floppies :-(
I copied our source tree to a new directory. We have many mixed language solutions previously converted from VS6 and CVF so I chose one. When I right mouse click on the solution file (still version 7.1) I get a choice to open with "Microsoft Visual Studio Version Selector", "Microsoft Visual Studio .NET 2003" and so on.
Choosing the "Version Selector" does _not_ ask me to choose which version which I expected, but instead goes straight into VS2003. So I chose to browse and went to the 2005 version of devenv.exe. This then enters the conversion wizard, and tells me it is ready to convert and in the summary it says it is converting solution "util" but under projects there is nothing! I click on Finish and the next panel tells me Conversion Complete - all projects converted successfully. So I click Close.
The conversion log tells me thatthe solution util has been converted that project util.vcproj has been converted but nothing about the vfproj!
In the solution explorer window I see both projects ('util' the C project, and 'util_lib' the Fortran project) All of the Project settings and Build options imply that the Fortran project is visible and active. Clicking "Build / Batch build/ Rebuild" the fortran and c source files are compiled ok,
for the Fortran files I get a message
Command line warning: overriding '/Qvc7.1' with '/Qvc8'
which I can't seem to find and fix.
More problematicallythe build does not combine the lib from the Fortran build with the lib from the C build and so further down the chain I get unresolved errors for calls to the Fortran routines.
Any ideas what I've done wrong / settings missed etc?
Thanks for any help
Les
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
For the warning, edit C:Program FilesIntelCompilerFortran9.1IA32Binifort.cfg and change the line:
-Qvc7.1
to:
-Qvc8
Whileyou're there, change the path to the linker to be that of VS2005. Reinstalling the Intel Fortran compiler will also give you the opportunity to select VS2005 as the command line default, which this affects.
Regarding the library combining, this is a VS2005 bug fixed in VS2005 SP1.
That "Version Selector' is a bit of a pain, isn't it? What it does is open the project in the version of VS that created it. Alternatively, you could have opened VS2005 and then opened the solution - it would then have converted it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks Steve.
Editing ifort.cfg fixed the compile message. (Never thought to look there, I went through all the Project Settings several times)So it seemsmy problems started when I only went through the integration option rather than installing the Fortran compiler from scratch.
I did installthe SP1 after installing VS2005 and then I did the integration, but after doing the above changes I'm still not getting the combined C and F90 lib Looks like I shall have to rewind week and start again :-(
Les
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yey I've found it!
All the dependencies were set okBUT, for the C project, under Settings / Librarian / General the option "Link Library Dependencies" was set to No !
Not sure why that was. After various re-installs I always copied the oldproject files (from my 2003 source tree)over to the 2005 source tree in order to do the convert from 2003 to 2005.
Anyway that's one for you to write in your little black book of "Problems with VS2005" to warch out for.
Thanks for the help.
Les
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content

- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page