[Scons-users] Suggestions for using MP Mutex during Action phase of build
manohar.mavilla at gmail.com
Sat Jan 30 00:52:26 EST 2021
Thanks for your prompt response.
We run multiple builds in parallel in different processes. Would calling
SideEffect() from one build in one process prevent mutual access to a file
from other builds running in separate processes?
On Sat, Jan 30, 2021 at 12:29 AM Bill Deegan <bill at baddogconsulting.com>
> You should probably be using SideEffect() if you're trying to prevent
> mutual access to a file.
> On Fri, Jan 29, 2021 at 8:14 AM Manohar Reddy <manohar.mavilla at gmail.com>
>> Dear Scons Community users,
>> In SCons, we have support for a multi-process mutex that can be acquired
>> by each build variant to coordinate writing to a shared file. The mutex is
>> implemented through two methods:
>> Example usage:
>> if not os.exists("foo.file"):
>> env.FooBuilder("foo.file", "foo.source")
>> But, this is currently not working for the action phase of the build. In
>> the example above, the call to env.FooBuilder() is protected by the mutex,
>> but this only queues up the action for SCons to perform later, and by the
>> time SCons executes this action, the mutex will have already been released,
>> so the actual action is not being protected.
>> Can someone guide us on any alternative approach where the pre-action and
>> post-action are performed right before and after the execution of the
>> Scons-users mailing list
>> Scons-users at scons.org
> Scons-users mailing list
> Scons-users at scons.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Scons-users