From: David Abrahams (dave_at_[hidden])
Date: 2003-03-29 10:11:27
Vladimir Prus <ghost_at_[hidden]> writes:
> Andre Hentz wrote:
>> > I don't know a solution yet. How can we force rebuild of 'rsp' file when
>> > 'exe' is rebuilt?
>> How about marking RSP targets as TEMPORARY, so they are removed
>> after its dependents are built?
> Interesting idea. But note that "TEMPORARY" does not remove file, no matter
> how unintuitive that is. In Perforce Jam, you'd have to call "RmTemps" rule
> to actually remove files and V2 does not have such mechanism yet (must be
> simple to add).
> I'd like also to know what Dave thinks --- he must have good experience with
> Jam tricks from work on testing system for V1.
It seems to me that hiding response-file generation and removal from
the jam dependency system may be the right thing to do. That would of
course mean that the RSP file is not actually a target at all, but
just gets built and removed or built and forgotten. We could even
imagine generating it in some temp. directory, though I don't see a
big advantage in it. The danger in either case is "clean" does not
find the RSP if it is not a target. That will less of a problem for
build-and-remove, but failed links may also leave the RSP behind.
The idea is that linking would encompass 2-3 actions:
1. a piecemeal action to build the RSP
2. the actual link
3. (optional) remove the RSP
-- Dave Abrahams Boost Consulting www.boost-consulting.com
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk