Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender: cygwin-owner AT sources DOT redhat DOT com
Date: Mon, 17 Sep 2001 08:18:27 -0400
From: rich-paul AT rich-paul DOT net
To: cygwin AT cygwin DOT com
Subject: Re: Make and VC++ compiler problems
Message-ID: <20010917081827.E28104@monster.rich-paul.net>
References: <3B8AE3790002CAB1 AT cpmail DOT asap DOT asp DOT net> <NFBBLOMHALONCDMPGBLFIEFHCBAA DOT info AT rlsystems DOT net> <20010915130349 DOT F28425 AT redhat DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.16i
In-Reply-To: <20010915130349.F28425@redhat.com>; from cgf@redhat.com on Sat, Sep 15, 2001 at 01:03:49PM -0400

I disagree with the statement that if you're using VC++, you
should use nmake.  There is no reason that a garbage compiler
should imply a garbage make environment.  Perhaps a better way to
phrase it is "Know the tools you're using".  My project uses VC++
in a cygwin environment quite nicely, although we're working
toward porting to mingw.

Anyway, the makefile can also be changed to use cp, that's what
I'd do, for portability.

On Sat, Sep 15, 2001 at 01:03:49PM -0400, Christopher Faylor wrote:
> On Sat, Sep 15, 2001 at 01:35:08PM +0200, Ronald Landheer wrote:
> >Hello Camilla,
> >
> >If you're running under Bash, you might want to try the following:
> >$ alias copy=cp
> 
> Somehow, I think that this problem is just indicative of the "tip
> of the iceberg".
> 
> If you're using VC++, then use nmake.  If you don't understand what
> cygwin is or how make works then just stick with the tools that are
> designed to work with what you're using.
> 
> cgf
> 
> --
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> Bug reporting:         http://cygwin.com/bugs.html
> Documentation:         http://cygwin.com/docs.html
> FAQ:                   http://cygwin.com/faq/
> 

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/