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.

On Jan 11, 2017, at 10:53 PM, Rene Rivera wrote:

On Tue, Jan 10, 2017 at 8:23 PM, Douglas Capeci <doug_capeci@mentor.com> wrote:
Does boost build support parallel builds distributed across multiple linux machines on a grid such as Sun Grid or LSF?

Not directly.. Although distributed builds have been done in the past with tools like distcc.

If so, what is the best way to accomplish this goal? Seems hard to find any docs that describe this requested behavior.

Not sure what the best way is.. But the one I know of is to write a wrapper script for the toolset command that takes care of the distribution, i.e. an equivalent to distcc. And then you configure the toolset but point it at. For example user-config.jam:

using gcc : : distcc ;

HTH.

--
-- Rene Rivera
-- Grafik - Don't Assume Anything
-- Robot Dreams - http://robot-dreams.net
-- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail