This is the mail archive of the
mailing list for the Cygwin project.
Re: include and library paths
- To: Mumit Khan <email@example.com.EDU>
- Subject: Re: include and library paths
- From: Ian T Zimmerman <firstname.lastname@example.org>
- Date: 01 Jul 1999 21:34:56 +0000
- Cc: email@example.com
- References: <199907012115.QAA21177@mercury.xraylith.wisc.edu>
>>>>> "Mumit" == Mumit Khan <firstname.lastname@example.org.EDU> writes:
Mumit> How about trying the "GCC" way -- use
Mumit> -I/usr/X11R6.4/include -I...?
Mumit> My personal opinion -- C_INCLUDE_PATH etc should never be
Mumit> used. You should see the number of bug reports from people
Mumit> who "forget" that they have these variables set in the
Mumit> environment and of course gets the wrong include file and
Mumit> all hell breaks loose. I like -I, -L, etc options that are
Mumit> visible when compiling/linking a file.
Except that my original situation involved a configure failure. I
know that I can pass extra options like this
but that only works for GNU autoconf style scripts, and only the clean
ones among these. (Ie. the ones that use CPPFLAGS and not some other
home cooked name, and that initialize it from the environment.)
2325 3rd Street #324, San Francisco, California 94107
Want to unsubscribe from this list?
Send a message to email@example.com