Yup, that would really be fantastic. And it is obvious to guess the
direction. Couple months ago, I tried to see what is the cost of
Codewarrior for symbian, an hefty (5K usd). I use the other version(s),so
I thought it would be nice to have a fairly same UI, so less hastle…
Also it would be nice to have both the krnl and usrmode. But then there is
the
marketing ( how many ways you can slice a pie …)
thanks for the news !
-prokash
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Paul Benware
Sent: Thursday, April 01, 2004 4:26 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Editor for device driver work
I just came back from a Microsoft conference (Mobile DevCon) where it was
announced during some of the sessions and one of the keynotes that Visual
Studio 2005 (aka Whistler, I think) was going to incorporate stuff from
eVC++ at least for the mobile platform development. MS wants developers to
be able to target all their platforms from one tool. I guess we shall see
how good of a job they do with this… They were showing demos of this
where the presenters were using VC 2005 and deploying applications to
Smartphones and PDAs…
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Prokash Sinha
Sent: Wednesday, March 31, 2004 11:19 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Editor for device driver work
Maybe it’s time to get the technology from eVC++ studio or Platform Builder
to VisualStudio. Recently there was feedback from given to most of us, if
not
all of us. I did mention that it would be a great step forward to this,
starting
with punch card (JCL, PROC) then makefile, then wizard, it’s getting better
everyday
so whynot VStudio handles it transperantly. I carry template project file to
have
mix-language compilation, MASM pwb is bit old fashioned. And on my way I
found that
the ml comes for kernl module target is different from ml that comes with
apps dev., if
my memory servers now !!! or at least somewhere 386(p) gets shovled in or
something.
-Different translator(s), different target(s) would be nice to have.
I’M NOT COMPLAINING THOUGH, AS OFTEN IT SOUNDS THAT WAY 
-prokash
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Vladimir
Chtchetkine
Sent: Wednesday, March 31, 2004 12:54 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Editor for device driver work
With VC7 it’s very easy to set up a build environment where you can use
VS as editor (with all its reach functionality) available to you and
still be able to do builds using “build” utility from the DDK. Here is
how I do it for myself. I have installed all 3 DDKs (W2K, XP, NET) under
one root and set global env. variable DDKROOT to C:\DDK. Then I create
an empty “makefile” project in VC7, added “source” and “makefile” files
to it and other files that compose my driver project. Then I’ve created
W2K, XP and NET configurations each with both, free and checked
versions. Then, in Project->Properties->Configuration Properties->NMake
I created following settings (example is given for “XP checked” config):
- For “Build Command Line”
call $(DDKROOT)\BIN\setenv.bat $(DDKROOT) WXP checked
cd $(ProjectDir)
build -beEIFZ
copy “$(ProjectDir)\bin\XP\checked\i386*.pdb” “$(XPSYM)\sys*.pdb”
- For “Rebuild All Command Line”
call $(DDKROOT)\BIN\setenv.bat $(DDKROOT) WXP checked
cd $(ProjectDir)
build -cbeZEIF
copy “$(ProjectDir)\bin\XP\checked\i386*.pdb” “$(XPSYM)\sys*.pdb”
… and everything started to fly
Here is a sample of my “sources” file
TARGETNAME = SdFMon
TARGETTYPE = DRIVER
DRIVERTYPE = FS
386_WARNING_LEVEL = /W4 /WX
MSC_OPTIMIZATION = $(MSC_OPTIMIZATION) /Ob1
!IF “$(_NT_TARGET_VERSION)” == “0x500”
UMFSD_WINVERDEF= /DNTVERSION=500 /DWINVER=0x500 /D_WIN32_WINNT=0x0500
BASE_INC= “$(BASEDIR)\inc\ddk\w2k”; “$(BASEDIR)\inc\ifs\w2k”;
“$(BASEDIR)\inc\ddk\wdm\w2k”
!IF “$(DDKBUILDENV)” == “checked” | “$(DDKBUILDENV)” == “chk”
TARGETPATH = Bin\W2K\Checked
UMFSDLIBPATH = $(DRVSDK)\KM\Libs\W2K\Checked\i386
COMMONLIBPATH = …\Libs\W2K\Checked\i386
!ELSE
TARGETPATH = Bin\W2K\Free
UMFSDLIBPATH = $(DRVSDK)\KM\Libs\W2K\Free\i386
COMMONLIBPATH = …\Libs\W2K\Free\i386
!ENDIF
!ELSEIF “$(_NT_TARGET_VERSION)” == “0x501”
UMFSD_WINVERDEF= /DNTVERSION=501 /DWINVER=0x501 /D_WIN32_WINNT=0x0501
/DRTL_USE_AVL_TABLES=1
BASE_INC= “$(BASEDIR)\inc\ddk\wxp”; “$(BASEDIR)\inc\ifs\wxp”;
“$(BASEDIR)\inc\ifs\flt”; “$(BASEDIR)\inc\ddk\wdm\wxp”
!IF “$(DDKBUILDENV)” == “checked” | “$(DDKBUILDENV)” == “chk”
TARGETPATH = Bin\XP\Checked
UMFSDLIBPATH = $(DRVSDK)\KM\Libs\XP\Checked\i386
COMMONLIBPATH = …\Libs\XP\Checked\i386
!ELSE
TARGETPATH = Bin\XP\Free
UMFSDLIBPATH = $(DRVSDK)\KM\Libs\XP\Free\i386
COMMONLIBPATH = …\Libs\XP\Free\i386
!ENDIF
!ELSEIF “$(_NT_TARGET_VERSION)” == “0x502”
UMFSD_WINVERDEF= /DNTVERSION=502 /DWINVER=0x502 /D_WIN32_WINNT=0x0502
/DRTL_USE_AVL_TABLES=1
BASE_INC= “$(BASEDIR)\inc\ddk\wnet”; “$(BASEDIR)\inc\ifs\wnet”;
“$(BASEDIR)\inc\ifs\flt”; “$(BASEDIR)\inc\ddk\wdm\wnet”
!IF “$(DDKBUILDENV)” == “checked” | “$(DDKBUILDENV)” == “chk”
TARGETPATH = Bin\NET\Checked
UMFSDLIBPATH = $(DRVSDK)\KM\Libs\NET\Checked\i386
COMMONLIBPATH = …\Libs\NET\Checked\i386
!ELSE
TARGETPATH = Bin\NET\Free
UMFSDLIBPATH = $(DRVSDK)\KM\Libs\NET\Free\i386
COMMONLIBPATH = …\Libs\NET\Free\i386
!ENDIF
!ENDIF
TARGETLIBS = $(TARGETLIBS) $(UMFSDLIBPATH)\KmCpp.lib
$(UMFSDLIBPATH)\KmDrvBase.lib $(UMFSDLIBPATH)\KmWrap.lib
$(UMFSDLIBPATH)\KmRtl.lib $(COMMONLIBPATH)\SdFMonLib.lib
DRVBASE_INC = “…..\Inc”; “…\KM_Inc”; “$(DRVSDK)\Common”;
“$(DRVSDK)\KM\Inc\Common”; “$(DRVSDK)\KM\Inc\KmCpp”;
“$(DRVSDK)\KM\Inc\KmRtl”; “$(DRVSDK)\KM\Inc\KmWrap”;
“$(DRVSDK)\KM\Inc\KmDrvBase”
INCLUDES= $(BASE_INC); $(DRVBASE_INC)
UMFSD_BASEDEF= /DRING0 /DNT_UP=0
!IF “$(DDKBUILDENV)” == “checked” | “$(DDKBUILDENV)” == “chk”
UMFSD_BASEDEF = $(UMFSD_BASEDEF) /DDBG=1
!ENDIF
C_DEFINES=$(UMFSD_BASEDEF) $(UMFSD_WINVERDEF)
SOURCES= SdFMon.rc \
SdFMonRecognizerHookDeviceObject.cpp \
SdFMonFilterDeviceObject.cpp \
SdFMonClose.cpp \
SdFMonCreate.cpp \
SdFMonCleanup.cpp \
SdFMonSetInformation.cpp \
SdFMonWrite.cpp \
SdFMonEnumSupportImp.cpp \
SdFMonLegacyMonitorCallback.cpp \
SdFMonDriverObject.cpp
-----Original Message-----
From: Charles Lane [mailto:xxxxx@earthlink.net]
Sent: Wednesday, March 31, 2004 11:33 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] Editor for device driver work
I *really* hate to ask this question because I know what it can lead
to…
However.
I’ve always used Visual Studio as an editor for device driver files and
then
the
Build utility to actually create the executables. I like VS’s browse
stuff
and so on.
Besides, I’m used to it.
Now I’m knee-deep in multiple platform stuff (x86, amd64, ia64, server
2003,
XP, 2000
and whatever the current AMD beta O/S is supposed to be.) and I think
it’s
time to say
good bye to VS for this sort of thing.
(I’m aware that there is a BAT file for using VS with the proper
compilers
but I think
maybe using something closer to Microsoft’s internal process is better.)
So.
What editor do you find useful for dealing with driver code?
Mickey.
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as:
xxxxx@borland.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: xxxxx@garlic.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: xxxxx@koolspan.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: xxxxx@garlic.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
There are