RE: make --win32 incorrectly handles PATH

[Scott Carter <scarter at emware dot com>]

Thanks for the replies.

You're right of course. FREE software is offered on a take-it-or-leave-it
basis. 

You've given me some ammo that I can now take to my "management" and make an
argument for either a) investing a little more time to try to get this
version of make working like we want, or b) using something else. We already
looked at the most obvious "something else" options and eliminated them --
we can't freely distribute nmake, and trying to support a dozen different
IDE's is a nightmare. We chose gnu make because it's freely distributable
and widely used/understood (as much a defacto standard as anything I'm aware
of). And we moved to the cygwin port because the development platforms we
support are WinNT/98, our users aren't necessarily computer sophisticated,
and we don't want to push any more unix-style notation on them than we have
to (yeah, I know -- I prefer unix too).

I'll try to persuade my boss for permission to delve "under the hood" of
make. If I'm successful, and I come up with some fixes or suggestions, I'll
certainly share them.


Regards,
Scott Carter
Software Engineer

> ----- Forwarded message from Chris Faylor <cgf@cygnus.com> -----
> 
> From: Chris Faylor <cgf@cygnus.com>
> To: cygwin@sourceware.cygnus.com
> Subject: Re: make --win32 incorrectly handles PATH
> Date: Thu, 20 Jul 2000 16:44:03 -0400
> Reply-To: cygwin@sources.redhat.com
> Mail-Followup-To: cygwin@sourceware.cygnus.com
> In-Reply-To: <200007202038.QAA32487@envy.delorie.com>; 
>   from dj@delorie.com on Thu, Jul 20, 2000 at 04:38:06PM -0400
> 
> On Thu, Jul 20, 2000 at 04:38:06PM -0400, DJ Delorie wrote:
> >
> >> d) With my apologies to "FREE" software proponents everywhere, my
> >> company exists to profit from non-free software.
> >
> >No need to apologize.  You are free to make whichever choices you
> >wish, just as we are free to choose otherwise.
> 
> Right.
> 
> I was offering you an option for solving your problem, i.e., jumping
> in and debugging the problem yourself.
> 
> You've offered several reasons why that is not possible, which is fine.
> 
> I'm sure that you understand that your inability to debug this does
> not mean that someone else will step in to solve the problem that you
> have uncovered.
> 
> Maybe someone will be motivated to look into this.  Unfortunately,
> I really can't do it right now or for the foreseeable future.
> 
> cgf
> 
> ----- End forwarded message -----

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com