On Mon, Sep 17, 2001 at 08:18:27AM -0400, [EMAIL PROTECTED] wrote:
>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.
There is nothing intrinsically wrong with nmake. It makes no sense
to me that someone would use what is apparently an nmake file with
cygwin's make. If something is working why not use it.
>Anyway, the makefile can also be changed to use cp, that's what
>I'd do, for portability.
And then the next question is "I'm getting an error about DEL."
And after that it will be "I'm getting an error about DIR."
If you want to take the time to meticulously go through the makefile and
change every single MS-DOSism, then sure, go ahead. I just don't see
the benefit.
cgf
>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.
--
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/
