- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Is it still impossible to compile separate (.f90) files in IVF? I recall this was the case in the previous versions and was hoping was fixed...
Pressing the compile button doesnt seem to do anything, nor does right-clicking on a file in solution explorer.
In fact if I then try to exit the compiler I get an "unknown windows error" which kills it first.
I am using "w_fc_pc_8[1].1.025.exe", which as far as I can understand is the latest version?
is this expected behaviour??
many thanks
Pressing the compile button doesnt seem to do anything, nor does right-clicking on a file in solution explorer.
In fact if I then try to exit the compiler I get an "unknown windows error" which kills it first.
I am using "w_fc_pc_8[1].1.025.exe", which as far as I can understand is the latest version?
is this expected behaviour??
many thanks
Message Edited by forall on 01-31-2005 02:53 PM
Link Copied
14 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
No, that is not expected behavior. I use the "compile single file" feature all the time. Right click on the file in the solution view and select Compile.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Steve,
thanks for the fast reply.
ok, this is what happens:
* if I click on compile button on the toolbar, definitely nothing happens;
* For a static library project originally created using an older version of IVF, if I right click on file > compile, it does work (although it gives no noticeable 0 errors diagnostic, which is why I thought it didnt work originally). However if I then close the solution or exit VS, an unknown unhandled exception brings down VS.
* If I create a new project from scratch it allows me to compile single file, and also shut down without errors (but I tried it with a single-file library, whereas the old one contained about 40 files) which is good.
so far looks promising - thanks.
thanks for the fast reply.
ok, this is what happens:
* if I click on compile button on the toolbar, definitely nothing happens;
* For a static library project originally created using an older version of IVF, if I right click on file > compile, it does work (although it gives no noticeable 0 errors diagnostic, which is why I thought it didnt work originally). However if I then close the solution or exit VS, an unknown unhandled exception brings down VS.
* If I create a new project from scratch it allows me to compile single file, and also shut down without errors (but I tried it with a single-file library, whereas the old one contained about 40 files) which is good.
so far looks promising - thanks.
Message Edited by forall on 01-31-2005 03:39 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Strange - haven't seen that behavior before... The Compile from the toolbar works for me when a Fortran file is the selected file. I don't recall seeing errors from VC.NET after a compile, either. Are there any details in the error message?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Steve, here is a screenshot of the error.
I can compile a single file using
* right click on file in solution explorer
but not using
* the toolbar button, nor
* the pulldown build menu compile button, nor
* CTRL-F7
regardless of whether file is open. I test this using a simple .f90 file with a syntax error, and only rightclicking generates some error info. the other options just do nothing.
I can compile a single file using
* right click on file in solution explorer
but not using
* the toolbar button, nor
* the pulldown build menu compile button, nor
* CTRL-F7
regardless of whether file is open. I test this using a simple .f90 file with a syntax error, and only rightclicking generates some error info. the other options just do nothing.
Message Edited by forall on 01-31-2005 04:26 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Interesting. Please submit this to Intel Premier Support - include the data collected from the error message and a zip of your solution folder.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
as it turns out the newly built project also starts crashing VS, when I add a bunch more files into it (even if I compile some the same non-problematic file).
Also, does this message mean anything (appears when rebuilding):
warning: module 'debugmod1.mod' is created by both 'file1.f90' and 'inc1.f90'.
Note that module mod1 is defined in the include file 'inc1.f90' that is included into 'file1.f90'. Note that inc1.f90 is NOT added to any project - it just sits in the directory. There is a reason for this construction (inc1.f90 contains OS-specific instructions and is swappable with Win/Linux, etc) and it worked fine in CVF.
Also, does this message mean anything (appears when rebuilding):
warning: module 'debugmod1.mod' is created by both 'file1.f90' and 'inc1.f90'.
Note that module mod1 is defined in the include file 'inc1.f90' that is included into 'file1.f90'. Note that inc1.f90 is NOT added to any project - it just sits in the directory. There is a reason for this construction (inc1.f90 contains OS-specific instructions and is swappable with Win/Linux, etc) and it worked fine in CVF.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I would not expect to see that if inc1.f90 was not listed under "source files" in the project. You may have a corrupted .vfproj file. I would encourage you to submit this to Premier Support.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
well, it seem fortunate the bug persisted right to the very simplest f90 code. Before I submit it, can people check if they get a windows error as follows: open the solution > right click compile on kinds.f90 and then close solution. in the fuller version of the bugged code, the error appeared in other circumstances as well, but in the cutdown it only happens as described.
the code is so simple it makes me think its a problem with my VS installation (a very fresh one, btw).
the code is so simple it makes me think its a problem with my VS installation (a very fresh one, btw).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I can reproduce it. So please send this to Premier Support with the instructions - be sure to specify that the file to try to compile is kinds_dmsl_kit.f90, not kinds.f90.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
submitted as Issue 287650. Note that I couldnt find a 'submit' button after uploading the files, so it wasnt 100% obvious whether the issue loaded. but I *think* it did.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I reported the toolbar compilebutton problem ages ago; still awaiting resolution...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes, I can see your report, Neal. It is being investigated. Thanks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
So are the 'compile toolbar button', 'CTRL-F7' and 'compile menu item' (as opposed to rightclick-compile on file in solution explorer) supposed to work correctly in the current IDE? Some posts suggest they are, others (see above) dont? It will save me submitting redundant bug reports. thanks
Message Edited by forall on 02-02-2005 01:05 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Button and Ctrl-F7 and build menu option do not work for me (latest download) and I reported it last year. Not serious, but inconvenient....

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