Since MFC 3.0 (which shipped with Visual C++ 2.0, decades ago) it has
been unnecessary to specify the MFC library in the link line; the
headers can magically add the right one. Guessing the MFC version
from $(VISUALSTUDIOVERSION) does not work with Visual Studio 2017 (we
guess 150; the correct value is 140).
ticket: 8678 (new)
AFS_LIBS=
!endif
-!if defined(VISUALSTUDIOVERSION)
-MFC_VERSION=$(VISUALSTUDIOVERSION:.=)
-!else
-MFC_VERSION=100
-!endif
-
-!if defined(NODEBUG)
-MFCLIB=MFC$(MFC_VERSION).LIB
-!else
-MFCLIB=MFC$(MFC_VERSION)D.LIB
-!endif
EXE_NAME=leash
WSHELPER=wshelp32
$(OUTPRE)$(EXE_NAME).exe: $(OBJS) $(XOBJS) $(LIBS)
$(LINK) $(LFLAGS) /out:$@ /ENTRY:WinMainCRTStartup $(OBJS) $(XOBJS) \
$(LIBS) $(SYSLIBS) $(BUILDTOP)\util\wshelper\$(OUTPRE)$(WSHELPER).lib \
- ../lib/$(OUTPRE)libwin.lib $(MFCLIB) $(SCLIB)
+ ../lib/$(OUTPRE)libwin.lib $(SCLIB)
copy $@ "$(OUTPRE)MIT Kerberos.exe"
kfwribbon.bml kfwribbon.h kfwribbon.rc: kfwribbon.xml