Hello bill
This might not help but once a long time ago I had built a driver using the
ddk and a user stack using the SDK. Both of these were free.
Later when I tried to integrate it with a larger component built using a
devstudio app the app failed to use the use mode stack DLLs I had built
with the SDK. Despite fiddling with compiler settings I could never get
this to work.
Once I switched my user stack to being built with the same version of
devstuidio it all magically worked.
I guess I'm thinking that edk2 wants to avoid a similar problem.
On Feb 7, 2014 3:50 PM, "Bill Paul" <[email protected]> wrote:
> The other day I decided fix my code so that it could build with the EDKII
> on
> Windows without a GNU toolchain (which meant re-writing some assembly from
> GNU
> AT&T syntax to Intel syntax -- don't ask), so I looked through the
> "supported
> toolchains" list in tools_def.txt to see what that would entail.
>
> I noticed there's a DDK3790 option which allows you to build just with the
> WinDDK compilers directly (e.g. no Visual Studio needed).
>
> It happens I have an actual CD copy of this kit -- I ordered it from
> Microsoft
> (for free!) some years ago when it was still a current product and held
> onto
> it, so I installed it on my Win7 machine in my office and lo and behold
> everything worked as expected (including the Microsoft C compiler being
> exceptionally fascist).
>
> But I noticed that the descriptions for the VS2003, VS2005, VS2008, VS2010
> and
> VS2012 toolchain tags all say they require the WinDDK as well, e.g.:
>
> # VS2012 -win32- Requires:
> # Microsoft Visual Studio 2012 Professional
> Edition
> # Microsoft Windows Server 2003 Driver
> Development
> Kit (Microsoft WINDDK) version 3790.1830
>
> My question is: what's the dependency that forces this requirement? It
> doesn't
> look as if the definitions in tools_def.txt cause the DDK tools to be used
> when one of the Visual Studio toolchain tags is selected, but I could be
> wrong.
>
> The reason I ask is that the WinDDK is obsolete and while you can still
> download it for free from Microsoft if you hunt for it, it seems the
> Windows
> Driver Kit 7.1 has taken its place. I think it includes the same basic
> tools,
> but they're installed in a different path.
>
> -Bill
>
> --
>
> =============================================================================
> -Bill Paul (510) 749-2329 | Senior Member of Technical Staff,
> [email protected] | Master of Unix-Fu - Wind River
> Systems
>
> =============================================================================
> "I put a dollar in a change machine. Nothing changed." - George Carlin
>
> =============================================================================
>
>
> ------------------------------------------------------------------------------
> Managing the Performance of Cloud-Based Applications
> Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
> Read the Whitepaper.
>
> http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk
> _______________________________________________
> edk2-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/edk2-devel
>
------------------------------------------------------------------------------
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk
_______________________________________________
edk2-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/edk2-devel
