X-Spam-Check-By: sourceware.org
To: cygwin AT cygwin DOT com
From: mwoehlke <mwoehlke AT tibco DOT com>
Subject:  Re: 3.81 and windows paths
Date:  Fri, 28 Jul 2006 12:50:15 -0500
Lines: 32
Message-ID: <eadion$sei$1@sea.gmane.org>
References:  <20060727195042 DOT GC27890 AT brasko DOT net> <44C92033 DOT A2978A8E AT dessent DOT net> <17609 DOT 11132 DOT 462789 DOT 443104 AT lemming DOT engeast DOT baynetworks DOT com> <20060727221136 DOT GD6653 AT trixie DOT casa DOT cgf DOT cx> <44C95766 DOT 3040904 AT eagercon DOT com>
Mime-Version:  1.0
Content-Type:  text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding:  7bit
User-Agent: Thunderbird 1.5.0.5 (X11/20060719)
In-Reply-To: <44C95766.3040904@eagercon.com>
Cc: bug-make AT gnu DOT org
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
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

Michael Eager wrote:
> Christopher Faylor wrote:
>> On Thu, Jul 27, 2006 at 05:09:16PM -0400, Paul D. Smith wrote:
>>> In fact, I'm wondering if there is an advantage to building GNU make
>>> using the Cygwin environment, vs. using a native MingW (for example)
>>> build of GNU make?  I'm afraid I'm woefully ignorant about the details.
>>
>> There is no advantage using cygwin if you want to use a Makefile which
>> contains MS-DOS paths.  Using MinGW makes perfect sense in that case.
>> Despite having suggested this repeatedly, it seems some users are still
>> not clear on this concept.
> 
> When I ran into this problem, it was because there was a
> WINDOWS environment symbol referenced in a dependency.
> It's not practical to change the environment symbol -- it is
> used by both makefiles and native windows programs.  Nor is it
> practical to re-write the paths in the makefile -- because the
> makefile needs to reference this (and other) shared environment symbols,
> which are not fixed in the makefile.
> 
> There are two equally unpleasant resolutions recommended:
> either install two products (Cygwin and MinGW) or retain
> a back-level version of make, forgoing all future bug fixes.
> Neither are very good, but I've opted for the second choice.

You're forgetting the third, correct choice: use cygpath to translate 
the offending environment variable (if you like, store a copy of the 
translated variable in make's environment).

-- 
Matthew
Warning: prolonged exposure to Cygwin may cause addiction.


--
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/