- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
I have run into a curious and ultimately nasty problem building a DLL:
When I build using the Release configuration I get a DLL that depends on such libraries
as libifcoremd.dll and others - even though I did not change any default options wrt
the runtime libraries and so on.
I have checked the properties of the project, but I can not find the reason for
these dependencies. In the object files I clearly see default libraries such as libifcoremd.dll,
but in a very similar project I do not see them.
Any idea what I can do about this?
Here are some details:
- I am using Developer Studio 2008 with Intel Fortran 11.1
- The error message during linking is:
Regards,
Arjen
I have run into a curious and ultimately nasty problem building a DLL:
When I build using the Release configuration I get a DLL that depends on such libraries
as libifcoremd.dll and others - even though I did not change any default options wrt
the runtime libraries and so on.
I have checked the properties of the project, but I can not find the reason for
these dependencies. In the object files I clearly see default libraries such as libifcoremd.dll,
but in a very similar project I do not see them.
Any idea what I can do about this?
Here are some details:
- I am using Developer Studio 2008 with Intel Fortran 11.1
- The error message during linking is:
libifcoremd.lib(for_main.obj) : error LNK2001: unresolved external symbol _MAIN__
..\\..\\bin\\Release\\dlwqlib.dll : warning LNK4088: image being generated due to /FORCE option; image may not run
The DLL is produced, however, and the summary says the project was successfully built
(even though two errors are reported).
Regards,
Arjen
Link Copied
2 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
libifcoremd.lib is not a debug library. But it seems your project is building as a console application. I suggest you carefully compare the project options between the two confiigurations.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Ah, it was the trailing "d" that made me think that.
I found the cause though, after, indeed, a careful inspection of the options in both projects: we were using the /force option to force a DLL. Without it we got errors about duplicate symbols in msvcrt.lib. By removing
the /force option and ignoring msvcrt.lib it now works without any complaints.
Regards,
Arjen

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