RE: Add search path to the cygwin.

[David Korn <dkorn at pixelpower dot com>]

>From: mike corbeil ordinary user account [mailto:mcorbeil@NetRevolution.com]
>Sent: 19 October 2000 21:49

>Well done and it's better that way.  If a person was new to Unix, or
>Linux, which ever was being used, and didn't have a decent book to refer
>to, then what I had written could certainly be a "byte" of a pain or
>nuissance.

 Even after several years of experience I still find myself struggling
to remember which shell is which, and whether subshells will inherit my
variables, and which syntax to use for loops, and... and ... and ...
 The power and variety of the Unix shells is a double-edged sword!

>Using PATH for this seemed strange and I've no idea if it'd even work
>(if it's stated in the book on make or the man page, then I don't
>remember this part). I've only used PATH for executables.
>
>Can PATH, or $PATH, actually be used to specify where include files are
>located?

  Not by default, at any rate as far as gcc is concerned. It's an
unlikely thing for any compiler to implement - since there is no
interchangeability between .h files and executables, there's no sense in
only using one environment variable to point to both. OTOH it *could*
be done - you could use a string substitution in the makefile to replace
all the colons between the $PATH components with space, -I, space, and
then prefix that with -I and add it to the compiler CFLAGS. But I've
never seen it done and I can't see any good reason to blur the meaning
of $PATH.

>>  "The secret of life is honesty and fair dealing. If you can fake that,
>> you've got it made." -Groucho Marx
>
>Business philosopher as well as good comedian, eh.  I haven't seen any
>of his material in years, but only remember a good comic.

 And a Discordian saint, too!

           DaveK
-- 
 "The secret of life is honesty and fair dealing. If you can fake that,
you've got it made." -Groucho Marx