X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	q=dns; s=default; b=VCbQV9g765mT1yVuu+LKH4PKW700+7vhDmMclWDT0BC
	J2mt9dfnJXH7F2GHDHkF6AGV8d4HTGKCfyYkBwDeQoJqHgr8QqPExUTjVleISCvC
	+C80EIi9v13ahAO1o9rrLDY/v6mEVAqfSFXnZoN/Fh1VqC0W7hAj8byflDKKzYvg
	=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	s=default; bh=sizkxN0Pf+AmNrn62QaWrBeQ6po=; b=snwyF/COH2UY0cQT0
	roQR/WVhXX2ZIQd05gurmIelGlhqz0wl7+v924BCEsv/VeX6DHfTLWMjaRJn10Bw
	y6y/QbKZfYscAb3NIyXDxYey4UHOypV8VUIMay+Wrk4p8nIW9D3+GzTQHSKUnPuI
	K7Rcjuv1ZzRFxI49bjcKXlCL7g=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
X-Spam-SWARE-Status:	No, score=-5.7 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_TRUST,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_NO,RCVD_IN_HOSTKARMA_YE autolearn=ham version=3.3.1
Message-ID:	<51641548.2060700@cwilson.fastmail.fm>
Date:	Tue, 09 Apr 2013 09:19:04 -0400
From:	Charles Wilson <cygwin AT cwilson DOT fastmail DOT fm>
User-Agent:	Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: Bug in ddk headers when used from cygwin
References:	<51625CAE DOT 2030703 AT cwilson DOT fastmail DOT fm> <20130408074801 DOT GA10199 AT calimero DOT vinschen DOT de> <51630442 DOT 4080805 AT cwilson DOT fastmail DOT fm> <20130409091609 DOT GI10126 AT calimero DOT vinschen DOT de>
In-Reply-To:	<20130409091609.GI10126@calimero.vinschen.de>

On 4/9/2013 5:16 AM, Corinna Vinschen wrote:
> On Apr  8 13:54, Charles Wilson wrote:
>> But doesn't this mean that the cygwin's w32api package should
>> exclude all of the ddk headers; it's not simply a case that you
>> "shouldn't" use ddk/*.h, but that you actually cannot, because
>> compilation will fail.
>
> The absence of intrin.h was a bug, but otherwise you could still use
> the ddk headers for what they are supposed to be:  Writing device
> drives and other kernel stuff.  The difference is just that the ddk
> headers from mingw-w64 cannot be used together with the user space
> headers like windows.h, but that's not different from "upstream".

...but is it reasonable to create a *cygwin* device driver or kernel 
mode item?  If you're using the cygwin compiler, then you're linking 
against the cygwin dll -- which makes a bunch of usermode w32 calls 
under the hood.  If it's bad juju to mix ddk/ kernel mode stuff with 
w32api/ user mode stuff, then any "cygwin" device driver is, by 
definition, bad juju.

If I'm correct, then the *cygwin* w32api-headers package (and 
cygwin64-w32api-headers) should exclude ddk/ from their deliverable 
footprint, even if intrin.h is added back to the toplevel w32api/ 
include directory for other reasons. Of course mingw64-x86_64-headers 
and mingw64-i686-headers need to retain the ddk/ headers, for precisely 
the reason you indicate, and those two already provide the toplevel 
intrin.h file.

--
Chuck



--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

- Raw text -