delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/2000/05/23/06:05:51

Date: Tue, 23 May 2000 13:04:05 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: djgpp AT delorie DOT com
Subject: Re: windows version of Crafty
In-Reply-To: <qotjisob4rbol7aue9hb79m7qo266unv7u@4ax.com>
Message-ID: <Pine.SUN.3.91.1000523130325.4858C-100000@is>
MIME-Version: 1.0
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com

On Tue, 23 May 2000, Damian Yerrick wrote:

> >It should be possible
> >to compile crafty with mingw32. It would need some Makefile hacking.
> 
> But not very much if you already have a working DJGPP makefile;
> DJGPP and mingw32 are both GNU make + GCC + GNU binutils.

I'm guessing that you never had to tinker with Makefiles too much ;-)

The real problems are not the names of the development tools--this is
easily parameterized with variables like CC, LD, and CFLAGS--the real
problems are dependencies on shell features and built-in commands, and
the subtle aspects of special characters such as ' and ".  It is very
hard to get these right so that it will work with more than a single
port of Make.  And if one of the Make's is MSVC's nmake with its
totally alien syntax, you are toast.

> From what I've read, unoptimized GCC output is total cr4p.

That's because the ``unoptimized'' output of other compilers is not
really unoptimized.  They do some optimizations by default.

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019