Re: Win DDK 3790 cannot compile with VS 6.0, but linking error with VS. NET
From: Linda Yang (hyang_at_signalogic.com)
Date: 02/06/04
- Next message: Bryan S. Burgin [MSFT]: "RE: USB networking driver for Media ATM"
- Previous message: Rohit Raina [MS]: "Re: Would an IM filter driver bind to a PPPoE running over USB"
- In reply to: Mark Roddy: "Re: Win DDK 3790 cannot compile with VS 6.0, but linking error with VS. NET"
- Next in thread: Phil Barila: "Re: Win DDK 3790 cannot compile with VS 6.0, but linking error with VS. NET"
- Reply: Phil Barila: "Re: Win DDK 3790 cannot compile with VS 6.0, but linking error with VS. NET"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 06 Feb 2004 02:20:02 GMT
Mark,
Thanks for the DDKBuild utility. I am trying out your DDKbuild utility.
I guess I was spoiled by visual studio where I can put Preprocessor
Definition in the project properties. I have a few defines in there
that I need for compilation because this cold runs on several platforms.
How do I do create these defines?
Same question also applies even with DDK build.exe utility, how do I do
preprocessor defines.
Linda
Mark Roddy wrote:
> On Wed, 04 Feb 2004 00:52:07 GMT, Linda Yang <hyang@signalogic.com>
> wrote:
>
>
>>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
>>
>
> Microsoft did not intentionally set out to make it impossible to use
> Visual Studio, why would they do that? VS is a huge revenue stream for
> them. What they set out to do was to distribute, with each release of
> the ddk, the complete (well almost complete) set of compilation tools
> qualified to correctly build drivers. This is a huge improvement over
> the previous situation, which had developers world-wide using 'some
> version or other' of 'some compiler or other' to generate something
> that might be more or less binary compatible with the target OS
> execution environment.
>
> You can still use the VS6 or VS7 IDE. You can fix up your current
> projects, which it seems directly invoke the compilation tools, or you
> can use the method that I (and probably others as well) developed
> years ago to address the no IDE support issue, referred to by Mr.
> Little as the DDKBUILD method. See my website for detailed
> instructions www.hollistech.com and free download of the shell script.
>
>
>
>
>
> =====================
> Mark Roddy
> Windows .NET/XP/2000 Consulting
> Hollis Technology Solutions 603-321-1032
> www.hollistech.com
- Next message: Bryan S. Burgin [MSFT]: "RE: USB networking driver for Media ATM"
- Previous message: Rohit Raina [MS]: "Re: Would an IM filter driver bind to a PPPoE running over USB"
- In reply to: Mark Roddy: "Re: Win DDK 3790 cannot compile with VS 6.0, but linking error with VS. NET"
- Next in thread: Phil Barila: "Re: Win DDK 3790 cannot compile with VS 6.0, but linking error with VS. NET"
- Reply: Phil Barila: "Re: Win DDK 3790 cannot compile with VS 6.0, but linking error with VS. NET"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
