Well, I searched the jamming archive, and I've searched my personal
mail files, but didn't find anything, although I could have sworn
I've seen postings about this...
The ghost thread. We need a thread sensitive :-)
Jam doesn't have any concept of "after the build is complete". If
you have a bunch of things that need to be done to stuff after it
is built, just define a rule that makes its outputs dependent on
its inputs, and invoke that rule using your built things as inputs.
E.g., if your last step is to bundle up everything you build in a
tar file, invoke your tar rule on everything you build. It won't
get run until the build is complete.
The problem is the build builds numerous products. The number
of dependencies would be huge and not maintainable. It would
more general to have a start and end action.
In that situation, I
think your best bet is to run a separate post-build script after
jam completes.
This is what i ended up doing.
thanx
3 messages in com.perforce.jamming[jamming] Re: last rule for jam?
