Re: Win DDK 3790 cannot compile with VS 6.0, but linking error with VS. NET
From: David J. Craig (SeniorDriversWriter_at_shogunyoshimuni.com.net)
Date: 02/04/04
- Next message: Bogdan Bejan: "Kernel malloc/realloc?"
- Previous message: Maxim S. Shatskih: "Re: WaitCommEvent"
- In reply to: Linda Yang: "Re: Win DDK 3790 cannot compile with VS 6.0, but linking error with VS. NET"
- Next in thread: Maxim S. Shatskih: "Re: Win DDK 3790 cannot compile with VS 6.0, but linking error with VS. NET"
- Reply: Maxim S. Shatskih: "Re: Win DDK 3790 cannot compile with VS 6.0, but linking error with VS. NET"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 3 Feb 2004 20:35:02 -0500
Did you try a Google search on 'DDKBUILD'? If so, why the questions
below. If not, try it. I don't use it because I detest using Visual
Studio for drivers. I use CodeWright and even use it with applications
that I build using Visual Studio. When Microsoft eliminated Brief
emulation for Visual Studio, my decision became real obvious and simple.
"Linda Yang" <hyang@signalogic.com> wrote in message
news:XmXTb.614$y55.225118420@newssvr11.news.prodigy.com...
> Gary G. Little wrote:
>
> > You should have the latest DDK installed. That includes the
"blessed"
> > compiler and tools for driver development. You will have wither
manually set
> > your executable paths in Visual Studio to the path of the WinDDK
3790
> > compiler, or download DDKBUILD and change your VS build lines to use
> > DDKBUILD. The latter is by far the least painful and the recommended
route.
> >
>
> Thanks for replying. I did some more research. I found this
paragraph
> in MSDN with an article titled New in the DDK for Windows XP:
>
> "A number of important changes have been made to the Windows DDK build
> environment. For one, the Windows DDK now includes a complete set of
> tools for building drivers. Microsoft® Visual C++® is no longer
required
> to be installed to use the DDK. Use of the included tools for all
> Windows 2000 and Windows XP drivers is expected within the shipping
> build environment. This version of the Windows DDK does not support
> building Windows XP or Windows 2000 drivers using a version of
Microsoft
> Visual C++ earlier than the one supplied with the DDK. Attempts to use
> an incorrect version of Visual C++ will result in the following error
> message from the compiler:
>
> error C1189: #error : Compiler version not supported by Windows DDK
> This requirement is due to the reliance on many new features within
this
> tool set for proper functioning of the include build environment. The
> compiler, linker, and supporting files, such as C Run-Times (CRTs),
> should be considered an atomic unit within the build environment. It
is
> likely that mixing the supporting tool files of Visual C++ versions 5
or
> 6 with those in this DDK release, which are based on the new Visual
C++
> version 7 code base, will result in errors in the binaries. Using the
> provided build environment and build tools is thus strongly
recommended
> to ensure generation of valid binaries."
>
> It's unfortunate that Microsoft no longer allow you to use Visual
Studio
> to build the device drivers, at least they try to make it difficult.
I
> had all my projects set up to compile under Visual Studio, I will make
> an attempt to change my VS build lines. Since I have never done this
> before, should I change it in the project file where: CPP=cl.exe to
> build.exe or do it in the custom build. What about the linker?
>
> Thanks again for the pointers.
>
> Linda
>
>
>
>
- Next message: Bogdan Bejan: "Kernel malloc/realloc?"
- Previous message: Maxim S. Shatskih: "Re: WaitCommEvent"
- In reply to: Linda Yang: "Re: Win DDK 3790 cannot compile with VS 6.0, but linking error with VS. NET"
- Next in thread: Maxim S. Shatskih: "Re: Win DDK 3790 cannot compile with VS 6.0, but linking error with VS. NET"
- Reply: Maxim S. Shatskih: "Re: Win DDK 3790 cannot compile with VS 6.0, but linking error with VS. NET"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
