Thanks Rene for your resonse.
Using your approach, does it guarantee that all build commands created by Boost Build will invoke my script or only those commands that are intended to invoke the gcc compiler? In other words, if a build action includes a command that is not a compiler command will my script be invoked?
It also seems that Steve's suggestion of setting the Boost Build JAMSHELL variable might be easier, since the user's script is simply receiving a list of all shell commands for each task that can be distributed across the network in parallel. A slot id is even provided with each task making simple forwarding to a grid engine easy.
Any comments on this?
On Jan 11, 2017, at 10:53 PM, Rene Rivera wrote: