Hi Steven,

I am experiencing the problem on Windows with msvc.

I added the semaphore in the msvc toolset and it works. Thank you.

The only issue that I still have is that it looks like ruining one linking at a time is not much better than all together. Is there a way I to change the JAM_SEMAPHORE value - instead only 1 it to limit the threads to a different number?

Thanks,

George

On Mon, Jul 1, 2013 at 12:28 PM, Steven Watanabe <watanabesj@gmail.com> wrote:

AMDG

On 07/01/2013 12:11 PM, George Georgiev wrote:
> Hi,
>
> I am having a project with multiple libraries and unit-tests
> (applications). From time to time depending on the change I am getting in
> situation where almost every unit-tests application needs to be linked. I
> would like to avoid running too many link processes since it does not seam
> to perform very well. At the same time I do want to use the multi-thread
> option for the rest of the targets.
>

I believe that Boost.Build already does this
for gcc.

> What will be the easiest way to do that. Can I use SEMAPHORE variable? How
> I can apply it to all the targets from a type (in my case - executable)?
> Can I specify semaphore value different than the default '1' - in my case 2
> or 3 linking threads will still be ok.
>

The variable is JAM_SEMAPHORE. You have to set
it per target. Boost.Build doesn't expose this.
I think the only way to use it is to edit the
toolset to set this variable.

In Christ,
Steven Watanabe

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build