delorie.com/archives/browse.cgi | search |
Newsgroups: | comp.os.msdos.djgpp |
From: | mhaley99 AT homemail DOT com (Matthew Haley) |
Subject: | Re: allegro compile time |
Message-ID: | <mhaley99.5.0003E9E9@homemail.com> |
Lines: | 24 |
References: | <e55o3.4067$xZ6 DOT 283996 AT harpo DOT ctel DOT net> <7nrjsm$iib$1 AT taliesin DOT netcom DOT net DOT uk> |
Organization: | Home |
X-Newsreader: | Trumpet for Windows [Version 1.0 Rev A] |
Date: | Fri, 30 Jul 1999 03:54:47 |
NNTP-Posting-Host: | 209.181.133.112 |
X-Trace: | news.uswest.net 933332291 209.181.133.112 (Fri, 30 Jul 1999 05:58:11 CDT) |
NNTP-Posting-Date: | Fri, 30 Jul 1999 05:58:11 CDT |
To: | djgpp AT delorie DOT com |
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
Reply-To: | djgpp AT delorie DOT com |
I have a 486DX 33. I always plan a nap if I am going to compile Allegro :) Disk caches /do/ help a lot though, really I think that the disk is the slowest part since there are so many small files to compile. In article <7nrjsm$iib$1 AT taliesin DOT netcom DOT net DOT uk> "Michael Stewart" <mike AT reggin DOT freeserve DOT co DOT uk> writes:>From: "Michael Stewart" <mike AT reggin DOT freeserve DOT co DOT uk>>Subject: Re: allegro compile time >Date: Fri, 30 Jul 1999 08:23:02 +0100 >Chewbaklava wrote in message ... >>just wondering, for those of you who use allegro, how long did it take to >>compile for you?? it almost took an hour (just over 50 minutes) for me on >>my 486DX 66. it said in the readme go do something else while it compiles >>but this seems WAY too long. >Allegro is a big project and it will take a few minutes, but it does sound >to me that 50 minutes is a little long. There are speed up hints in the FAQ >which may help.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |