- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Say I have two fortran projects, called A and B for example, within a single master solution. Project B depends on a module contained in project A. If I set project A as a dependency of project B, then it correctly builds A before it builds B and during the linking stage, it has no problem finding the library that was built by project A. However, the problem is that when I am compiling project B, it complains about not finding the .mod file built by project A even though it was already built and is located (by default) in the same directory as the library file that was built (Debug). Now, I understand that I can manually add the path to the .mod file in the settings for project B, but what I don't understand is why I should have to do that since I already established the dependency. Shouldn't it "just know" to look in the output directory of project A to find the .mod file that it needs just like it does to find the corresponding .lib file?
If I only had two porjects, this would not be much of a problem, but I actually have hundreds of projects in my solution with complex dependencies among them. Currently, I am having all the projects dump their .mod files into a single directory called /mods and then including that directory manually within each project. This just seems cumbersome and unecessary if I have already established the correct project dependencies. It this the way it is is supposed to behave or am I doing something wrong?
Chuck
If I only had two porjects, this would not be much of a problem, but I actually have hundreds of projects in my solution with complex dependencies among them. Currently, I am having all the projects dump their .mod files into a single directory called /mods and then including that directory manually within each project. This just seems cumbersome and unecessary if I have already established the correct project dependencies. It this the way it is is supposed to behave or am I doing something wrong?
Chuck
Link Copied
2 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It is behaving as it is "supposed" to, but I fully agree that it would be preferable if the INCLUDE path from dependent projects was also merged in. My guess is that this was not considered because, otherwise, project dependencies are handled entirely within the generic Visual Studio shell and not with language interaction.
I would suggest that you file a Feature Request with Intel Premier Support asking for the module output paths of dependent projects were added to the INCLUDE path of the parent.
I would suggest that you file a Feature Request with Intel Premier Support asking for the module output paths of dependent projects were added to the INCLUDE path of the parent.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thank you very much for your reply. I just wanted to make sure I wasn't overlooking anything obvious. I will file that feature request.
Chuck
Chuck
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