RE: DDK build result different from VS result
From: Hannes (hannes_at_nospam.nospam)
Date: 02/01/05
- Next message: Pavel A.: "Re: SDK String API use at Kernel level"
- Previous message: Pavel A.: "Re: WPA2 Support???"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 31 Jan 2005 17:19:01 -0800
Hi again,
Thanks for the tip from Mark Roddy of looking through the included
makefiles, to find out why certain compiler flags are added to my
compilations. I have now stripped my sources file down significantly, and I
am left with these few 'extras' in there:
TARGETNAME=spm
TARGETPATH=obj
TARGETTYPE=DRIVER
C_DEFINES=-DNDIS50_MINIPORT -DNDIS50 -DNDIS_MINIPORT_DRIVER -DNDIS_WDM=1
USER_C_FLAGS=/QI0f /TP
MSC_OPTIMIZATION=/O2 /Og
TARGETLIBS=$(DDK_LIB_DEST)\i386\ndis.lib
SOURCES=<list of my files>
Can I consider my build environment "supported" at this point, or do I need
to get rid of more flags?
Also, I am looking at some flags passed to the linker, and I am wondering if
these can cause problems to me?
-debug
-debugtype:cv
/functionpadmin:5
I want my build as optimized as possible, so seeing -debug in there worries
me a little. The documentation is not clear on whether this will generate a
less optimized driver?
And - what is /functionpadmin:5? "Minimum Function Padding" ? It seems
related to incremental linking, but the DDK also sends "INCREMENTAL:NO" to
the linker, so this seems contradictory.
Finally, I see
/pdbcompress
being passed to the linker - I assume this is not an optional flag? (yes,
the .pdb file indeed gets compressed on my file system).
Again, any input appreciated.
Thanks,
/ Hannes.
PS. The output spm.sys file is still 500kB, twice the size of the VS build
result of 250kB...
- Next message: Pavel A.: "Re: SDK String API use at Kernel level"
- Previous message: Pavel A.: "Re: WPA2 Support???"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|