Jacek Ławrynowicz
Jacek Ławrynowicz

Reputation: 2700

Why is lib.exe removed from recent WDK releases?

Is this a bug? Visual studio 2008 build system uses lib.exe to create static libraries. I setup build environment with WDK's setenv.bat and then start devenv.exe /USEENV. Building user-mode programs and dlls works, but due to missing lib.exe static library can't be built.

Upvotes: 1

Views: 859

Answers (2)

Hans Passant
Hans Passant

Reputation: 941873

These are the crucial bits in the WDK makefile:

!ifndef LIB_NAME
LIB_NAME=$(LINK_NAME) /lib
!endif

LIBRARIAN=$(LIB_NAME) /out:$@ $(LIBRARIAN_FLAGS)

!ifndef LINK_NAME
LINK_NAME=link.exe
!endif

In other words, lib.exe {options} == link.exe /lib {options}

Upvotes: 1

snoone
snoone

Reputation: 5499

The lib.exe functionality has been moved into link.exe, type link.exe /lib for details (you should get the same help as you would if you had just run lib.exe from the SDK).

-scott

Upvotes: 8

Related Questions