Why does my release driver binary includes full path to source and pdb?

Discussion in 'Windows Vista Drivers' started by Tom V S, Feb 19, 2004.

  1. Tom V S

    Tom V S Guest

    I am builing a release driver using XP DDK 2600 free build environment. The
    driver binary includes a full path to the pdb and source files (to all
    source files and not headers). I don not want these to be included into the
    release build. Its fine if its a debug build. Drivers found user under
    windows\system32\drivers doesnt include these info, I assume that these are
    also built using the same DDK which I am using. Why is the difference? How
    can I get rid of this? Thanks.

    # Target name and type
    TARGETNAME=Uucf1894
    TARGETPATH=obj
    TARGETTYPE=DRIVER

    !IF "$(DDK_TARGET_OS)" == "WinXP" || "$(DDK_TARGET_OS)" == "Win2K"
    # XP/Later DDK build env being used
    !IF "$(DDKBUILDENV)" == "chk"
    NTDEBUG=ntsd
    NTDEBUGTYPE=both
    !ELSE
    NTDEBUG=ntsdnodbg
    NTDEBUGTYPE=both
    !ENDIF
    !ELSE
    # Win2k DDK build env being used
    !IF "$(DDKBUILDENV)" == "checked"
    NTDEBUG=ntsd
    NTDEBUGTYPE=both
    !ELSE
    NTDEBUG=ntsdnodbg
    NTDEBUGTYPE=both
    !ENDIF
    !ENDIF
    # for assembly listings
    USER_C_FLAGS = /Fc

    # for PDB
    USE_PDB=1

    USE_MAPSYM=1
    BROWSER_INFO=1

    SOURCES=Uucf1894.cpp \
    Uuioctl.cpp \
    UuPwr.cpp \
    Uucf1894.RC
     
    Tom V S, Feb 19, 2004
    #1
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.