Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive:	<http://sourceware.cygnus.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help:	<mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender:	cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To:	mailing list cygwin AT sourceware DOT cygnus DOT com
Date:	Thu, 30 Mar 2000 13:16:03 -0500
Message-Id:	<200003301816.NAA25667@envy.delorie.com>
From:	DJ Delorie <dj AT delorie DOT com>
To:	dikypkyl AT ptdprolog DOT net
CC:	cygwin AT sourceware DOT cygnus DOT com
In-reply-to:	<Pine.GSO.4.10.10003301312050.10979-100000@home1> (message from
	Marc Kurtz on Thu, 30 Mar 2000 13:12:46 -0500 (EST))
Subject:	Re: questions about kernel source headers
References:	<Pine DOT GSO DOT 4 DOT 10 DOT 10003301312050 DOT 10979-100000 AT home1>

> CIPE uses kernel headers (usr/src/linux/include) in its code. How do
> I integrate the cygwin headers with the kernel headers?

In general, you don't.  The parts of CIPE that use linux-specific
headers will need to be investigated to determine how to re-implement
those portions in a cygwin-specific way.  You usually can't just use
headers from other platforms and expect it to work.

Of course, it also depends on which headers its using, and why.

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -