MainComputersProgrammingLanguages › Compilercache

Compilercache

Edit Page
Report
Scan day: 16 February 2014 UTC
-92
Virus safety - good
Description: Caches compiled object files to dramaticly speed up compiles. More convenient than make, and speeds up builds (like RPM builds) that make doesn't. Obsoleted by ccache.
compilercache now also has a sourceforge entry: here is the README file included in the distribution: compilercache Version 1.0.10 ---------------------------- Table of Contents ----------------- 1 .... What is compilercache and Why do I want it ? 2 .... Is it dangerous to use compilercache ? 3 .... How do I install compilercache ? 4 .... How do I configure compilercache ? 5 .... Show me an example of compilercache usage ! 6 .... How do I clean all those Megabytes of Cache files ? 7 .... Technical insights and problems 8 .... Some performance statistics ! 1. What is compilercache and Why do I want it ? ------------------------------------------------ Compilercache is under the GNU General Public License (GPL). Compilercache is a wrapperscript around your C and C++ compilers. Each time you compile something, the wrapperscript puts the result of the compilation into a cache. And once you compile the same thing again, the result will be picked from the cache instead of being recompiled. You might wonder why you need this, since there seems to be another tool for this purpose, "make". But to get "make" working you need to create a Makefile. You need to take care of your dependencies manually. If you make a mistake, wrong code will be generated. Another drawback with "make" is that if you normally compile your project with -O2 (optimizations) and now want to debug it, you will have to recompile the whole stuff with -g (debugging). now with "make" you have to do a "make clean", then change the options, and then recompile everything. With compilercache you basically do the same, but if your project has already been compiled with -g in the past, and now currently you run it with -O2 and want to switch back to -g, the old compilation results will be picked from the cache. i.e. switching compiler options goes fast! not like "make" which forces you into a complete recompilation. Since compilercache is just a wrapper around your compiler, you can still use "mak
Size: 2048 chars

Contact Information

Email:
Phone&Fax:
Address:
Extended:

WEBSITE Info

Page title:Compilercache
Keywords:
Description:
IP-address:82.165.123.76

WHOIS Info

NS
WHOIS
Status: connect
Date
Changed: 2009-11-11T12:14:17+01:00
Changed: 2012-12-10T20:50:22+01:00
Changed: 2012-12-10T20:50:22+01:00