Hmm, for application development, especially in cases where existing
makefilery, autowhatever etc strongly is geared towards gcc and the
rest of a GNU toolchain, sure.
But for driver development? Windows drivers are by definition platform
specific, you aren't going to be using cross-platform so
> It is nice to be able to use the same open toolchain for both
> application and driver development...
Hmm, for application development, especially in cases where existing
makefilery, autowhatever etc strongly is geared towards gcc and the
rest of a GNU toolchain, sure.
But for driver developmen
Okay I finally figured it out.
The problem with the DDK headers in the MinGW-w64 SVN is that there are
still headers missing (like ntdef.h among others).
After messing around for a good while with trying to combine the MinGW and
MinGW-w64 headers together to complete the puzzle, I finally g
On Mon, May 3, 2010 at 12:11 PM, Kyle Stewart wrote:
> I would like to use MinGW-w64 as my one stop shopping toolchain for
> targeting the Windows platform including driver development, but I have run
> into a snag. I have downloaded the latest personal builds for both x86 and
> x64 targets. I am
I would like to use MinGW-w64 as my one stop shopping toolchain for
targeting the Windows platform including driver development, but I have run
into a snag. I have downloaded the latest personal builds for both x86 and
x64 targets. I am running a x64 Windows 7 host and I have successfully used
the
