curaga
Group: Members
Posts: 2163
Joined: Feb. 2007 |
 |
Posted: June 30 2008,15:45 |
 |
Whenever you do some more compiling, and most stuff has the autohell *cough* autotools *cough*, you will exactly know what I'm talking about - nothing has changed since the last package 1 minute ago, yet you have to wait for it to check everything. So annoying.
Checking you have gcc.. yes (oh really)
Checking your gcc works.. yes (ooooh)
and so on. Well folks, I have a solution 
I thought I should use the cache for my advantage. So I configured a simple package, removed anything I might possibly change from the config.cache (install prefix and optimization flags), and now I copy this file whenever I compile anything and have a huge speed boost in configuring.
| Quote | | Why a simple package? Wouldn't a complicated one give more speedup? |
Why yes, thanks me for asking. The thing is, only the simple parts are almost guaranteed not to change. So the thing is being sure the cache screws nothing up.
Especially for older comps, as the config phase can take longer than the compiling  .
So, first time with a simple package (I used popt):
./configure -C
Then edit the config.cache by removing lines you might change.
Then, whenever compiling anything, copy this file there and give -C to configure and it will load the cache and not check anything that's in there.
--------------
There's no such thing as life. Those mean little jocks invented it ;)
-
Windows is not a virus. A virus does something!
|
.
DSL Market ,
Great VPS hosting provided by Tektonic
