X-Spam-Check-By:	sourceware.org
Date:	Wed, 16 Aug 2006 20:19:06 -0400 (EDT)
From:	Igor Peshansky <pechtcha AT cs DOT nyu DOT edu>
Reply-To:	cygwin AT cygwin DOT com
To:	mwoehlke <mwoehlke AT tibco DOT com>
cc:	cygwin AT cygwin DOT com
Subject:	Re: change in behavior of make from 3.80 to 3.81
In-Reply-To:	<ebvvri$mqd$2@sea.gmane.org>
Message-ID:	<Pine.GSO.4.63.0608162016310.14156@access1.cims.nyu.edu>
References:	<6 DOT 2 DOT 3 DOT 4 DOT 2 DOT 20060815151104 DOT 0b40e260 AT pop DOT nycap DOT rr DOT com> <01b901c6c116$21259430$a501a8c0 AT CAM DOT ARTIMI DOT COM> <6 DOT 2 DOT 3 DOT 4 DOT 2 DOT 20060816091525 DOT 0ab90af0 AT pop DOT nycap DOT rr DOT com> <20060816144110 DOT GX20467 AT calimero DOT vinschen DOT de> <6 DOT 2 DOT 3 DOT 4 DOT 2 DOT 20060816111421 DOT 0b446b60 AT pop DOT nycap DOT rr DOT com> <20060816155054 DOT GY20467 AT calimero DOT vinschen DOT de> <Pine DOT GSO DOT 4 DOT 63 DOT 0608161418370 DOT 9095 AT access1 DOT cims DOT nyu DOT edu> <6 DOT 2 DOT 3 DOT 4 DOT 2 DOT 20060816144036 DOT 09695af0 AT pop DOT nycap DOT rr DOT com> <Pine DOT GSO DOT 4 DOT 63 DOT 0608161543520 DOT 14156 AT access1 DOT cims DOT nyu DOT edu> <ebvvri$mqd$2 AT sea DOT gmane DOT org>
MIME-Version:	1.0
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

On Wed, 16 Aug 2006, mwoehlke wrote:

> Igor Peshansky wrote:
> > Alternatively, you can try to implement a $(cygpath ...) function in make
> > and submit *that* to the upstream maintainers.  That way, the Cygwin make
> > will not have to invoke a separate process to convert the paths that it
> > (as a program linked to cygwin1.dll) already knows how to do.
>
> I'd like to point out that such a patch would be all of about five lines
> of "code"... (And for the record, I've written both new make functions
> AND my own version of cygpath, so I know what I'm talking about.)

Properly written, perhaps about 10.  But what's a constant factor between
friends? ;-)

> Except note you would almost certainly want $(cygpathu) and $(cygpathw).

Umm, actually I was thinking of $(cygpath) with 2 parameters -- the type
of conversion, and the list of paths.

> Because no one seems to have gotten the point yet,
> http://cygwin.com/acronyms/#SHTDI ...and that somebody is not likely to
> be one of the people not having problems, so if all these other posters
> would kindly put their patches where their mouths are, then maybe
> something would be accomplished.

And those patches should certainly go to the GNU make mailing list for
the upstream maintainers to review.
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_	    pechtcha AT cs DOT nyu DOT edu | igor AT watson DOT ibm DOT com
ZZZzz /,`.-'`'    -.  ;-;;,_		Igor Peshansky, Ph.D. (name changed!)
     |,4-  ) )-,_. ,\ (  `'-'		old name: Igor Pechtchanski
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"Las! je suis sot... -Mais non, tu ne l'es pas, puisque tu t'en rends compte."
"But no -- you are no fool; you call yourself a fool, there's proof enough in
that!" -- Rostand, "Cyrano de Bergerac"

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -