#25 closed task (fixed)
Create a compiler object cache
Reported by: | bird | Owned by: | bird |
---|---|---|---|
Priority: | minor | Milestone: | 0.1.3 |
Component: | kBuild | Version: | |
Keywords: | Cc: |
Description
Integrating the object cache in kBuild will permit us to skip unnecessary linking.
Change History (3)
comment:1 Changed 17 years ago by
Status: | new → assigned |
---|---|
Summary: | integrate or create a compiler object cache → Create a compiler object cache |
comment:2 Changed 16 years ago by
Priority: | major → minor |
---|---|
Resolution: | → fixed |
Status: | assigned → closed |
This seems to work pretty well, except for Visual C++. closing.
comment:3 Changed 16 years ago by
Milestone: | 0.1.1 release → 0.1.3 |
---|
Note: See
TracTickets for help on using
tickets.
Of course it much more fun writing this myself, so in source:trunk/src/kObjCache is the beginnings of something. The current code implements a rather simple cache that only contains a single object and will therefor only speed up incremental builds.
That said, the current code works pretty will with incremental builds. I get a 3x speed up on a touch include/iprt/err.h build (3:45 -> 1:17 mins) on the iMac here (building VirtualBox? of course). The bad news is that Visual C++ sucks speed wise when requested to only run the precompiler, so there isn't much time saved here. (gcc/g++ is very fast, and therefore saves a lot of time.)
The next thing that needs doing is tracking extra output files (check that they exists for a start). And add a pass-thru piped mode to try speed up the initial build at bit, current figures are like 10:26 vs 11:42 mins.