-
|
I have a requirement where I want to build multiple configurations simultaneously in the same source code directory, similar to the difference between For CI services, such occasional errors are critical, and without reviewing the detailed logs, it is impossible to determine whether the issue stems from code problems or what appears to be a data race problem. I would like to know if there are any best practices in SCons for parallel builds of multiple configurations? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
|
By simultaneous builds, you mean concurrent running of SCons instances from the same source tree? That doesn't work, mainly for the reason in the snip above: the signature database is a single file, with no resource protection beyond the one you see (writing to a temporary and renaming it). You'll always be fighting over the contents of that file. You might be able to improve on things by arranging for each build flavor to have its own https://scons.org/doc/production/HTML/scons-man.html#f-SConsignFile It's possible that judicious use of environments and variant directories can let you do such a build with a single SCons invocation. |
Beta Was this translation helpful? Give feedback.
-
|
@HalfSweet You can build multiple variants via one invocation of scons by using VariantDirs()'s (easier if you specify them in your call to SConsign().. |
Beta Was this translation helpful? Give feedback.
@HalfSweet You can build multiple variants via one invocation of scons by using VariantDirs()'s (easier if you specify them in your call to SConsign()..
(This is exactly the use model VariantDirs are meant for)