Re: [jamboost] header cacheing, etc.

From: David Abrahams (david.abrahams_at_[hidden])
Date: 2002-05-24 16:51:26

----- Original Message -----
From: "Thomas Witt" <witt_at_[hidden]>
To: <jamboost_at_[hidden]>
Sent: Friday, May 24, 2002 4:41 PM
Subject: Re: [jamboost] header cacheing, etc.

>
> Dave,
>
> On Friday 24 May 2002 14:25, David Abrahams wrote:
> >
> > I'm prepared to merge the changes, but thought I should give people a
> > chance to look at them first.
>
> when trying to use HCACHEFILE I ran into the folllowing question. Is it
> possible to refer to a files location from within a file. I would like to
do
> something like this:
>
> HCACHEFILE = $(location-of-this-file)$(SLASH).hcache ;
>
> The idea is having one cachefile per project. To me this seems to be the
best
> way to use headercaching, or is there an advantage in having a central
> cachefile ?

Actually, it appears that the cache file gets some relative paths, so a
quickie approach would have to use one HCACHEFILE per build invocation
directory. I added this to my allyourbase.jam:

...

normalized_ALL_LOCATE_TARGET ?= [ join-path $($(gTOP))
$(ALL_LOCATE_TARGET) ] ;
LOCATE_SOURCE = [ FDirName $(normalized_ALL_LOCATE_TARGET)
$(nodot_subdir) ] ;
LOCATE_TARGET = $(LOCATE_SOURCE) ;
+ HCACHEFILE ?= $(LOCATE_TARGET)/.jamdeps ;

SOURCE_GRIST = [ FGrist $(<[2-]) ] ;

# Reset per-directory ccflags, hdrs

SUBDIRCCFLAGS = ;
SUBDIRC++FLAGS = ;

...

I'm sure we can eliminate the relative paths, eventually.

-Dave