In our build system, when building boost it always uses 2 cores, even if you pass a custom -j jobs number to build.sh . The boost package should use the number of jobs that was passed in on the CLI
In our build system, when building boost it always uses 2 cores, even if you pass a custom -j jobs number to build.sh . The boost package should use the number of jobs that was passed in on the CLI
This has the potential to greatly increase the speed of compiling Hush on a fresh clone on multiple cores. boost is one of the slowest dependencies to compile
This has the potential to greatly increase the speed of compiling Hush on a fresh clone on multiple cores. boost is one of the slowest dependencies to compile
Commit 79f126be43 on the duke branch now lets boost use the default of as many cores that the machine has, which seems good enough. Closing.
Commit 79f126be431fdb07cc81502df716da36b7a10d56 on the duke branch now lets boost use the default of as many cores that the machine has, which seems good enough. Closing.
In our build system, when building boost it always uses 2 cores, even if you pass a custom -j jobs number to build.sh . The boost package should use the number of jobs that was passed in on the CLI
This has the potential to greatly increase the speed of compiling Hush on a fresh clone on multiple cores. boost is one of the slowest dependencies to compile
Commit
79f126be43on the duke branch now lets boost use the default of as many cores that the machine has, which seems good enough. Closing.