- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I am compiling a program which calls IMSL routines. When launching the debugger (F5 or Ctrl-F5), the IDE asks me to rebuild the project even if it has just been built. For projects without IMSL calls, I do not have this problem. Can someone tell me what's going on? Thanks.
Mao
Mao
Link Copied
5 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I've never seen this particular problem before, at least not triggered by using IMSL. Is this CVF or IVF? Are you USEing the IMSL modules or doing it "F77 style"? Are the IMSL files installed on a network share?
Try this. Do a Build..Clean on your project/solution. Remove one source file from your project and add it back in. Do a Rebuild. See if that helps.
Try this. Do a Build..Clean on your project/solution. Remove one source file from your project and add it back in. Do a Rebuild. See if that helps.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Steve:
I try the steps you suggested. It did not work!
1. I am using IVF 8.1 under MS .NET 2003.
2. The project is simple; it contains only one source file. 3. The program calls an IMSL routine, RCURV, in F77 style. The Property/Linker/Input option is $(LINK_F90). The project is successfully built, but the IDE still asks me to rebuild the project everytime I try to "Start without Debugging" (Ctrl-F5).
4. The IMSL files are located in my local system.
Any thoughts? Thanks.
Mao
I try the steps you suggested. It did not work!
1. I am using IVF 8.1 under MS .NET 2003.
2. The project is simple; it contains only one source file. 3. The program calls an IMSL routine, RCURV, in F77 style. The Property/Linker/Input option is $(LINK_F90). The project is successfully built, but the IDE still asks me to rebuild the project everytime I try to "Start without Debugging" (Ctrl-F5).
4. The IMSL files are located in my local system.
Any thoughts? Thanks.
Mao
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I would not have thought that $(LINK_F90) works. Try adding the following line to one of your sources:
include 'link_f90_static.h'
include 'link_f90_static.h'
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I see this same effect without using IMSL at all in the project. The project has numerous files, with both C++ and Fortran in the solution. Yet, every time I do "build solution", it wants to recompile the same set of 6-8 files from the IVF project, even if I just did!
One of the files being recompiled contains only the code for one module, and it seems the timestamp of the resulting .mod file is always very late in the build process. This could explain why some other .for files depending on that module got recompiled the next time around. However, at least one of the .for files being recompiled does not depend on this module at all!
I don't know if this information is of any help, but it seems something is wrong with this Studio .NET integration in IVF 8.1.30 at least.
Any ideas?
Regards, -+-Ben-+-
One of the files being recompiled contains only the code for one module, and it seems the timestamp of the resulting .mod file is always very late in the build process. This could explain why some other .for files depending on that module got recompiled the next time around. However, at least one of the .for files being recompiled does not depend on this module at all!
I don't know if this information is of any help, but it seems something is wrong with this Studio .NET integration in IVF 8.1.30 at least.
Any ideas?
Regards, -+-Ben-+-
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I doubt it's a problem in the IDE integration, but please create a ZIP of your project, including the .mod files generated, and submit a support request to Intel Premier Support so that we can look at it. It would also be very helpful if the buildlog.txt from a recent rebuild was included.

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