Suppress import library creation - Visual C++ linker

Question

Is there, a perhaps undocumented way to prevent linker from creating IMPLIB for a DLL or an EXE, despite having __declspec(dllexport) directives within the source code?

Specifying no /IMPLIB results in .LIB created with a default name.

This is important when the declspec directives arrive from 3rd party code which is not under control. This is, for example, the case with boost::serialization. A possible solution would be a way to "undeclare" a DLL export. DEF file also cannot do it (AFAIK), because it can only add to the export list but not remove from it.

Can't you just delete it if you don't need it? What's the real problem? — Bo Persson, Apr 02 '12 at 16:27
The real problem is the time it takes the linker to make these (developer productivity optimization in a large firm) — Pavel Radzivilovsky, Apr 03 '12 at 15:33

score 1 · Accepted Answer · answered Mar 03 '13 at 16:44

Many 3rd party code does not use __declspec(dllexport) directly, but hides it under a macro in order to control it. Typically they want to switch between dllexport and dllimport depending on where the header file is included (inside the dll implementation or by the user of the dll)

If that is the case in the library you try to include it should not be too difficult to alter this behavior via macro manipulation to meet your exact needs.

For example, boost::serialization check the config.hpp and see how you can control it.

score 1 · Answer 2 · answered Mar 03 '13 at 22:20

There is not any way to do this with a linker option, using /implib:"nul" fails miserably when the linker uses it to name the .exp file. The most practical solution is to remove the files again after a build. Project + Properties, Build Events, Post-Build event and paste:

del $(TargetDir)$(TargetName).lib
del $(TargetDir)$(TargetName).exp

enter image description here

score 1 · Answer 3 · answered Mar 05 '13 at 01:18

1

Using a .def file containing your exported functions marked with the PRIVATE keyword will tell the linker to skip placing the symbol in your import library.

Refer to this MSDN page for more information about MSVC's .def file syntax.

answered Mar 05 '13 at 01:18

Eddy Luten

432
2
11

1

Still creates the .lib and and .exp files though. – Andreas Haferburg Jan 27 '15 at 10:25

score 1 · Answer 4 · answered May 25 '22 at 15:30

1

Nowadays, you can use /NOIMPLIB and /NOEXP in the advanced linker options as per this bug ticket. Works for me on Visual Studio 2019.

answered May 25 '22 at 15:30

Krishty

164
12

score 1 · Answer 5 · answered Apr 02 '12 at 20:33

1

According to this, if you supply the .exp file when linking, the linker will not create a .lib file. To be honest, though, I can't tell if this helps in your case.

answered Apr 02 '12 at 20:33

irobot

1,026
1
6
13

I wonder if it is possible to create an empty EXP file to supply it. – Pavel Radzivilovsky Feb 28 '13 at 16:35

Suppress import library creation - Visual C++ linker

5 Answers5