- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Sometimes whole project stops compiling,
and marks every "use" statement as a separate error of look:
"error #7002 Error in opening compiled module file. Check INCLUDE paths. [..moduleName..]"
Tried checking include paths, added additional paths in the building directory and source files directory
Tried cleaning solution, manually cleaning generated files (.mod, .obj, etc..)
Nothing has really helped.
The only way to fix it is moving back to the last development version completely and copying text, hoping that it wont break again, and usually it is completely fine after just retracing all the updates. That is until it happens again
What is known about possible reason for it to occur:
1) some files being changed (added/removed), changing path to files (removing file and adding existing file on visual studio)
2) switching between debug / release modes. (debug mode doesn't use OMP, release uses OMP)
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
1] Do a clean build.
2] Look at the very first error produced, is the module USEed in one of the files compiled before the first error? If not then it is compile order.
3] If it was compiled do the .mod and .obj files exist, where are they?
This will give insight into the nature of the problem.

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