You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Support for distributed compilation would be a cool feature to have. I suppose that it could be very complicated though. Build commands in the Ninja manifest would need to use some wrapper command that redirects the command to a build slave, then we still need to make sure that the buildslave can properly execute the command, which is problematic already when only the build directory on the slave is on a different path.
The text was updated successfully, but these errors were encountered:
I suppose this will also only work if we're using relative paths for everything, which is not really the case in Craftr at the moment.
On the upside, now in Craftr 3 , commands are always dispatched via the Craftr command-line (using the --run-action option). This allows us to easily catch the invokation and re-direct it to a build slave.
Support for distributed compilation would be a cool feature to have. I suppose that it could be very complicated though. Build commands in the Ninja manifest would need to use some wrapper command that redirects the command to a build slave, then we still need to make sure that the buildslave can properly execute the command, which is problematic already when only the build directory on the slave is on a different path.
The text was updated successfully, but these errors were encountered: