Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.

import library not generated

abhimodak
New Contributor I
545 Views

Hi

With 11.1.054 on WinXP64 with VS2005, I am seeing that the import library is not generated if I use project type as "DLL with sample code". Using "DLL" as project type and then adding a file by Add existing item or adding a new file does generate the corresponding .LIB.

I can see that under Project --> Properties --> Linker --> Advanced --> Import Library is set to $(TargetDir)$(TargetName).lib and that the command line and the build-log show /IMPORTLIB:complete file path in all cases. Yet, the import library is NOT generated when project type is "DLL with sample code".

Has this happened to anyone else or it is just my computer/settings?

Abhi

0 Kudos
4 Replies
IDZ_A_Intel
Employee
545 Views

Generating the .LIB requires a DLLEXPORT directive in the routine to be exported. If you don't have this, or it is incorrect, you won't get the .LIB. The options you mention have no effect on this.

0 Kudos
abhimodak
New Contributor I
545 Views

I am quite sure that the DLLEXPORT is there since the "sample code" automatically puts it.

Abhi

0 Kudos
abhimodak
New Contributor I
545 Views

I restarted the Visual Studio and I see the .LIB generated. To check, I used the same project (which indeed had DLLEXPORT in it) and also created a new project from scratch. Both are creating .LIB as expected. May be I had messed up the /IMPORTLIB: path when I touched that switch and changed the default $(Targetlib).. etc.

This would make it put the library in the other path, wouldn't it?. What happens if this path does not exist (although I don't think it was the issue in this case)?

Abhi

0 Kudos
IDZ_A_Intel
Employee
545 Views
I don't know what happens if the path doesn't exist. It probably creates it.
0 Kudos
Reply