Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-Id: <5.1.1.6.2.20030311131429.00a03aa0@mail.actron.com>
X-Sender: nsomos AT mail DOT actron DOT com
Date: Tue, 11 Mar 2003 13:29:20 -0500
To: cygwin AT cygwin DOT com
From: Neil Somos <nsomos AT actron DOT com>
Subject: compilercache may be helpful
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed

I stumbled across compilercache at http://www.erikyyy.de/compilercache/
and thought I would share it in the hope that some folk might find it useful.
I found no prior mention of it on this mailing list.

The description at sourceforge is as follows
--------------
Compilercache is a wrapperscript around your C and C++ compilers. Results 
from compilations are put into a cache. And once you compile the same thing 
again, the result will be picked from the cache instead of being recompiled
--------------

http://sourceforge.net/projects/compilercache/

Both flex and md5sum are needed for it to work/install.
It also depends on bash.

I tried it on cygwin and it seems to work.
(Although some of the instructions might need tweaking as
  the version number was upped but the instructions weren't)

Its usefulness would be in direct proportion to how large and
time-consuming your compiles may be.  If you are short on disk
space to begin with, you might want to skip it.

neal


--
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/