> There are two completely separate things: one thing is make deciding > how many jobs can be run in parallel and when more jobs can be started.
Thanks for your explanation. > That's controlled by the jobserver and currently there's no > way to replace the built-in jobserver implementation with something > different (such as allowing a remote facility to track this). I hope that this situation can be improved somehow. > The second thing is invoking a single job once make believes that it's > OK to do so. That is reasonable. > The "remote" API can make it possible to build make so that it always > uses this method, This might be also interesting for specific software applications. > but I think it's become obsolete The software status might evolve again a bit more. > because it's simpler and more flexible to implement a separate program > and reset SHELL, How many computer resources can be eventually saved with an alternative approach? > as I describe above, than implement a bunch of new code inside > GNU make itself. How are the chances to improve internal configuration interfaces? Regards, Markus _______________________________________________ Bug-make mailing list Bug-make@gnu.org https://lists.gnu.org/mailman/listinfo/bug-make
