Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Message-ID: <014101c2c0c4$9264d580$78d96f83@pomello> From: "Max Bowsher" To: "Marcel Telka" Cc: References: <20030120145735.GC28535@tortuga.etc.sk> <20030120150543.GC27717@redhat.com> <20030120175247.GD28535@tortuga.etc.sk> <004b01c2c0ad$6dea9300$78d96f83@pomello> <20030120180623.GE28535@tortuga.etc.sk> Subject: Re: Announce: ioperm-0.2.1 for cygwin released Date: Mon, 20 Jan 2003 20:43:21 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Marcel Telka wrote: > On Mon, Jan 20, 2003 at 05:57:42PM -0000, Max Bowsher wrote: >> Marcel Telka wrote: >>> On Mon, Jan 20, 2003 at 10:05:43AM -0500, Christopher Faylor wrote: >>>> On Mon, Jan 20, 2003 at 03:57:35PM +0100, Marcel Telka wrote: >>>>> This software adds support for ioperm() function to Cygwin. >>> 2. Windows DDK is required for the driver compilation. >> 2. is likely a problem. Are you aware that w32api has some ddk >> support now? > Yes. But this is only at .h level. I need a linker (binutils)... > I'm unaware about any way to compile & link a device driver using > cygwin-only tools :-( It is at very least possible to create a null.sys device driver that implements a /dev/null-style bitbucket device, entirely with cygwin-only tools. There is sample code at: http://reactos.wox.org/download/ddk-sample.tar.gz I found that the current libntoskrnl.a in w32api-2.1 was too undeveloped to support compilation of this sample. However, installing w32api-cvs solved that problem. Food for thought, anyway. I don't know how mature the mingw ddk is, but its probably worth a try. Max. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/