Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
X-Apparently-From: <earnie?boyd AT yahoo DOT com>
Message-ID: <3A648477.CDA965A6@yahoo.com>
Date: Tue, 16 Jan 2001 12:27:19 -0500
From: Earnie Boyd <earnie_boyd AT yahoo DOT com>
Reply-To: Earnie Boyd <cygwin AT cygwin DOT com>
X-Mailer: Mozilla 4.76 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Robert Collins <robert DOT collins AT itdomain DOT com DOT au>
CC: cygwin AT cygwin DOT com
Subject: Re: two differents version of unctrl.h, one in cygwin-1.1.7 and one in   
 ncurses-5.2
References: <kvk87wx4h4 DOT fsf_-_ AT vzell DOT de DOT oracle DOT com> <3A63CEBA DOT 6509B31 AT ece DOT gatech DOT edu> <3A643D02 DOT BCA1CC9C AT yahoo DOT com> <3A643F10 DOT 480F6601 AT ece DOT gatech DOT edu> <040201c07fb9$f6449160$0200a8c0 AT lifelesswks> <3A644D95 DOT FB8E7B46 AT yahoo DOT com> <044a01c07fc5$0449e390$0200a8c0 AT lifelesswks>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Robert Collins wrote:
> 
> GCC, the most common compiler in use under cygwin (I feel pretty safe with this assumption) is the tool that will be faced with two
> include files of the same name, and the issue of getting the right one *has* been solved by *distributors* on platforms where the
> cygwin differences shouldn't affect the solution for this issue.
> 

As I've said in response to Chuck, GCC has a solution, it's the -I
switch.  If you want to use the ncurses headers that are stored in
/usr/include/ncurses you just add `-I/usr/include/ncurses' and viola it
uses those headers instead of the /usr/include/unctrl.h header.  To
configure a program you would
  CC='gcc -I/usr/include/ncurses' ../configure ...
and the configure script would find the available headers.

The rule of thumb to use is, if a package footprint steps on the
OS/runtime footprint the package footprint needs to be segregated in a
recognizable manner.  My suggestion to use /usr/include/ncurses fits
that rule.

Cheers,
Earnie.

_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com


--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple